forked from mosaicstack/stack
mos-dt-0andClaude Opus 5
43f69bf167
Per Mos, with his two additions. Charter gains a fourth first-class principle: when a property cannot exist at the layer that specified it, three honest moves are mandatory — implement what the layer can guarantee; state the boundary in BOTH directions (what it does not defend AND what it does, since either alone misleads); and record the real guarantee as a TRACKED DEPENDENCY, not prose. A written-down gap is acceptable engineering; an implied-fixed gap is the mission's core failure in a new costume. The residual risk is now RM-59 (depends_on RM-12, RM-21, RM-25) — a real backlog task owned by the choke-point executor and spine, which verify from outside the worktree's authority. Mos's point: 'record where the guarantee comes from' only holds if the record is a live dependency someone must close; a documented gap with no owner becomes a permanent gap that reads as intentional. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>