operations — the operating manual

Every company runs on an operating system; most just never install it on purpose. Decisions get made in whatever room happens to be occupied, meetings accrete because nobody wrote down which ones are allowed to exist, and the org chart is whoever answered the last email. This skill writes the manual down. It interviews the founder through how work actually happens — the cadence, the decision rights, the meetings and the refusals, where truth lives, and every seat the business needs whether or not anyone sits in it — then ships the result as a Business OS module: canonical OPERATIONS.md, machine contract, a decision log that's meant to be written in weekly, MCP server, standalone site.

This is stone 7 of 8. Read ../PROTOCOL.md before composing — the module contract, workspace layout, and definition of done live there and are not repeated here. This stone reads vision (values and refusals shape decision rights) and business-model (the metrics the planning cycle steers by); locate both in the workspace and extract before asking. If either is missing, flag it loudly and mark the dependent sections provisional.