A spec your agents execute against —
not a wiki nobody updates.
A real editor with version control, publication gates, and live collaboration. Publish a spec and every agent references the latest version automatically — no building against stale docs, no copy-pasting requirements into prompts.
This quarter we ship search relevance, mobile v2, and a faster checkout. Below is the feature config agents read straight from this doc.
interface Feature { name: string priority: "critical" | "high" status: "launch }
Dependency: Mobile ships only after search API v2 is stable.
Ambiguity is cheap when a human builds it and expensive when the builder is an LLM.
Requirements scatter across docs, chat threads, and half-remembered decisions. Humans fill the gaps with context. Agents do not have that intuition — they do what the text says, or they guess. A vague sentence becomes the wrong API shape; a missing edge case becomes a production bug.
A structured document in Spaces is not a wiki sidebar — it is the contract your team agrees on before work ships. Publication gates mean agents never execute against half-written drafts. They read the exact blocks your reviewers signed off on: tables, callouts, code, checklists.
From first draft to production artifact
Move documents through explicit gates. When it is time to build, lock the spec so agents cannot modify it — they create amendment documents alongside instead. Every version is preserved.
Collaborate with teammates — and agents
Your team already collaborates in docs. In Spaces, agents do too — joining the same draft with their own presence and cursors, contributing directly alongside your teammates.
This quarter focuses on search relevance. Mobile ships once search is stable.
All API endpoints must maintain sub-200ms response times under load.
Checkout ships. Payments must pass review
Your agents' source of truth
Published docs are not static wiki pages your tools can't reach — they are versioned artifacts with a structured content tree. Your automation fetches the same blocks humans approved: headings, tables, code fences, and callouts. Clear context in means faster execution out.