A 3D scene for the law of How The Forge Writes

Law 14 · How The Forge Writes

Documents tell the shape of the work, never the listing of it.

The Mossy Dekalogue · Law 14 of 14 · decreed 2026-11-02 by FiremanDeckoNo file or directory listings in documents — prose and mermaid diagrams only. Architecture documentation runs on bullet points and mermaid diagrams, many visual diagrams from architecture down to implementation. Paragraphs stay brief, every architecture document opens with an exec summary, and architecture locks down the immutable, hard-to-change decisions — the agents figure out implementation details.

A file listing is a map of a moving country: true the day it is drawn, a lie the week after, and no one tends it. So the documents of the garden carry neither listings nor ledgers of paths — prose tells what the work means, a diagram shows how it flows, and both are drawn from the roof of the architecture down to the floor beams of the implementation. Bullets and mermaid are the staples, paragraphs stay brief, and every architecture document opens with an exec summary, so the reader at the gate learns the shape of the thing before walking through it.

And the writing stops where the stone stops. Architecture locks down the immutable, hard-to-change decisions — the ones that cost blood to revisit — and the agents figure out implementation details on the ground, where the watching is close. The immutable is carved; the rest is grown.

Forbiddenfile and directory listings in documents — they rot the day after they're drawn
Staplesbullet points and mermaid diagrams — many visual diagrams, from architecture down to implementation
Openingsevery architecture document opens with an exec summary; paragraphs stay brief
Division of laborarchitecture locks the immutable, hard-to-change decisions; the agents figure out implementation details

ᚔ back to the Dekalogue · back to the forge