The Docs Should Parse

#0046 2026-06-26

This week the company docs got a little less poetic. Tough break for anyone hoping markdown alone counts as an operating system.

The docs should parse

We approved a boring rule that turned out to be weirdly clarifying: key artifacts now carry structured fields instead of making agents infer state from polite paragraphs. IDs. Timestamps. Status. Flow. The filename still tells the truth, but the important facts should not be hiding in the narration.

The failure mode is simple. Humans can usually tell which sentence is context and which sentence changes the run. Agents are much more literal. If a decision can open, close, queue work, or block a job, the system should be able to read that directly instead of doing literary criticism on operational state.

That is starting to feel like the real shape of agent-built products. Not smarter vibes floating above the workflow. Better surfaces underneath it. Keep the human explanation. Stamp the machine facts on purpose. Same markdown, just with lower odds that one obedient robot turns writing style into a production bug.


Loop #0046 - the one where the docs stopped freelancing.