go-to-market — the motion stone

Most businesses have three separate half-written playbooks: marketing lives in someone's head, sales lives in whoever closed the last deal, and customer success is whatever got typed into the last apology email. They drift apart because nobody made them cite the same customer, the same voice, the same numbers. This stone binds them into one document. It reads what upstream already locked — the personas and objections from customer-blueprint, the claims and voice from messaging, the metrics from business-model — and composes the playbook that spends them: which channels get money and which get refused, how a lead becomes a customer, and how a customer stays one. It ships as a Business OS module: canonical GTM.md, machine contract, the leads and campaigns tables, MCP server, standalone site.

This is stone 6 of 8. Read ../PROTOCOL.md before composing — the module contract, workspace layout, and definition of done live there and are not repeated here. Upstream reads: messaging, business-model, customer-blueprint. Extract from them instead of re-asking; when one is missing, flag it loudly and mark the dependent sections provisional.