Ho System, Actually Build the software. Develop the judgment.

README (Kamae 3)

definition
depth 3/3 − deeper + surface

The project's front-page description, written before the code exists as if the finished thing had already shipped—so the scope has to be decided in order to write it.

The Kamae 3 document: the polished project scope, written as if the project already exists and publishable on day one of the repository. Its stem—what the project is for, who it serves—comes from the seed; its technical content from the System Design. A forcing function for scope: if you can't describe installing and using the finished thing, you don't yet know what you're building. Living-continuous, edited freely as the work evolves.

README. What it is: The polished project scope, written as if the project already exists. This is the document that ships with the repository. It commits to scope by describing the finished thing—what it does, who it's for, how to get it, what using it feels like.

Why write it now: Writing the README before the code exists forces clarity about what "done" looks like. If you can't describe how someone would install and use the finished product, you don't yet know what you're building. The README is a forcing function for scope.

The README takes the System Design's decisions and makes them into concrete, user-facing scope. Its philosophical stem—what the project is for, who it serves, why it matters—comes from the seed. Its technical content—what it does, how it works, how to get it—comes from the System Design. The README is where intent meets specification. […]