Idea: Evaluate "busflow-ceo" Repo Extraction
Status: PARKED — Deferred strategic decision with an explicit activation trigger. Origin: Relocated from TODOS.md (former §9 — Strategic — Repo Architecture) during a TODOS pruning audit (2026-05-11).
Concept
The monorepo contains strategic content (docs-hub, context-engine, presentations, architecture docs) alongside product code. Extracting a dedicated "visionary workspace" repo could provide:
- Fine-grained access control over sensitive strategic content
- A clean separation of product engineering from strategic tooling
- A space for agentic-driven development experiments without polluting the product repo
Extraction Scope
If triggered, extract studio/docs-hub, packages/context-engine, studio/presentations, and select docs/ content into a new busflow-ceo repo. The context-engine would serve as the API layer feeding documentation back into the product monorepo.
Trigger Conditions
Revisit when either:
- (a) the context-engine is battle-tested enough to serve as the documentation bridge back into the product repo, or
- (b) the team grows past ~5 people and role-based access control becomes a real need