Core spine: from trigger to boundary
The log follows this sequence:
trigger → why it mattered → constraint → decision → implementation → result → what changed → boundary
For your Operator Stack work, an even tighter formulation is:
doctrine → mechanism → scar → decision artefact
The doctrine names the operating belief. The mechanism explains how it works. The scar shows the reality that made the belief costly to learn. The decision artefact lets another operator see what changed in practice.
Evidence: numbers, sequence, and artefacts
Use numbers, sequence, system behaviour, before-and-after state, thresholds, and screenshots or artefacts where relevant.
Replicability: name the hidden dependencies
State starting conditions and hidden dependencies. Do not present a one-off relationship or lucky timing as a repeatable process.
Opening: what broke and what it forced
Say what broke, why it mattered, and what decision it forced.
Ending: a rule, a limit, or a next test
End with the new operating rule, the remaining limitation, or the next test. Avoid motivational morals.
Main risks
Watch for these failures:
- a post-hoc hero story
- blaming a person for a system incentive
- a generic lesson detached from the scar
- omitting failed attempts
- jargon replacing process
AI role: map and audit the process
Process mapper, contradiction finder, missing-step auditor, technical editor.