Research, frameworks, and product thinking. This is where ideas live before they become requirements. Nothing here is a spec. Nothing here is a ticket.
Each page documents the thinking behind a feature or system — the why, the tradeoffs, the open questions. When thinking matures into requirements, a Feature Spec is written and linked here.
Every feature has up to three artifacts:
| Layer | Location | Purpose |
|---|---|---|
| Thinking | This section (PKB) | Research, frameworks, dialogue, open questions |
| Requirements | Feature Specs database | Distilled spec — what gets built and why |
| Execution | Agent: Dev page | Ticket — status, blockers, link to spec |
Flow: Thinking matures → COO writes Feature Spec → Spec locks → COO writes ticket. No layer duplicates another. Tickets link to specs. Specs link to PKB pages.
Onboarding — Personalization Framework
Opportunity Solution Map — Opportunities