Give your project a goal. Watch it ship.
A Factory turns your goal into durable work. It runs your agents on your machine, verifies the results and remembers what happened. The cockpit shows the whole day as one river.
A project that continues after the conversation.
Claude Code, Codex and Grok do the work inside a Factory. The Factory keeps the goal, the work, the evidence and the history between sessions.
| AGENT SESSION | /GOAL · /LOOP | ORCHESTRO | |
|---|---|---|---|
| Keeps working toward a goal | No | while the session runs | ✓ across sessions |
| Work survives the session | No | No | ✓ durable backlog |
| “Done” is checked independently | No | self-assessed | ✓ separate check |
| Another worker takes over | No | No | ✓ with a receipt |
| Finds new work when the backlog is empty | No | No | ✓ Advisor |
A board runs tickets. A Factory pursues a goal.
Linear with OpenAI’s Symphony gives every open ticket a coding agent, a workspace and a run until review. Orchestro starts one step earlier, with the goal, and ends one step later, with the result.
| LINEAR + SYMPHONY | ORCHESTRO | |
|---|---|---|
| Work starts from | a ticket someone writes | a goal with a number |
| “Done” means | a pull request ready for human review | an independent check, then the metric after release |
| When the backlog is empty | agents wait for new tickets | the Advisor proposes work toward the goal |
| Domain | code in a repository | content, product, sales: any domain with tools and permissions |
| Memory | ticket state in the tracker | durable history and what was learned |
One goal. One Factory.
Six steps, from the goal you write to the direction you keep giving.
Start with what you want to achieve.
A publication. A product. A service you want to keep improving. Start with the outcome and the boundaries.
You don’t need to begin with forty prompts or a hand-drawn workflow.
northstar init \
--dir packs/content-factory \
--slug content-factory \
--goal "Build an evidence-led content system
for danielepelleri.com: publish useful work,
improve discoverability and learn from results."The goal becomes a roadmap.
Onboarding connects the goal to capabilities, observable sources, evidence rules and the work to do first. Metrics need measurable sources. Permissions need authority. Missing capabilities stay visible.
Your agents do the work. The Factory keeps continuity.
Work is selected, executed, independently checked and recorded. When a check fails the work goes back with the reason. When a worker stops, the next configured one takes over and the history stays. “Done” needs evidence.
The Advisor keeps the loop moving toward the goal.
When the planned work is done and the goal is still far, the Advisor follows its routine: read the results, compare them with the goal, find the gap, propose work. Proposals go through the same governed intake. What exceeds authority waits for you.
- 1Read the results
- 2Compare with the goal
- 3Find the gap
- 4Propose work
- 5Send it through intake
One question first: what shipped today?
Every job the Factory touched today flows left to right through four stations: opened, started, solution written, online. Read it in four steps.
Every problem climbs from a guess to a verified fix.
The Factory keeps what it learned between cycles. The river shows how far each problem got. The graph shows what it is connected to.
Your chat is the control surface. The Factory is the memory.
Ask what is happening. Add a request. Find out why work is waiting, from the conversation where you already work.
- ChatGPT / Claudeyou ask
- Orchestro MCPcontrol plane
- Cloud intentdirection travels
- Local intakegoverned
- Execution & evidenceon your machine
- Cloud readbackstatus + receipts
Different goals. Separate project truth.
Each Factory has its own domain, tools, permissions, metrics and backlog. The Orchestro core is shared. One cockpit, one river each.
A real Factory. Actual published work.
The original Content Factory was manually configured, before goal-based bootstrap landed.
Factory run branches produced articles and site changes, including broader article coverage in the site’s LLM index.
Framework work added stricter capability readiness and closeout rules for delivered work that remained open.
Each publication registers the metric it should move: Search Console clicks and impressions against its own baseline. The check runs after release; until the data arrives, the result stays open.
Autonomy has operating rules.
Waits keep their context
Waiting has a reason and a way back. It need not freeze unrelated work.
Verification is independent
The worker produces a result. A separate check decides whether the evidence is sufficient.
Learning stays governed
History can inform new work. Governor, Critic and bounded experiments keep decisions within authority.
What you can use. What we’re building.
Product snapshot · 4 October 2026Local Factory loops, durable work, independent checks, CLI operation, Reliability and Content cases. Private access with project-specific setup.
Goal scaffold, Domain Builder / Compiler V1, capability reconciliation, cloud publishing, owner cockpit, hosted MCP and governed intent processing. Implementation is not a public self-service launch.
Self-service chat onboarding, public installation and broader domain validation. No claim of a finished autonomous SaaS.
Execution stays with the project.
And everything still has a command.
CLI, MCP and web are designed around the same project identity and history. The web is a view into the Factory, not a second backlog.
$ northstar readiness --pack packs/content-factory ✓ 5 capabilities ready · 1 needs authority $ northstar checkpoint --pack packs/content-factory next: Linking P2 · eligible $ northstar run --pack packs/content-factory running on Codex · receipt recorded $ northstar watch --pack packs/content-factory watching · next cycle in 15 min $ northstar cloud status --pack packs/content-factory connected · last sync 12 s ago $ northstar stato --pack packs/content-factory 3 shipped today · 1 waiting for you
Give one project a goal. Build its loop.
You set the direction. The Factory keeps the project moving.
Private preview · hands-on onboarding · your agents and tools