Five OS designs, five ways to organize work.
Look inside five OS designs. Explore the roles, follow the dependencies and find where your judgment enters the workflow.
Builder and Decision are design blueprints. Content, Growth and Librarian diagrams show their package workflow definitions, not a live execution. See the current catalog for available features and setup.
Builder OS
Build the team your ambition deserves.
An operating system begins with understanding the work. The Builder blueprint connects your brief to research, system design, specialist teams and a reviewed package.
Design blueprint
The system starts with you.
A useful AI team begins with a specific outcome. Your host carries the conversation; your brief sets the purpose, the constraints and the decisions you want to keep.
- The result you want
- The boundaries that matter
- A shared definition of done
Builder OS · Public architecture concept
- Domain brief
- Team architecture
- Workflow design
- OS package
You approve the brief and system design before moving further.
Decision OS
Give a consequential decision more than one perspective.
Five independent analyses examine the same evidence. A red team challenges their conclusions before synthesis brings the trade-offs into one decision memo.
Research blueprint
Scroll the diagram horizontally to see every step.
Frame
This specialist develops its contribution from the inputs defined in the workflow.
- Receives
- Your brief
- Hands off to
- Research
- Context
- Defined by the OS and your host
- Read the map
- Connected steps show dependencies. Steps on the same level can contribute independently.
- Evidence base
- Five analytical lenses
- Red-team challenge
- Decision memo
The workflow informs your judgment. The decision remains yours.
Content OS
Carry a strong idea all the way to your audience.
An editorial line with a role for every stage: discover the angle, write the story, refine the assets and review the work before distribution. Each handoff has a purpose.
Researcher
This specialist develops its contribution from the inputs defined in the workflow.
- Receives
- Your brief
- Hands off to
- Strategist
- Context
- Defined by the OS and your host
- Read the map
- Connected steps show dependencies. Steps on the same level can contribute independently.
- Editorial brief
- Draft & edits
- Prepared assets
- Your publication decision
Actions depend on your host, configured connections and permissions. Review the result before authorizing external effects.
Growth OS
Connect the strategy. Then choose your next move.
Strategy, editorial, distribution, revenue and learning work from shared intelligence. Explore three connected methods for your marketing foundation, brand system and next campaign.
Scroll the diagram horizontally to see every step.
Intake
This specialist develops its contribution from the inputs defined in the workflow.
- Receives
- Your brief
- Hands off to
- Intelligence
- Context
- Defined by the OS and your host
- Read the map
- Connected steps show dependencies. Steps on the same level can contribute independently.
- Marketing foundation
- Brand system
- Campaign strategy
- Reviewed recommendations
Actions depend on your host, configured connections and permissions. Review the result before authorizing external effects.
Librarian OS
Follow an insight back to its source. And forward to its use.
Research is more than gathering links. Source access, close reading, evidence review and synthesis form a traceable path to knowledge you can understand, question and reuse.
Research Planner
This specialist develops its contribution from the inputs defined in the workflow.
- Receives
- Your brief
- Hands off to
- Teaching Style · Source Scout
- Context
- Defined by the OS and your host
- Read the map
- Connected steps show dependencies. Steps on the same level can contribute independently.
- Deep research
- Book intelligence
- Learning paths
- Knowledge for another OS
Actions depend on your host, configured connections and permissions. Review the result before authorizing external effects.
Your work has its own logic.
Your AI team should, too.