Expert · Lesson 04 — Accountability — contracts + postmortems + gates as one system
E04Expert
Expert · Lesson 04● live

Accountability — three disciplines as one system

Sprint contracts, postmortems, and pre-flight gates only compound when they reference each other. The integration is the lesson.

18 min read · 45 min applyprereq: Operating 01, 02, 04

Session slides

The Integrated Accountability Loop
01The Integrated Accountability Loop
Human memory cannot sustain structural safety
02Human memory cannot sustain structural safety
Mechanical integration over discipline
03Mechanical integration over discipline
Three disciplines become one compounding safety net
04Three disciplines become one compounding safety net
Sprint contracts pre-register the exact definition of done
05Sprint contracts pre-register the exact definition of done
Contracts must translate into mechanical gates
06Contracts must translate into mechanical gates
Pre-flight gates act as the un-bypassable enforcement layer
07Pre-flight gates act as the un-bypassable enforcement layer
Fired gates carry historical context and trigger evaluation
08Fired gates carry historical context and trigger evaluation
Postmortems evaluate structures, not human discipline
09Postmortems evaluate structures, not human discipline
Action items ship as mechanical rules, not promises
10Action items ship as mechanical rules, not promises
Postmortems mechanically strengthen the original contract
11Postmortems mechanically strengthen the original contract
The compounding effect of mechanical integration
12The compounding effect of mechanical integration
The empirical proof of the integrated loop
13The empirical proof of the integrated loop
The Integrated Workflow Blueprint
14The Integrated Workflow Blueprint

Three disciplines, one system

I think most people who adopt sprint contracts, postmortems, and gates run them in isolation. Each one does some useful work on its own. None of them catch the failure modes of the others, which is the part I missed for a long time.

Compounding starts when they reference each other. Contracts produce gates. Postmortems strengthen contracts. Gates carry context from postmortems back to runtime. Each layer covers what the others miss, and the three practices stop being separate and start being one loop.

The integration is mostly mechanical. A contract criterion ships as a gate. A postmortem action item ships as a gate or a contract criterion. A gate that fires links back to the incident or the contract that produced it. None of this needs new tools. It needs every artifact in one layer to have a matching artifact in the others.

Where the three disciplines catch each other

Compounding works because each discipline catches what the other two can’t. The table below is the entire integration in one view.

DisciplineCatchesMisses (caught by next discipline)
Sprint contractsScope drift, missing acceptance criteria, ambiguous “done”Failure modes not enumerated in the template — caught by postmortems
PostmortemsStructural causes of failures, gaps in contract templatesAction items that don’t ship — caught by gates / mechanical layer
Pre-flight gatesMissing checks at runtime, bypassed disciplinesGate criteria that aren’t in the contract — caught by next contract’s template review

The cycle closes. Gates catch what postmortems missed. Postmortems strengthen contracts. Contracts produce gates. Without all three, one failure mode leaks through every time.

Subscribers only · continued

The rest of Expert · Lesson 04 is for subscribers.

Accountability — contracts + postmortems + gates as one system

  • Every Expert-tier lesson — diagnostic prompts, transcripts, prompt kits, full homework
  • Every research paper — methodology, figures, tables, reproducibility appendices
  • New Expert lessons + papers as they ship (quarterly cadence)
  • Foundations + Operating lessons stay free; bundles on GitHub stay free; this tier is the deep stuff

Free while the early catalog ships. Paid tier comes later — subscribe now and you’re grandfathered in.