BusinessGovernance
Knowledge Base Strategy
Prox OS needs multiple knowledge surfaces because the audience changes:
Purpose
Prox OS needs multiple knowledge surfaces because the audience changes: founder, future team, AI agents, contributors, users, developers, operators, and public ecosystem partners do not need the same level of detail.
Layers
| Layer | Audience | Source of truth | Notes |
|---|---|---|---|
| Internal Team Knowledge Base | Founder, trusted maintainers, scoped AI agents | Git repository docs | Stores structured decisions, role specs, ADR/RFC notes, AI decision summaries, runbooks, and operating models. |
| External Public Docs | Developers, users, community | Docs app / public docs | Explains app model, SDK direction, public roadmap, contribution paths, and safe platform concepts. |
| GitHub Repo Wiki | Community collaborators | GitHub Wiki or Discussions | Good for lightweight FAQ and community notes; not architecture source of truth. |
| Internal API Docs | Internal systems, admin, ops, agent workers | API docs behind Access or org auth when implemented | May include admin-only routes, scopes, and operational notes. |
| Public API Docs | Developer ecosystem | OpenAPI / Scalar generated from API contracts | Public API surface only, with examples and stable contract notes. |
| AI Control Plane Records | Maintainers and AI workers | docs/development/ai-control-plane | Stores curated summaries, task graphs, run logs, integration reports, and prompt templates. |
What Belongs In Repo Docs
- Durable decisions.
- Role specs.
- Architecture boundaries.
- Roadmap status.
- Task graph templates.
- Reusable prompts.
- AI run summaries.
- Public or sanitized operating notes.
What Does Not Belong In Repo Docs
- Raw long chat transcripts.
- Private prompt streams that contain sensitive context.
- Secrets, tokens, account IDs, billing details, private financial records, or personal legal documents.
- Unreviewed speculation presented as current capability.
Public vs Internal API Docs
Internal API docs may include admin routes, audit boundaries, and agent worker use cases. Public API docs should be generated from implemented OpenAPI contracts and should not expose internal control-plane routes before they are ready.