How-to — look it up by what you want to do
For someone who has written .muro once and now wants a particular thing done. Not a book to read from the top. If you have never seen the notation, work through Your first .muro first.
Every page has the same three parts: what it assumes, the steps, and how to check. Definitions of the words used in the steps live in the reference.
Writing a building
| What you want | Page |
|---|---|
| Add a second storey | Add a storey |
| Join storeys with a stair, void or shaft | Connect storeys |
| Divide a dwelling into rooms | Subdivide a unit |
| Write repeated floors once | Typical floors |
| Open windows and satisfy daylight | Windows and daylight |
| Find rooms with no way out | Find unreachable spaces |
| Describe a site and get coverage and FAR | Describe a site |
| Split one building across files | Split into layers |
| Keep a reference alive across a rename | Survive a rename |
| Lay measured reality over the plan | Write as-built |
| Decide what appears in the area schedule | Counted and uncounted divisions |
| See what a dimension you wrote decides | What koyu derives from the dimensions you write |
Running the tools
| What you want | Page |
|---|---|
| Let an agent reach koyu | Install the MCP server |
| Have an agent write the building | The agent loop |
| Check the MCP responses by hand | Debug MCP over stdio |
| Read a building from your own program | Embed koyu in a program |
| Inspect space allocation before boundary decisions | Start with a spatial model |
| Edit this documentation | How this documentation is written |
When you are stuck
| Symptom | Page |
|---|---|
| An error appeared and you do not know its code | Look up a diagnostic by symptom |
| You want the common traps up front | Common trouble |
| You already have the code | Diagnostic code index |