PERSISTENT AI-AGENT LOOPS · PRIVATE PREVIEW

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.

14
jobs shipped today12 online now · 3 waiting for you · 2 reopened later
END OF DAY · 19:00
34 jobs opened28 started17 solution written12 online6 waiting to start3 waiting for you8 being worked on · ↩ +45 checking before going online↩ 2 failed the check↩ 2 reopened after deliveryFirst published · newest first16:27Gmail subject no longer trunc…16:14RSS feed dates corrected16:11Internal links to archived po…16:11Mobile charts redrawn15:51Glossary: 12 new agent terms15:50Series page in reading order15:33Lighter images on the home pa…15:30Loop series 1/6: what an agen…15:26Alt text on every cover15:11Canonical on translat… · reopened15:00Titles no longer cut off on G…+3 more
◈The FactoryYou decide here: publish the loop series in English too?
◈The FactoryYou decide here: publish the loop series in English too?
34 jobs opened28 started17 solution written12 online6 waiting to start3 waiting for you8 being worked on · ↩ +45 checking before going online↩ 2 failed the check↩ 2 reopened after delivery
◈The FactoryYou decide here: publish the loop series in English too?
◈The FactoryYou decide here: publish the loop series in English too?
07:00Sample data · one content-factory day replayed in 30 seconds · a green dot is a first publication19:00
THE DIFFERENCE

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.

A typical agent sessionAgent with /goal or /loopWith OrchestroPromptworkanswerThe conversation ends.loops while the session runs/goalworkcheckStops when the session ends.The next cycle starts with history.Goaldurable workcyclesevidencelearningcycle 3 · history kept
AGENT SESSION/GOAL · /LOOPORCHESTRO
Keeps working toward a goalNowhile the session runs✓ across sessions
Work survives the sessionNoNo✓ durable backlog
“Done” is checked independentlyNoself-assessed✓ separate check
Another worker takes overNoNo✓ with a receipt
Finds new work when the backlog is emptyNoNo✓ Advisor
You define the direction.Goal, constraints and evidence guide the next authorized work. You don’t draw every step.
You keep execution with the project.The remote control plane adds visibility and intent; it does not need to become the machine that owns your repository.
ALREADY DISPATCHING AGENTS FROM A BOARD?

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 + Symphonyboard: 0 ticketsTicketCodex agentPull requestHuman reviewBoard empty.Agents wait for the next ticket.Orchestrobacklog: 2 · from the AdvisorBacklog empty, goal not reached: the Advisor proposes the next work.GoalWorkCheckMetricAdvisortraffic +20% y/y
LINEAR + SYMPHONYORCHESTRO
Work starts froma ticket someone writesa goal with a number
“Done” meansa pull request ready for human reviewan independent check, then the metric after release
When the backlog is emptyagents wait for new ticketsthe Advisor proposes work toward the goal
Domaincode in a repositorycontent, product, sales: any domain with tools and permissions
Memoryticket state in the trackerdurable history and what was learned
Based on OpenAI’s public Symphony specification, released 27 April 2026 as a reference implementation. A tracker stays a good place for tickets; this compares what happens around them.
HOW A FACTORY WORKS

One goal. One Factory.

Six steps, from the goal you write to the direction you keep giving.

01 · GIVE IT A GOAL

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.

Local terminalnorthstar
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."
✓ Goal saved in the domain manifest✓ Valid domain scaffold created→ Next: connect sources, permissions and verification
02 · BUILD THE WORK SYSTEM

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.

GOALA publication that keeps getting better.5 ready · 1 needs authority
Evidence miningobservable sourcepermissionverificationready
Writingobservable sourcepermissionverificationready
SEOobservable sourcepermissionverificationready
Internal linkingobservable sourcepermissionverificationready
Distributionobservable sourcepermission missingverificationneeds authority
Measurementobservable sourcepermissionverificationready · GSC export arrived
DURABLE WORKPRIORITY
ArticleTurn a real engineering incident into a storyeligibleP1
SEOMake every published article discoverableeligibleP2
LinkingConnect the article to its topic clustereligibleP2
MeasureReview results when a GSC export arriveseligibleP2
New evidence can become the next authorized work.
03 · TURN ON THE LOOP

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.

ObserveSelectExecuteVerifyRecordLearnNexthandoff → CodexCYCLE 3 OF 3A worker stopsThe next one takes over. History stays.
CONFIGURED EXECUTOR CHAIN
Claude Codequota exhaustedCodexlast workerGrokstandby
DURABLE HISTORY · NEWEST FIRST
10:32Selecting the next eligible item
10:28History kept across the switch
10:24Receipt recorded
10:20Independent check passed. Later progress proves continuation
10:16Handoff receipt: switched to Codex
10:12Claude Code: provider quota exhausted
Illustrative sequence. A running host, configured tools, permissions and provider quota are required. Execution pauses when the host is offline.
03 · WHEN THE BACKLOG RUNS OUT

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.

GOAL · MARKETING FACTORYOrganic traffic +20% year over year
+9%of +20%
11 points to go
BACKLOG5 items
Competitor analysis: what 5 similar blogs rank forAdvisor · goal gaprunning
Keyword gaps from Search Console queriesAdvisor · goal gapeligible
Funnel drop: article → newsletter signup at 0.8%Advisor · goal gapeligible
CTA test on the 10 most-read articlesAdvisor · goal gapeligible
Paid test: €200 LinkedIn promotionAdvisor · goal gapasks you
ADVISOR ROUTINE
  1. 1Read the results
  2. 2Compare with the goal
  3. 3Find the gap
  4. 4Propose work
  5. 5Send it through intake
Advisor4 items accepted by intake. The paid test needs you: it spends budget.
Illustrative sequence. The Advisor proposes; governed intake, permissions and the owner decide what becomes work.
04 · WATCH · GIORNATA

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.

Step 1 · thicknessthe river at the end of the day
34 jobs opened28 started17 solution written12 online6 waiting to start3 waiting for you8 being worked on · ↩ +45 checking before going online↩ 2 failed the check↩ 2 reopened after delivery
Band thickness = number of jobs
Stopped early. The reason is written beside it.
Band thickness = number of jobs
Stopped early. The reason is written beside it.
05 · LEARN · MEMORIA

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.

The river of what it learnedWEEK 8 OF 8
25 hypotheses22 cause confirmed18 fix attempted16 fix released12 verified3 still a hypothesis4 cause known, no fix yet · ↩ +32 fix being tried4 released, waiting for a check↩ 2 fix failed, back to the cause↩ 1 reopened after verification
A fix counts as verified only when an independent check passes on main. Fixes that fail drop back a step, in their own lane. Sample data, eight weeks replayed.
The graph of connectionsSEO & searchNewsletterLoop seriesTranslationsImagesPages & formsContent to refreshseo/checklist.mdnewsletter.mdloop-series/index.mdtranslations.mdimages.mdpages/verify.mdstyle/sources.mdowner-writing.md
VERIFIED BY A THIRD PARTYTitles cut off on GoogleSEO & search
The FactorySame cause in three places: a length limit ignored for titles, social titles and the email subject. I fixed the rule, not the single page.
Tap any dot to draw its connections, one at a time. Tap a link type to hide it.
06 · KEEP GIVING DIRECTION

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.

  1. ChatGPT / Claudeyou ask
  2. Orchestro MCPcontrol plane
  3. Cloud intentdirection travels
  4. Local intakegoverned
  5. Execution & evidenceon your machine
  6. Cloud readbackstatus + receipts
YouWhat is the Content Factory working on?
OrchestroCluster linking sprint, on Codex. Last durable progress: 4 minutes ago. Two GSC tasks are waiting for a new export; independent work can continue.From the Factory’s last synced snapshot
YouAdd a P2 task to build a downloadable content audit tool.
OrchestroRequest sent. The local Factory checks it through governed intake.
Receiptbacklog:example-audit-tool · P2After local acceptance
Conversation expresses intent. The Factory remains the authority. Hosted MCP is implemented in private preview; ChatGPT / Claude require a configured client.

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.

Content Factory
RunningBuild a useful, discoverable publication.
Own goal · tools · permissions · history
Product Reliability
Waiting for evidenceKeep critical product journeys working.
Own goal · tools · permissions · history
Sales Factory
Needs youDevelop a qualified pipeline within agreed limits.
Own goal · tools · permissions · history
Customer Support
RunningTurn recurring questions into better service.
Own goal · tools · permissions · history
ORCHESTRO CORE · SHAREDCanonical intake · permissions · work selection · independent verification · durable history
Illustrative workspace states. Content and Reliability are real pilots; Sales and Support are further domains to validate, not generally available products.
REAL PROJECT · DANIELEPELLERI.COM

A real Factory. Actual published work.

CONFIGUREPRODUCEIMPROVEVALIDATEmetric check +28 daysGSC clicks vs. baseline · openmainmanual configurationrun branchf40812f01 publishedrun branch3a9e1bf02 publishedrun branch51a52d803 publishedcloseout rulesPublished 3 October 2026
01 / Configure

The original Content Factory was manually configured, before goal-based bootstrap landed.

02 / Produce

Factory run branches produced articles and site changes, including broader article coverage in the site’s LLM index.

03 / Improve the system

Framework work added stricter capability readiness and closeout rules for delivered work that remained open.

04 / Validate after release

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.

Publications and Git history checked 4 October 2026. Output is proven here; audience growth, conversion lift and fully hands-off operation are not inferred.

Autonomy has operating rules.

waiting · GSC exportother work keeps moving

Waits keep their context

Waiting has a reason and a way back. It need not freeze unrelated work.

WorkerClaude Codeseparate✓ Checkindependentevidence sufficient

Verification is independent

The worker produces a result. A separate check decides whether the evidence is sufficient.

HistoryreceiptsGovernor · Criticappliedwithin authorityasks yououtside authority

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 2026
Real pilots today

Local Factory loops, durable work, independent checks, CLI operation, Reliability and Content cases. Private access with project-specific setup.

Private core

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.

In development

Self-service chat onboarding, public installation and broader domain validation. No claim of a finished autonomous SaaS.

Execution stays with the project.

YOUR COMPUTERThe Factory does the work.Agents · repository · tools · evidence
CLOUD CONTROL PLANEDirection travels. History stays.Intents in · status and receipts out
YOUR PHONE & CHATYou stay in the loop.Cockpit + ChatGPT / Claude · in development

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.

CLIyou run it from the terminal
MCPyour chat asks and adds requests
Webthe cockpit shows the river
↳ one project · one history
Explore the CLI reference →
northstar · packs/content-factoryillustrative output
$ 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