RESIDENT / REPORTER
Document the event and source trail. Ask which office owns the mechanism, what appeal exists, what would prove correction, and when the receipt will be public.
Project Shadow 1.0.1 contains no Myth package. Generic Myth v0.2.0 and Full-Canon Myth v0.3.5 are separate optional companions; both default off, neither is required by R1, and neither can authorize action or change an R1 result. ARM remains a civic repair workshop, not a certification service; publication transfers no authority and is not operational deployment, efficacy, safety, certification, a legal-compliance finding, permission to act, or a global green.
One civic lifecycle / six distinct public doors
The RecordremembersCivic QAinspectsPBHPpausesARMrepairsProject Shadowinstruments + testsALMSIVIpreserves optional originCHAMBER 06 / CIVIC FIELD MANUAL
The Manual becomes real when a person can use it on Monday morning: to inspect a decision, stop a preventable harm, design a repair, and leave a record the next person can challenge.
FOUR ENTRY ROLES
The action changes with the role. The duty to distinguish evidence from inference, trace burden, preserve recourse, and verify effectiveness does not.
Document the event and source trail. Ask which office owns the mechanism, what appeal exists, what would prove correction, and when the receipt will be public.
Separate the legitimate service goal from the harmful shortcut. Escalate the recurring condition, preserve the smallest safe Door, and log the control failure.
Name authority, funding, implementation owners, affected groups, safeguards, measurement, correction triggers, and the independent reviewer before asking for trust.
Disclose the model or automation boundary, data and objective limits, tool permissions, test coverage, human stop, appeal path, incident receipt, and retirement condition.
FIRST EIGHT MOVES
Use one real failure, one accountable scope, and one public definition of done. Expand only after the path works.
Choose one recurring public failure narrow enough to trace end to end.
Open an evidence ledger before writing the diagnosis.
Map authority, incentives, implementation, data, vendors, and consequence handoffs.
Interview the people who absorb the delay, burden, error, surveillance, or loss of recourse.
State the strongest competing explanation and the unknown that could change the plan.
Define a reversible first correction and an independent pause condition.
Assign a recurrence mechanism, prevention owner, verification owner, and deadline.
Publish a plain-language receipt—including when the repair did not work.