4 Commits

Include renames

Author	SHA1	Message	Date
mos-dt-0andClaude Opus 5	cdd5568adb	docs(remediation): promote query-for-refutation to charter doctrine ... Per Mos. A subordinate asked to confirm a hypothesis will agree — the bias is induced by the query, not by the answerer's diligence. 'The DB flaked, please confirm' and 'confirm or refute, with the log line that proves it' are different instruments returning different answers to the same question. This matters most with agent subordinates, which are agreeable by construction, so the discipline cannot rest on the answerer being rigorous — it must be built into how the question is asked. Origin: the orchestrator's ci-postgres hypothesis was refuted by the implementing seat with log evidence and then settled by reproduction. Phrased for confirmation, it would have returned agreement and D-21 would have been re-classified on a false premise, silently corrupting a banked finding. Operational form: state the hypothesis as yours, ask for evidence that kills it, say what would change your mind, and reproduce when the answer is consequential. Added to KICKSTART's standing invariants so it survives compaction. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 23:21:15 -05:00
mos-dt-0andClaude Opus 5	cbbe3e1ce2	docs(remediation): gate definition now REFERENCES canonical roles; bank D-26 ... The delivery-gate definition was incomplete from setup — the merge-gate verdict step was missing because the gates were restated from memory rather than referenced, and the omission propagated into every worker brief since. Then it recurred inside the correction: the correcting message was itself a restatement and dropped five things, including a security precondition (an unminted gate seat fails open to the owner's admin account — the #3084 breach mechanism) and a citation to a file that does not exist. D-26 is the definitive case because every condition favoured success: attention maximal, actor knew the rule best, subject was the rule itself. A rule its own enforcer cannot follow while enforcing it is not a discipline — it is a requirement for a mechanism. MISSION.md and KICKSTART.md now reference fleet/roles.local/merge-gate.md and fleet/roles/validator.md and state only the gate ORDER. Every reference resolves; a dangling pointer is worse than a restatement. Precondition independently verified: merge-gate token is least-privilege, pull=True push=False admin=False — structurally cannot merge. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 22:53:13 -05:00
mos-dt-0andClaude Opus 5	31c3191305	docs(remediation): rolling-branch resume pointer + D-9 interim comms rule ... KICKSTART resume now points at origin/remediation/state for the live board, per Mos's cadence ruling: every tick is pushed to the rolling branch immediately (durable per-tick, no per-tick main PR); main carries periodic snapshots only. Reading the board from main would silently yield a stale tick, so the step warns explicitly. D-9 hardened: comms/v1 must use file/stdin transport, never argv interpolation. Standing interim rule until then — agent-send -f for any body with special characters, never -m. Mandatory in every worker brief alongside the D-8 clause. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-07-31 17:50:26 -05:00
mos-dt-0andMos	01e966f36d	docs(remediation): mission charter + reconciled execution backlog (#1026) ... Co-authored-by: mos-dt-0 <[email protected]>	2026-07-31 22:47:03 +00:00