juliodavid8a.com
/Doctrine

Doctrine — the factory's constitution.

Rules distilled from repeated failure, written once, enforced everywhere. An article is a rule I wrote after the same failure happened more than once. Each one lists the sparks that caused it.

Each article is a constraint promoted from the spark ledger. Articles are rows in the doctrine table — ratification is an INSERT, and this page grows on its own.

Each article is one row; writing the row publishes the article.

01 · Everything is a Form

RATIFIED 2026.2
§ THE RULE

Every unit of work enters as a form and leaves as a record. No loose ends, no untracked state.

§ WHAT IT CHANGED IN THE LOOP

Before the article, asks lived in chat scrollback and half-remembered intentions; work started without a stated goal and finished without a receipt. After ratification the loop refuses unformed input — capture became a hard station, and the nightly file went from reconstruction to bookkeeping. A form has to state an acceptance check, so an ask that cannot be checked gets rejected at capture instead of dragging on.

§ THE INCIDENTS THAT WROTE IT
SPARK 004
SPARK 011
§ HOW THE APPS ENFORCE IT

Perse rejects unformed work at capture. CasaCommand writes chores as forms with owners. Pythia opens a form per deliberation.

02 · Verification over trust

RATIFIED 2026.3
§ THE RULE

Output is claimed; state is proven. A gate passes work only when a test ran and the result was inspected.

§ WHAT IT CHANGED IN THE LOOP

The verify station stopped accepting green checkmarks and started demanding evidence — tests run against the real system, state inspected, not reported. Confidence language ("should work", "looks right") was banned from gate criteria. Verify takes a few minutes longer per pass. I stopped starting mornings by reading a broken nightly report.

§ THE INCIDENTS THAT WROTE IT
SPARK 017 · 2026-02-18
Silent success is worse than loud failure.
SPARK 018 · 2026-02-21
Two sources of truth means one is always a lie.
SPARK 050 · 2026-06-27
The verify gate degrades at the divergence rate.
§ HOW THE APPS ENFORCE IT

Perse’s verify gate replays state before ship. CasaCommand marks a chore done only on evidence. Pythia requires independent voices to converge before a position.

03 · Gates relocate, never disappear

DRAFT — NOT YET RATIFIED
§ THE RULE

Remove a checkpoint and it reappears downstream — priced in incidents.

04 · Zero sparks is a healthy day

DRAFT — NOT YET RATIFIED
§ THE RULE

The ledger rewards boring. A quiet night means the doctrine held.

Articles 03 · Gates relocate, never disappear and 04 · Zero sparks is a healthy day are drafts: the rule is stated, the incidents and the record are not written yet. Each is one row in the doctrine table, so writing the row publishes the article.
← the floorthe spark ledger →