Public knowledgebase and docs

The public site and docs should not tell different stories. Marketing can be shorter and sharper; docs can be deeper and more operational. Both should originate from the same reviewed knowledge about what Gwen does, what is live, and what is planned.

Public marketing should explain the promise: Intelligence That Works, Enterprise Intelligence for work, Personal Intelligence for life, living memory, missions, integrations, approvals, Work Budget, and outcomes.

Docs should answer implementation-level user questions: how to start, how Work Budget works, what Gwen can do today, how integrations are connected, what approvals mean, how memory is controlled, and how missions/artifacts are reviewed.

Research, product telemetry, customer questions, code changes, capability launches, and support patterns should generate proposed updates. Gwen can draft those updates, but public publication should remain reviewed.