Deckwright / What compounds

What compounds

Last updated 2026-07-28 · v2 · the screenshots below are the operating product, photographed 2026-07-10 - a real board from Deckwright's own development, not staged material.

Software is never finished; it is between changes. Most AI tools optimize the build and leave nothing behind it: when the session ends, what remains is code and a transcript. The best agent control planes do better - an audit trail, a searchable archive of the work, sometimes a wiki distilled from the team's own discussion - but none of it is bound to the code, so the question that actually matters still has no stored answer. The intent, the decisions, the constraints, the rejected alternatives - the things the next change needs most - evaporate, and every future change begins by re-explaining the project to a fresh context window.

A Deckwright project accumulates instead. Work deposits its full record where it happened - at the board, at the stage, at the card - and every future change inherits it. This page shows what that deposit actually looks like on an operating board.

The board level

An operating Deckwright Mission Board named Broadside Bay showing 8 total stages and 40 total cards. A board-level Tech Stack contract panel sits above the stage list. Each stage - Foundations: Rules Contract, Event Harness and Authoritative-Server Contract; Networking and State Sync; Geometry, Fleet and Placement; Turn Loop, Silence Economy and Visibility - carries its own five-state progress stepper: Scoping, Ready, Working, Verify, Done. — An operating board: Broadside Bay, 8 stages, 40 cards. The Tech Stack contract lives at board level and is inherited by every stage and card below it. Each stage carries its own five-state progression (Scoping, Ready, Working, Verify, Done) and its own attached context. Stage 1 sits at Verify; stage 2 is Working; stages 3 and 4 are Scoping - a real project, mid-life.

The stage and card level

The Foundations stage opened on the same Deckwright board. The stage shows a Bench Proof control with three alignment states - Unverified, Misaligned, Aligned - currently Aligned, and a stage description reading: rules-as-data, deterministic command to state-delta-plus-events harness, and the anti-cheat contract. Below it, the Rules Contract card shows a two-phase pipeline - Context: Proposed, Investigating, Specified; Production: Task Board, Approved, In Progress, Verify, Live, currently Live - toggles for Auto Approve and Attest Existing Code, a completion record labeled Custody: Secretary to Captain, completed, reading All clear, dated June 18 11:01 AM, and a version history showing v1 Current. — Inside stage 1: the stage holds a live Bench Proof alignment state (currently **Aligned**) and its own scope description. The Rules Contract card below it shows the deposit in full: the two-phase pipeline run to **Live**, the participation dials (Auto Approve, Attest Existing Code), a signed completion record with named custody (**Secretary → Captain · completed · "All clear." · Jun 18, 11:01 AM**), and a version history. This card also carries 110 officer handoffs - the complete working record of every agent that touched it.

What this means for a team

The next change inherits. Change 41 on this board does not start from zero; it starts from forty cards of accumulated specification, decisions, and verification evidence, inherited down the board-stage-card chain.
The next person inherits too. Onboarding is reading the board, not interviewing whoever remembers. The custody records say who approved what, when, and on what evidence.
Audits read themselves. Every completed card carries its verification contract, its evidence, and a signed completion record. The question "why is the code like this" has a stored answer.
The code stays regenerable. Because the record is the durable layer, the code remains its current build - downstream, replaceable, and auditable against the intent that produced it.

This is what we mean when we say the conversation is not the deliverable and the pipeline is not a conveyor. What you buy with a Deckwright project is not just the software at the end. It is the accumulated, structured, inheritable understanding of that software - and it compounds with every card that crosses the board.