Getting started

You don’t have to finish it

Documentation fails when it’s treated as a project — a big push that’s never quite done, so it never starts. This isn’t that. Nothing here has to be finished; it’s designed never to be. A partly-documented flow is already useful; a blank one isn’t.

1. Write what you know while you’re already in a flow — a sentence on a table here, a gotcha there. Don’t set aside a day for it.

2. Leave the rest empty. Undocumented objects are absent, not shown as red gaps to shame you into filling them.

3. Let drift tell you what needs attention: when the schema changes, the flag points at exactly what to revisit.

   The work comes to you in small, real pieces, instead of one big audit you never get to.