Docs
Public knowledgebase and docs
How Gwen's marketing, docs, news, and in-app guidance should come from the same evolving knowledge system.
One source of truth
A product that says one thing in its marketing and another in its docs erodes trust at exactly the moment someone is deciding to rely on it. Gwen's public site and its knowledgebase are meant to tell the same story.
Both originate from the same reviewed knowledge about what Gwen does, what setup a job may need, and how work is governed. Marketing is the shorter, sharper version; docs are the deeper, more operational version — not a different message.
Marketing and docs play different roles
The two surfaces serve different moments. Marketing is for the person deciding whether Gwen is worth their attention: the promise, the difference, the outcomes. Docs are for the person who has decided and now wants to know exactly how it works.
Keeping them aligned but distinct means neither has to compromise — the pitch stays crisp, and the detail stays thorough.
What belongs where
Public marketing carries the promise: Intelligence That Works, Enterprise Intelligence for work, Personal Intelligence for life, living memory, missions, integrations, approvals, Work Budget, and outcomes.
Docs answer the implementation-level questions: how to start, how Work Budget works, what Gwen can do, what setup a job may need, how integrations connect, what approvals mean, how memory is controlled, and how missions and artifacts are reviewed. When in doubt, the promise goes to marketing and the mechanics go to docs.
How the knowledgebase evolves
This knowledgebase is meant to be living, not frozen. Research, product telemetry, customer questions, code changes, capability launches, and support patterns all generate candidate updates.
Gwen can draft those updates as part of running itself — but public publication stays reviewed. The result is documentation that keeps pace with the product without drifting into claims no one checked.
Why this matters to you
For you, the payoff is documentation you can trust and that stays current. What you read here is intended to match what the product actually does, reviewed before it is published.
It is also a demonstration of the product itself: a knowledge system that is created, maintained, and improved by the same intelligence — and the same approval discipline — that you can put to work in your own workspace.