AI Orchestrator FAQ: purchase, download and use

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. A single AI tool is enough to start — the files and rules are provider-neutral. You add a second or third tool only if you need more independent review, more capacity, an outage buffer, or genuinely parallel work.

Yes. With one tool you run the roles in turn — research, plan, implement, and review in a fresh pass. You don’t need a paid API plan; a normal account is enough.

Two Claude can be an excellent, complete setup: same interface, shared conventions, more capacity, and real parallel work in separate worktrees. A tool mix only becomes more interesting when you deliberately want stronger role separation, a more independent second opinion, or a buffer against one provider’s limits and outages. It’s a deliberate trade-off — not a verdict that two Claude is ‘doing it wrong.’

No. A prompt pack is a collection of snippets. Here you get a connected way of working made of local Markdown files: project context, agent briefings, QA and release gates, protected areas and handoffs fit together — vendor-neutral and reusable across sessions and models.

The free guides explain the principles — briefings, model choice, QA, handoffs — and stay fully usable without a purchase. The package adds the reusable working material: fillable briefing and QA templates, protected-area and handoff structures, and a fully worked example project, so you do not rebuild the system by hand from every guide.

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 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.

No. The Operator Bridge is meant as a local companion tool around the workflow and runs on your own machine. This page explains the way of working — it does not host a service and it is not a file inside the product ZIP.

No. The idea of the Bridge workflow is the opposite: reports are sanitized, and secrets such as API keys or tokens stay local and are not copied into the report you hand to Claude or Codex.

No. There is no promise of unattended auto-deployment. Release steps run through gates that require explicit human confirmation — especially for anything that touches money or production.

No. The Founder SEO Tool produces an analysis and concrete next steps — priorities, risks and a copy-paste handoff for your agent. It checks more than meta tags, but it promises no rankings and does no automatic Google indexing.

No. The paid ZIPs today contain documents, templates and workflows — no app and no dashboard. Local tools like the Operator Bridge or the Founder SEO Tool belong to the broader operator system and the add-on direction, but they are not automatically in the download.

Because the package is built around a founder/operator workflow. The Operator Bridge demonstrates and supports that workflow locally — it explains the way of working, but it is a separate, local tool and not a file inside the product ZIP.

Yes. The documents, templates and workflows are usable on their own — with any AI tool and entirely without the Bridge. The Bridge is an optional local companion tool, not a requirement.

No. The Founder SEO Tool is an operator/demo workflow surface, not part of the purchased ZIP. It helps turn a page into an agent brief — with no ranking promise.