Builder doesn't just create prompts. It compiles an operational system.
A prompt tells a model what to say. It does not say who decides, which tool is allowed, what gets checked or what happens when a step fails. Builder answers those questions first, then compiles the answers into one package.
01 Structure
A prompt is advice. A system is structure.
You can read the package, install it and version it.
Not a bundle of prompts. An organization, compiled.
A compiled OS is one folder, growth-os/, holding its organization, agents, skills, programs, workflows, tools, memory, knowledge, data, views, policies, evals and lifecycle.
02 Contents
Everything an OS can hold.
- Organization
- Directors, specialist teams, agents and skills. Directors own the mission, teams group agents by the part of the work they own, and each agent follows written skills.
- Work
- Programs and workflows. Programs run the steps that must not guess, workflows are versioned graphs, and runtime rules set the budget, timeout, retry and escalation of every step.
- Reach
- Tools, MCPs, APIs and CLIs, declared by capability rather than by vendor and bound by you. Agentik is the MCP server your host calls.
- Context
- Memory, knowledge and databases. Memory is scoped per project and per mission, knowledge carries a freshness and a licence rule, and databases hold typed records, private by default.
- Control
- Permissions, model routes, evaluations and approvals. Each agent stores a need, not a model name, external writes wait for a human, and recovery and rollback are written into the package.
- Surface
- Interfaces and views: dashboards, tables and org charts, each with its data, its actions and its permission.
03 Compiled
Compiled means it is checked.
A package that does not hold together does not compile.
Every schema must validate, every reference must resolve and every workflow graph must compile without a cycle.
Three checks travel with the package: structure blocks, quality asks for repair, safety needs a human.
04 Packages
Five packages. One contract.
Every official OS is compiled against the same contract. A mission activates the subset of agents it needs.
- Content OS
- nine agents in six teams, pinned to version 0.1.0.
- Growth OS
- forty-eight agents in ten teams, pinned to version 0.1.0.
- Librarian OS
- twenty-five agents in seven teams, pinned to version 0.1.3.
- Decision OS
- ten agents in nine teams, pinned to version 0.1.0.
- Builder OS
- twenty-one agents in twenty teams, pinned to version 0.1.0.
05 From brief to package
Describe the need. Approve the design. Keep the OS.
- 01
Need
You describe what the system must accomplish, for whom, and how you will know it worked.
- 02
Research
Builder researches the domain and cites every source it read.
- 03
Architecture
It proposes the organization: Director, teams, agents, methods and gates.
- 04
Your approval
You review the design in your browser before anything is compiled.
- 05
Compile
Builder compiles a private package and runs its checks.
- 06
My OS
The OS stays in your account, ready for its first mission.
06 Atlas
The Atlas of 10,000 systems.
The Atlas maps 10,000 systems an organization could install, across sectors, business functions and mission types.
A model scored each one to rank what to research first. The scores compare ideas; they are not customer results.
Vote for the one you need. Votes decide what Builder researches first.
07 Principles
What Builder will not claim.
A long list of parts is not quality, and a compiled package is not a proven one.
No invented metrics. No unread sources. Run evidence is published when it exists.