docs(gtm): record the model-to-production thesis, checked against the repo

[unfoundbox]

What

• docs/gtm/model-to-production-thesis.md (new): records the 2026-10-02 session summary. One-line description: autonomous model-to-production infrastructure. Business model: open core plus inference engineering as a service. It covers the architecture loop, the Qwen / p95 < 300 ms wedge, the GTM, and the plan to turn job descriptions into evals.
• It sets this beside the same-day "local lane for your coding agent" recommendation. Both use the same core but aim at different buyers.
• It maps each thesis layer to what exists on main at 9bc8a2d. The registry, receipts, MCP server and a sweep harness seed (sweep.py) exist. The registry has no vLLM, SGLang or TensorRT-LLM entries and no datacenter-GPU measurements. The planner, docks and providers are zero code.
• It names the hardware ceiling. The quota allows one g6e.2xlarge, so one L40S. An H100 comparison needs a quota request or a box rented elsewhere.
• docs/DECISION-INBOX.md: a new entry asks which buyer leads, the developer's local lane or the team that needs inference owned.

What this does not do

It leaves VISION.md, the README and the landing page unchanged. They wait on the decision above.

🤖 Generated with Claude Code

https://claude.ai/code/session_011TqzXL1YTm2Dk55TQyk1JS

---

Generated by Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
spacepilot	Error		Oct 2, 2026 10:03am UTC
spacepilot.dev	Error		Oct 2, 2026 10:03am UTC

[unfoundbox]

The red Vercel – spacepilot status isn't from this PR. The PR only adds two Markdown files under docs/. The same status failed on the head of #183, which merged on 2026-09-25 (25e7c4e). The Vercel spacepilot project has no rootDirectory set (the landing site deploys from landing/ through the spacepilot.dev project), so its failure looks like a project-settings problem, not a code one. I haven't read the deploy logs, so that isn't confirmed. Nothing in the repo fixes it yet. The likely fix is in Vercel: delete or disconnect that project, or point it at a real root. The GitHub Actions workflows (pytest, packaging, security) didn't run on this PR because its diff only touches docs.

---

Generated by Claude Code