The mesh counts the same facts. Zero on both sides closes the session; otherwise it answers, for example: “tasks: you declared 0, the mesh reads 2”
Step 5 · the test starts itself
The last action in starts the group's test
Action A
test-created
Action B
test-created
Action C
test-created — arrives last
Action D
parked on a question
C arrives → the test starts. D holds nothing back.
The group locks; D moves to the package's next group.
Arming on the first action split Workwear's 41 review actions into 11 groups — 11 test runs and 11 releases for one review (13 October). gate_arm_verdict.ts
Step 5 · tester, releaser, node agent
Three programs take turns — nobody watches
1
Tester
runs the e2e steps on dp-box-reviewer and climbs the actions
2
Releaser
stage, then prod — prod is locked 06:00–20:00 on weekdays
3
Node agent
each box installs the published package
Each step is started by the one before. Nothing polls.
The test gate was once a model session reading the board every two minutes. Now it is run_test_gate.ts, and a model opens only on red. settle_parents.ts, operate.ts
Step 6 · failures
Every red goes to one place: the fail stream
1a red test, release or install is published as a failure
2repeats of one error fold into one record
3a new error: one Haiku call matches it to a known root cause
4each root cause gets one fail session — at most 3 at once
✓it fixes the cause, starts the test again, closes itself
Step 7 · the reasoning
Claude only where judgement is needed
Claude — judgement
coding an action
diagnosing and fixing a failure
Plain code — events
starting a test and running it
releasing to stage and prod
installing on each box
closing a session
Step 7 · the rules
Four rules hold it together
1
Done is a fact
a stage, a green test, an answer from Adrian — never a sentence
2
Root cause, no fallbacks
measure the cause before the fix; a fallback hides the defect
3
The rulebook
every correction becomes a rule — 541 in dp-brain/rulebook
4
Hooks
26 checks run before every shell command; a breach is refused with the right command
Your day
What a developer does day to day
Steer the sessions
give a session its order
answer the questions on actions
approve from a before/after picture
read the fail stream
Code by hand — the same steps
take the action; read the rulebook slice
fix; code.typecheck clean
write the e2e step; climb to test-created
commit with Action:, push — then it is the tester's