This records why the Knowledge Site (this Control Centre) was created. For the technical build history, see Mission Control & Control Centre Development.
Reasons
- Chat conversations becoming too large to work in effectively.
- Important decisions being difficult to relocate once buried in long conversation history.
- Context loss between long sessions.
- Need for a permanent project memory that doesn’t depend on any one conversation surviving.
- Need for a single authoritative source of truth, rather than knowledge scattered and duplicated across sessions.
- Independence from any individual AI session – the knowledge should outlast any specific chat, model, or provider.
What it became
The Knowledge Site became the project’s canonical knowledge repository – the place where decisions, technical knowledge, and strategy live permanently, rather than a project-management tool that sits alongside a separately-remembered history. See Mission Control & Control Centre Development for how it was actually built, and “Project Knowledge Must Be Independent of AI Memory” for the decision that formalised this.