PUBLIC WORKS LEDGER
Make the evidence, claim state, owner, correction history, and unresolved questions visible.
PROJECT SHADOW 1.0.1 · CORRECTED R1 REFERENCE · PRELIVE · 2026-08-17
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.
ECOSYSTEMARM
One civic lifecycle / six distinct public doors
The RecordremembersCivic QAinspectsPBHPpausesARMrepairsProject Shadowinstruments + testsALMSIVIpreserves optional originA repair system for public power
AMERICA NEEDS A CAPA.
A CORRECTIVE AND PREVENTIVE ACTION SYSTEM.
Politics, institutions, markets, media, and AI all convert incomplete models into real consequences. This manual connects public evidence to diagnosis, a pause before harm, corrective action, prevention, verification, and a record that cannot quietly forget.
OUTRAGE IS AN ALARM.REPAIR IS A PROCESS.NO CLOSURE WITHOUT A RECEIPT.
ONE MANUAL / THREE NECESSARY LAYERS
Evidence you can inspect.
Machinery you can understand.
Tools you can run.
No single layer is enough. A ledger without repair becomes an archive. Repair without evidence becomes ideology. A field guide without system mechanics mistakes symptoms for causes.
REPUBLIC REPAIR BAY
Expose the machinery: power, incentives, dependencies, automation, failure paths, and feedback loops.
CIVIC FIELD MANUAL
Give people a procedure they can actually run—from first observation through verified closure.
THE SAME ACCOUNTABILITY PROBLEM / DIFFERENT MACHINERY
Politics. Systems. AI.
The Manual treats them as connected consequence engines. Each needs evidence, bounded authority, a challenge path, a repair owner, and an observable definition of done.
Political power
Elections, parties, legislatures, executives, courts, donors, media, and organized movements convert stories into authority.
- RECURRING FAILURE
- Accountability is episodic while influence is continuous.
- INSPECTION QUESTION
- What changes between elections, and who can verify it?
Institutional systems
Agencies, procurement, benefits, policing, schools, health systems, and workplaces turn policy into daily consequence.
- RECURRING FAILURE
- Procedure can look neutral while distributing burden and recourse unevenly.
- INSPECTION QUESTION
- Who pays first, who can appeal, and can the harm be reversed?
Automated judgment
Models, ranking systems, agents, data pipelines, and vendor tools can scale a hidden assumption into thousands of decisions.
- RECURRING FAILURE
- A fluent output can outrun evidence, ownership, and meaningful human review.
- INSPECTION QUESTION
- What is the action boundary, and where is the independent stop?
THE PUBLIC REPAIR LIFECYCLE
From event to evidence-backed closure.
Every stage produces a handoff and a receipt. Skip one and power can rename the failure, bury the uncertainty, implement theater, or declare victory without proof.
- 01→
Observe
Collect the event, decision, output, context, and people affected before the story hardens.
- 02→
Document
Separate sourced fact, verified fact, inference, hypothesis, and the unknowns that could change the decision.
- 03→
Diagnose
Trace authority, incentives, dependencies, bottlenecks, automation, and who absorbs failure first.
- 04→
Pause
Interrupt irreversible consequence. Name the Wall, find the Gap, and preserve a smaller reversible Door.
- 05→
Repair
Correct the present harm and change the mechanism that would otherwise reproduce it.
- 06→
Verify
Define an observable test, owner, deadline, challenge path, and evidence threshold before declaring success.
- 07→
Remember
Publish the receipt, correction history, unresolved questions, and what would trigger another review.
CHOOSE AN ENTRY / KEEP THE WHOLE SYSTEM
Five doors into the work.
Start where the need is clearest. Each door reconnects to the same lifecycle and the full standalone manual remains intact.
01 / DIAGNOSE
Map the recurring failure
Find the mechanism beneath the argument and identify who pays first.
OPEN WORKBENCH ↗02 / REPAIROpen the repair library
Move across democracy, information, economic power, rights, public capacity, and AI.
OPEN WORKBENCH ↗03 / BUILDCreate a repair work order
Turn a documented failure into containment, correction, prevention, verification, and an exportable receipt.
OPEN WORKBENCH ↗04 / TESTRun the public-power test
Score a promise against evidence, implementation, rights, reversibility, and receipts.
OPEN WORKBENCH ↗05 / VERIFYBuild the evidence ledger
Keep fact, inference, uncertainty, correction, and verification from collapsing together.
OPEN WORKBENCH ↗WORKING FLAGSHIP / LOCAL TOOL
Agreeing with a candidate is not evidence that the promise can survive power.
The Candidate Test begins with a short ten-question values map, then opens into a complete eight-lens evidence audit. Candidate words, governing record, funding, contradictions, foreseeable harm, consistency, and corrections remain separate from party and from the visitor's values.
Open the test →WORKING TOOL + PRESERVED IDEA
One tool is live locally. One earlier idea remains a concept.
The Repair Builder is the current working tool. The Local Action Generator below is an archived concept, not an active build queue, launch promise, or extension of locked Project Shadow R1.
Policy Repair Builder
Convert a documented failure into a repair record: root cause, immediate correction, preventive action, lawful authority, affected people, owner, due date, verification method, and effectiveness threshold.
Open the working CAPA-style builder →Local Action Generator
Turn one scoped civic problem into a jurisdiction-aware action path: who controls the lever, what record to request, where testimony belongs, what coalition is needed, and how a resident can verify movement.
Historical proposed output → local action sheet with escalation pathWHY ME / WHY THIS BASELINE
Openly democratic socialist. Publicly testable.
Phillip Linstrum is a working-class father and QA Systems Manager who built ARM to apply harm prevention, audit trails, corrective action, and effectiveness checks to public power. The viewpoint is disclosed. The evidence rules apply even when the author agrees with the candidate.
WHYNO HIDDEN BASELINE ↗
ARCHIVED SOURCE EDITION · 2026.08.03
The earlier standalone manual remains available for provenance.
It is a dated research snapshot, not the current website status surface. Its numerical and political claims require item-by-item re-verification before being represented as current; the working Repair Builder and this live site govern the present public workshop.
SNAPSHOTNOT CURRENT EVIDENCE ↗