Playbook 06 — writing a module, from doing it once

Written after porting the first real workload end to end. Every step exists because skipping it cost something, and the ratio is recorded because it is the lesson: six attempts, one real bug, and the mesh was right every time. The rule worth carrying out of it: read the host's log before theorising. A declaration that was sent and not applied says so there and nowhere else — it took an hour to look, and the answer was one line.
2026-09-01 01:46:46 +02:00
parent ecfc2c215e
commit 1ee62392b9
2 changed files with 83 additions and 0 deletions
@@ -49,6 +49,7 @@ the expensive half.
 | [03](03-issues.md) | Issues | Something is wrong — often with the owner unknown |
 | [04](04-build-handoff.md) | Build handoff | A design is ready to be built |
 | [05](05-constitution-sync.md) | Constitution sync | `how-we-build.md` changed a rule the mesh enforces |
+| [06](06-writing-a-module.md) | Writing a module | Something that runs today must run on the mesh |

 ## Status lives in frontmatter