docs(deed): mapping spec family 7 — 0-AI-MANIFEST decision (rename-hazard response) - #858
Merged
Merged
Conversation
…zard response) The first live conformance finding of the conversion wave (marid, verified 2026-09-19): a renamed-not-translated 0-AI-MANIFEST.deed — INI content wearing a .deed name at repo root — fails grammar, filename dispatch, and family coverage at once. Renames are not translations; this spec gives the wave a decision BEFORE ~900 generated files meet it. Contents: naming-collision rule (0.2-AI-MANIFEST.a2ml cartridge directory-manifests are a DIFFERENT family — match on content shape, never filename); option A recommended ((manifest ...) clauses on the repo deed; praxis-deed rejected with reasons); full field table (agent identities as verbatim symbols, policy rules as order-preserving list, work-allocation cross-checked against declared agents); wave rules (no renames; whole-tree deed-lint CI gate; generator-first per the #645 lesson); three ruling asks recorded. Refs #837
Contributor
|
Warning Review limit reachedNext included review available in 4 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 (1)
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 |
|
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.
Response to the first live conformance finding of the wave (reported on #837, verified on marid main @ 96cfea4):
0-AI-MANIFEST.deedat the repo root is INI content wearing a.deedname — renamed, not translated. It fails grammar (=is not a deed), filename dispatch (matches no pattern), and family coverage (family 7 didn't exist). ~900 generated files are behind it. This spec gives the wave its decision before contact, not during.Contents:
0.2-AI-MANIFEST.a2mlcartridge directory-manifests (YAML-ish, JSON-schema governed) are a DIFFERENT family — the wave matches on content shape, never filename(manifest …)clauses on the repo deed (it's repo state — who is allocated here, under what policy);*_praxis.deedrejected with reasons (prose rules, no:when/:then/:prioritybases — forcing them in invents fields the grammar forbids before ruling)deed-conformance.yml) is the enforcement surface; generator-first per the Fix the scaffold that propagates 'License: PMPL-1.0-or-later' (runbook §7a source fix) #645 lesson (fix the ~900-file emit source before the files)Example verified mentally against the actual marid instance shape; translator support rides after the ruling (fail-closed until then — which is precisely the correct current behaviour).
Refs #837.