AI Founder Kit
Organizes the project.
Core modules
- Human Quick Start
- AI Start File
- Project Context
- Founder Decisions
- Task System
- Handoffs
AI Founder Operating System
Stop rebuilding your AI workflow from scratch. A file-based operating system for founders working with ChatGPT, Claude, Codex and AI agents — built from running a real production project.
You are not buying the models — you are buying the operating system around them: context, decisions, roles, routing, quality gates, handoffs and the next best action, across sessions and models.
Example role assignment — fully configurable, not a fixed ranking. Available models change over time. The system records these decisions; it does not access your AI accounts or monitor usage.
The problem
They lose context, decisions, task history, quality standards and coordination between different AI tools.
The system
One layer runs the project. The other coordinates the AI team. The operating system keeps them in sync.
Organizes the project.
FOUNDER_DECISIONS.md
PROJECT_STATUS.md
Both layers read and write the same current state.
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.
Three products
Organizes the project.
Core modules
Coordinates the AI team.
Core modules
Keeps both in sync.
Real workflow
Verified
What you actually get
Not a loose prompt collection: project context, routing, verification and handoffs work together as one operating workflow.
This is not a prompt pack — it is one connected operating system of project, routing, QA and handoff modules.
Activate a module — connections and short infos appear.
PROJECT_CONTEXT.md
Project Layer
Keeps the project goal, context and assumptions stable.
Included in: Founder Kit + Bundle
ACTIVE_TASKS.md
Project Layer
Shows what is being worked on right now and what comes next.
Included in: Founder Kit + Bundle
MODEL_ROUTING.md
AI Team Layer
Assigns tasks to the models and modes that fit them.
Included in: Orchestrator Kit + Bundle
QUALITY_GATES.md
AI Team Layer
Secures reviews and quality checks before the next step.
Included in: Founder Kit + Bundle
HANDOFF_LOG.md
Shared State
Preserves results and handoffs across sessions and models.
Included in: Founder Kit + Bundle
PROJECT_CONTEXT.md
Project Layer
Keeps the project goal, context and assumptions stable.
Included in: Founder Kit + Bundle
ACTIVE_TASKS.md
Project Layer
Shows what is being worked on right now and what comes next.
Included in: Founder Kit + Bundle
MODEL_ROUTING.md
AI Team Layer
Assigns tasks to the models and modes that fit them.
Included in: Orchestrator Kit + Bundle
QUALITY_GATES.md
AI Team Layer
Secures reviews and quality checks before the next step.
Included in: Founder Kit + Bundle
Keeps the project goal, context and assumptions stable.
Included in: Founder Kit + Bundle
Shows what is being worked on right now and what comes next.
Included in: Founder Kit + Bundle
Assigns tasks to the models and modes that fit them.
Included in: Orchestrator Kit + Bundle
Secures reviews and quality checks before the next step.
Included in: Founder Kit + Bundle
Preserves results and handoffs across sessions and models.
Included in: Founder Kit + Bundle
Shared operating state
Fictional sample project — no real people or companies. Real file excerpts on the product pages: Founder Kit Orchestrator Kit Operating System
What is actually inside
Each kit is a set of working files you add to your project. These are the actual filenames that ship in v1.0 — no screenshots of an app that doesn’t exist.
Project layer
START_HERE_FOR_HUMAN.md Where the project stands and the next best action. START_HERE_FOR_AI.md The first file an agent reads — context, rules, priorities. PROJECT_CONTEXT.md What/who/why and the constraints that frame decisions. PRODUCT_STRATEGY.md Positioning, scope and priorities. FOUNDER_DECISIONS.md Append-only decision memory, kept out of chat history. PROJECT_STATUS.md The verified current state. ACTIVE_TASKS.md Scoped tasks in flight, with allowed files and a definition of done. ROADMAP.md Phased plan of now / next / later. NEXT_BEST_ACTION.md A single, unambiguous next step. QUALITY_GATES.md The bar a change must clear to be "done". STOP_RULES.md Hard conditions under which work pauses instead of guessing. HANDOFF_LOG.md Append-only timeline of completed work. templates/ Task, handoff, decision, status, roadmap and QA report formats. AI team layer
START_HERE_FOR_HUMAN.md Human orientation for the coordination layer. START_HERE_FOR_AI.md Binding instructions an agent reads before acting. AI_ROLE_MATRIX.md Which AI takes which role, with separation of duties. MODEL_ROUTING.md How to choose a tool and model for a task. MODE_SELECTION.md The smallest reasoning mode that safely solves it. TASK_ROUTING.md How a raw task is shaped, scoped and sent. RESOURCE_POLICY.md Deliberate use of expensive modes. REPO_GATE.md Pre-change checks that protect the repository. WORKTREE_POLICY.md Isolating parallel work so agents do not collide. CONFLICT_PREVENTION.md Keeping parallel agents off the same files. HANDOFF_PROTOCOL.md How one agent passes verified work to the next. REVIEW_AND_VERIFICATION.md How results are reviewed and independently verified. ESCALATION_RULES.md When to escalate to a stronger model or a human. STOP_RULES.md When an agent must stop rather than continue. TASK_HISTORY.md Append-only trail of routed tasks and results. templates/ Implementation, research, review, QA, handoff and stop-report formats. Shared state
SHARED_FILE_MAP.md Single source of truth for every shared concept across both kits. INTEGRATION_FLOW.md The end-to-end loop that ties project and AI team into one motion. INSTALLATION.md One installation for both kits into the same project. examples/sample-project/ A small, fully filled-in project showing the whole loop once. PROJECT_CONTEXT.md A filled-in context for the fictional sample project. MODEL_ROUTING_DECISION.md One real model-and-mode routing decision. QA_REPORT.md One QA report with all gates passing. Product preview
What the files look like once they are filled in — limited excerpts from a fictional sample project, one on every product page.
Fictional sample project — no real people or companies.
The project context survives outside individual chats — every session and every AI tool starts from the same state.
All product previews: Founder Kit Orchestrator Kit Operating System
Compare
The Founder Kit runs the project. The Orchestrator Kit runs the AI team. The Operating System is the complete system that keeps both in sync.
| Capability | Founder Kit | Orchestrator Kit | Operating System Complete system |
|---|---|---|---|
| Project context | Included | Not included | Included |
| Decisions and roadmap | Included | Not included | Included |
| Tasks and handoffs | Included | Shared | Included |
| Quality gates | Included | Partial | Included |
| AI role matrix | Not included | Included | Included |
| Model routing | Not included | Included | Included |
| Repo / worktree safety | Not included | Included | Included |
| Review and verification | Not included | Included | Included |
| Integrated end-to-end loop Bundle only | Not included | Not included | Included |
| Sample project Bundle only | Not included | Not included | Included |
| Best for | Running the project | Coordinating the AI team | Both, kept in sync |
| Current status | Pre-release | Pre-release | Pre-release |
PRE-RELEASE — NOT FOR SALE. No prices are shown — the bundle is the recommended complete system, not a paid upsell here.
The difference
Prompts solve single interactions. An operating system holds everything around them.
Proof
The structure comes from running a real production project — including the parts that break.
Built from the operating system used to develop, audit and run a real production project. No fabricated users, revenue, logos or testimonials.
Buyer questions
Honest answers to the questions we would hear most often — before there is anything to buy.
Yes. The kits are provider-neutral: roles, routing and rules are written as Markdown files that you use with any AI model, assistant or editor. Nothing is locked to a specific provider, and no particular model is required.
No. The kits are structured Markdown files that you read, fill in and add to your project. Git helps but is optional. A text editor is enough.
The website is available in German and English — the actual product files and templates are in English. That keeps them usable with every AI tool and in any team.
A download: a ZIP archive of Markdown files that you use locally inside your project. There is no running online service, nothing is hosted, nothing phones home.
No. No account, no login, no cloud. The files belong in your project or repository — that is all.
No. A one-time purchase, no recurring usage fees, no consumption-based credits.
The Founder Kit organizes the project: context, decisions, status, roadmap, tasks and the next best action. The Orchestrator Kit coordinates the AI team: roles, model routing, working modes, repo gates, reviews and handoffs. One layer runs the project, the other runs the AI tools.
The AI Founder Operating System contains both kits plus the layer that keeps them in sync: the shared file map (SHARED_FILE_MAP), the end-to-end integration flow (INTEGRATION_FLOW), the upgrade path and a fully worked sample project.
Yes. The license allows use in an unlimited number of your own private and commercial projects, including adapting and restructuring the files for those projects.
Work you produce with the kit may be used for clients. The original kit files themselves may not be passed on, resold or distributed as a white-label product — including as a client deliverable.
All v1.x updates are included for v1 buyers; v2.0 and later major versions are separate products. Support is best-effort email support for installation and reproducible product defects — no consulting, no individual project advice, no customization, no guaranteed response time.
The later flow: confirm the payment, open the confirmation page, receive the download link, additionally get a delivery email, unzip the archive locally and start with START_HERE_FOR_HUMAN.md (or START_HERE_FOR_AI.md for your agent).
A typical first complete working cycle — set up the files, fill the context, run one task through the loop — takes roughly 25–35 minutes. It depends on your project and the AI tool you use, and it is an orientation, not a guaranteed result.
The products are in pre-release and not yet for sale. Purchase and pricing information follows at launch.
Product evolution
The two kits and their shared installation and handoff workflow.
SEO, quality and funnel workflows that measure and improve the work.
A neutral, white-label founder cockpit tying everything together — a separate future product under its own terms, not included in a v1 purchase.
Products are released in versions. Early adopters get the Foundation versions first. No finished SaaS is promised, and there is no countdown or artificial scarcity.