docs(deed): redirect every broken deed-era pointer — #64 ref, abnf links, district-path links; leave normativity to a ruled follow-up - #838
Merged
Conversation
- Campaign issue reference (#64) pointed at a closed, unrelated Hypatia issue; now points at the real tracking issue #837 in both spec copies. - All abnf/deed.abnf link targets resolved from each doc's own directory depth to the file holding the cited content: deed.anbf (v1.0.0) or the misnamed v0.1.0 archive deed.abnf_v1.0; the two-file naming situation is stated plainly in the normative-grammar paragraph and in comment-only banners atop both grammar files. Grammar bodies byte-unchanged. - K9 spec links repointed to 2-protocols/k9-coordination/spec/. - anchor README: three more dead links of the same class repaired (../deed/spec, grammars/anchor.abnf, old k9-coordination-protocol path). - Every link: in the three edited docs validated to resolve. Refs #837
Contributor
|
Warning Review limit reachedNext included review available in 43 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (5)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
hyperpolymath
added a commit
that referenced
this pull request
Sep 17, 2026
#837) (#840) Campaign step 2 → first mapping spec. Refs #837 (tracking); does not close it. ## What this adds `1-formats/deed/mappings/` — a new home for translation authority docs, exactly the thing the groundwork said was missing (a family is allowed to be translated only against a mapping spec; translation-without-spec is how the pin-generator trap repeats). **`mappings/README.adoc`** — the frame every family spec must carry: source surface · target form · field table (path + deed value type + transform) · drop doctrine (STATE-v2 "discard the derivable" carried into the campaign) · provenance/validation rules · acceptance greps. Also fixes the family order groundwork chose, highest-loss-risk first. **`mappings/clade-to-repo-deed.adoc`** — family 1: `CLADE.a2ml` → `<canonical-name>_chora.deed`. - **Field table is complete** — every template field mapped to clause path + type + transform. Enums and closed taxonomies carried *verbatim* as symbols: lineage `standalone|monorepo|monorepo-child|inflated|deflated|hub|satellite`, status `reserved|incubating|active|dormant|merged|superseded|archived|extinct`, the 12-clade closed taxonomy, and the deliberate `primary`+`primary-name` redundancy (so CLADE-006 survives). - **P-1..P-5 provenance rules:** uuid re-derived (UUIDv5 URL namespace) and fail-closed on mismatch, never copied; source must still parse as a2ml before translation (half-hand-translated files rejected); every emitted deed parses against the normative grammar (`deed.anbf` v1.0.0 until the #837 canonical-file ruling); `estate` stem fails closed on dispatch ordering; CLADE-003/004/005/006 gate semantics re-expressed before the checker may retire. - **`:beholding-chora` handled honestly** — required by the grammar, so the translator resolves it from the registry (gv-clade-index is the one declaration site today) and **refuses to emit** otherwise; no made-up identifiers. - **Worked translation** of the real `rsr-template-repo` instance, machine-checked against the grammar's structural rules before commit (balanced forms 12/12, `:schema-version` structurally first, zero bare `=` outside strings). - **Open questions recorded, not decided** (§8): stem choice canonical- vs prefixed-name; whether gv-clade-index migrates in the same wave; ordering for repos minted before the chora is registered. ## What this does not do - No grammar file touched; the canonical-file ruling from #838 stays where it is (with the owner). - No `.a2ml` file converted; this is spec, not execution. - No new normativity invented — every clause shape cites the grammar's own rules (`=`-ban, symbol-vs-string, dispatch side condition). After this lands (and with the open rulings answered), the next campaign steps are the remaining family specs (META/ECOSYSTEM, STATE, AGENTIC/…) and then the canonical translator + conformance lane that these specs constrain.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope: pure redirect PR requested by the owner — make the pointers resolve, stamp no normativity verdict. Refs #837 (campaign tracking).
What was broken (post-district-reorg main)
#64— actually a closed, unrelated Hypatia-setup issuelink:../abnf/deed.abnf(7 mentions × 2 doc copies)deed.anbf(v1.0.0, current) ordeed.abnf_v1.0(misnamed v0.1.0 archive)link:../specs/K9-COORDINATION-SPEC.adoc(2 × 2)2-protocols/k9-coordination/spec/COORDINATION-K9-SPEC.adoc1-formats/a2ml/anchor/README.adoc:../deed/spec/…,grammars/anchor.abnf,../k9-coordination-protocol/specs/…../../deed/spec/…,abnf/anchor.abnf,../../../2-protocols/k9-coordination/spec/…(Three of the anchor dead links pre-date today; same redirect class, folded in.)
Honesty banners instead of a verdict
The grammar ships as two disagreeing files:
deed.anbfdeclares itself v1.0.0 (the later revision);deed.abnf_v1.0contains v0.1.0 DRAFT content despite its filename. Rather than unilaterally renaming — which would promote one to normative — each file now carries a comment-only banner cross-referencing the other and #837, and the docs' normative-grammar paragraph states the two-file situation plainly. Grammar bodies are byte-unchanged.DEED-GRAMMAR-SPEC_v0.1.adocis an archive and is left frozen; its stale#64is documented here rather than re-editing history.Validation
link:resolves to an existing file from the doc's own location (external links excluded)#64)orabnf/deed.abnfreferences in the live copiesgit diff --stat: +12/−1 across both grammar files, the −1 being the archive's reworded intent line)Follow-up (held, needs ruling): choose the canonical grammar file, likely
git mv deed.anbf deed.abnf+ rename the archive todeed.abnf_v0.1.