LOCAL GOVERNANCE RAILFOR SOFTWARE WORK
Let AI build.Stay the author.
Turn the design, scope, and done-criteria a human approved into one spec of record. AccordRail stops work only at the moment it breaks that accord — with the reason and the next move attached.
WINDOWS / LINUX · LOCAL ONLY · 0.1.3
ONLY THE MOVE THAT BREAKS THE ACCORD STOPSA REAL REFUSAL
$ accordrail gate
DENY LAYER BACKFLOW
src/domain/rules.ts
→ src/ui/format.ts
A dependency from domain to ui runs
against the approved layer direction.
Your options
01 / move the shared logic into shared
02 / propose a revision to the spec
✓ FILE NOT WRITTEN — nothing is broken yet
01 / THE REASON
Not an intelligence problem.
A memory problem.
A good design is decided.
The AI and the humans both understand the reasons. Nothing is broken here.
The reasons fall out of context.
No malice involved. The judgment made dozens of turns ago simply isn't there anymore.
Everything still runs. The shape is gone.
Tests pass, the compiler is silent — and the structure quietly becomes something no one can fix.
02 / ONE AGREEMENT
From the accord
to the work.
This is not turning conversations into rules. A human-approved spec of record is the baseline, and the work handed to the AI, the code that gets written, and the claim of "done" are all checked against that same single rail.
01SPEC OF RECORD
Spec
Only human-approved design becomes the baseline that nothing else can rewrite.
Read ↗ 02WORK OWNERSHIPOwnership
Hand over one person's share of the work — not the whole codebase.
Read ↗ 03DETERMINISTIC GATEGate
Stop only the move that breaks the spec, with the reason and the next options.
Read ↗ 04MEASURED EVIDENCEEvidence
Keep a record of what was stopped, what passed, and what was read.
Read ↗03 / THE GATE
It doesn't wait
to be called.
AccordRail doesn't bet on the AI remembering to ask. Write/Edit is checked before the file exists; Shell commands are re-measured the moment they finish.
How the gate works ↗WRITE / EDIT GATEDENIED · 01
PROPOSED
src/domain/rules.ts
→ src/ui/format.ts
backflow
A dependency from domain to ui crosses the approved layer direction.
FILE NOT WRITTENNEXT: MOVE TO SHARED / PROPOSE REVISION
04 / LOCAL BY ARCHITECTURE
Your code
stays home.
Source analysis, the dependency graph, the spec of record, history, the UI — everything runs on your machine. No cloud calls, no statistical models in the verdict.
TypeScriptJavaScriptPythonRustWindows x64Linux x64
ACCORDRAIL / 0.1.3
Let AI build.Get started ↗
Stay the author.