Bundle · Run both as one system
AI Founder Operating System
The Founder Kit organizes the project. The Orchestrator Kit organizes the AI team. The Operating System keeps both synchronized.
Project System
Organizes the project.
FOUNDER_DECISIONS.md
PROJECT_STATUS.md
Shared State
Both layers read and write the same current state.
- synchronized
- current
- verified
- versioned
AI Team System
Coordinates the AI team.
AI_ROLE_MATRIX.md
HANDOFF_LOG.md
Select a module to see its connection through the shared state.
Activate modules with mouse or keyboard — the matching connection lights up.
Comparison
What each layer covers.
| Capability | Founder Kit | Orchestrator Kit |
|---|---|---|
| Project context & decisions | Included | — |
| Task templates & handoffs | Included | Shared |
| Roadmap & project status | Included | — |
| AI role matrix & routing | — | Included |
| Reasoning mode selection | — | Included |
| Repo gates & worktrees | — | Included |
| Stop rules & escalation | Partial | Included |
| Context synchronization across both Bundle only | — | — |
Context synchronization across both layers is what only the bundle provides.
Shared installation
One installation, one workflow.
Both kits install into the same project and share START_HERE files, task formats and handoff conventions, so there is a single source of truth rather than two parallel systems.
How the files cooperate
Which files work together.
- Founder Kit
Project Statusfeeds the Orchestrator Kit’s task routing. - Founder Kit
Founder Decision Logconstrains which models and actions are allowed. - Orchestrator Kit
Handoffswrite back verified results into project status. - Orchestrator Kit
Stop Rulesreference project QA gates before continuing.
What the bundle adds
The files only the bundle ships.
On top of both kits, the Operating System adds the layer that keeps them synchronized — plus a fully worked example. Real filenames; no file contents reproduced, no download yet.
Bundle layer
-
SHARED_FILE_MAP.mdSingle source of truth for every shared concept across both kits. -
INTEGRATION_FLOW.mdThe end-to-end loop that ties project and AI team into one motion. -
INSTALLATION.mdOne installation for both kits into the same project.
Worked example
-
examples/sample-project/A small, fully filled-in project showing the whole loop once. -
PROJECT_CONTEXT.mdA filled-in context for the fictional sample project. -
MODEL_ROUTING_DECISION.mdOne real model-and-mode routing decision. -
QA_REPORT.mdOne QA report with all gates passing.
Real preview
One complete task loop — filled in.
From decision to the new next best action: one pass from the sample project, step by step.
- Founder decision DR-0001: one question instead of a survey — with an optional comment
- Next best action Add the comment field — the smallest step that delivers the decision
- Scoped task TASK-001 with allowed files and a protected data schema
- Model + mode Implementer role, “Normal” mode — the smallest safe mode
- Repo gate 6/6 checks passed — own branch, clean state
- Implementation Optional comment field added; an empty comment stores nothing
- QA 7/7 gates passed — verified by a different role
- Handoff Recorded on both the agent and the project level
- Project status The verified state replaces the old one — nothing is lost
- New next best action Test five real appointments before building more
Fictional sample project — no real people or companies.
What you download
Format & installation.
How the product will arrive — no app, no account, no cloud.
- Download format
- ZIP archive
- Core format
- Markdown files and templates
- Language of the product files
- English — the site is bilingual, the kit files themselves are English
- Installation
- Copied locally into your project / repository
- Account required
- No — no cloud, no running online service
- Subscription
- No — a one-time purchase, no recurring fees or credits
- Updates
- All v1.x updates included; v2.0 is a separate product
- Support
- Best-effort email support for installation and reproducible defects
Bundle-only value
Problems only the bundle solves.
- Project state and AI coordination stay in one synchronized loop.
- A decision logged on the project side immediately informs routing on the AI side.
- Handoffs reference both the project status and the agent rules at once.
- One installation, one source of truth, one continuing workflow.
Roadmap to the cockpit: the bundle is the foundation the future v2.0 Founder Cockpit builds on.