forked from mosaicstack/stack
mos-dt-0andClaude Opus 5
d1e7ba19ca
Charter gains a first-class principle per Mos: no write is done until the requested PROPERTY is observed; a success exit code is not evidence. Success output is designed to be believed — that is why the inert-gate class exists and why the P-WRAPPER tri-state is not optional. Recorded with its provenance: the orchestrator committed this exact error (D-12), and three of the session's twelve instances were its own. D-13: diagnosing D-12 found two parallel credential registries that can disagree. gitea-mosaicstack-mos-dt-0.token EXISTS, but tea has no mosaicstack login for that identity — so raw-API paths work while tea-dependent wrapper paths silently degrade. tea is not stale; the login does not exist. Capability declared authoritative by the token-file set does not govern the tea path. RM-04 must reconcile the registries (or assert agreement at startup, with a must-fail control). RM-50's pre-dispatch check must verify capability for the path actually used. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>