sb-steeringlisted

# Maintain durable project guidance ## Apply project language style Before authoring any artifact or user-facing prose, read: ```sh specbind rule read language-style --for consume ``` Apply returned policy only to natural-language prose. `NO_CHANGE RULE_ABSENT` means no additional project preference; any `ERROR` line stops the workflow. Steering carries what outlives any single change: how this project is built, what it values, and the constraints every change inherits. You author it. The CLI owns discovery and identity. Nothing else in SpecBind depends on this running, and nothing invalidates when it does — steering is never gate evidence and editing it approves nothing. That cuts the other way too: **`sb-discovery` reads the whole collection and routes work on it**, so a document that has quietly gone out of date misroutes real work. Guidance you are not confident is still true is worth removing. ## 1. Confirm what you are doing Three things can be asked for, and they are not interchangeable: | Intent | What it means | | --- | --- | | **Bootstrap** | The project has no steering, and wants a first set | | **Synchronize** | Steering exists and the codebase has moved past it | | **Add** | One new subject deserves its own document | Ask when the request does not say. The current inventory is input to that conversation, not the answer to it: **an empty `steering/` is a valid steady state**, not a prompt to bootstrap. A project that decided it does not want steering sho