Built, next, and still being explored.

Updated October 4, 2026Read as Markdown ↗

A running private product, public observations and clear limits on what has been proved.

Deployed / private preview

• Owner cockpit: project switching, current work, freshness, requests, owner actions, progress and Blockers & Recoveries. Some historical scope and recovery facts are not recorded; they remain unknown.
• Content public view: a current read model with timestamps and a dedicated sanitized projection. Live Factories shows the latest availability, including stale or unavailable states.
• Hosted MCP: authenticated, project-scoped reads and bounded owner intents. Local canonical intake and decisions remain authoritative. The deployed transport is not proof of a complete ChatGPT / Claude onboarding experience.

ARVO’s public cockpit is Coming online. Its historical Reliability work is a real case, not a live public feed. Owner access remains private; there is no general self-service SaaS.

Proven historical domains

• Autonomous Reliability Factory: ARVO supplied real investigation, repair, verification and operating lessons. Actual actions depend on the pack’s permissions and release authority.
• Autonomous Content Factory pilot: danielepelleri.com reuses the same ledger, backlog, lifecycle, selector and executor / verifier. The manually configured domain adds evidence, thesis, writing, editorial reviews, SEO, internal linking and publishing checks.

These cases demonstrate domain reuse. They do not establish traffic growth, revenue impact or universal integrations. The dated ARVO account retains its historical adoption and benchmark limits.

Implemented in the private core

• Goal scaffold: northstar init --dir <packDir> --goal <text> creates a validated domain manifest. It does not connect adapters, grant permissions or start execution.
• Domain Builder / Compiler V1: validates an agent’s proposal against real capabilities, materializes work and reports READY or NOT_READY.
• Capability reconciliation: names gaps in truth, execution, verification, durability, mapping, cloud, watch and board.
• Cloud intent processing: passes allowed requests through local intake, roadmap and owner-decision primitives with idempotent receipts. Requested, materialized, selected and delivered remain separate.
• Executor chain: ordered alternatives exist for configured providers. No automatic failover or unattended Mac reboot story is claimed as proven live without the corresponding runtime receipts.
• Sales domain: cross-domain implementation and test evidence exist. This is not a live sales pilot or proven CRM / revenue integration.

In development / not yet proven end to end

• Self-service onboarding: public installation, credentials, integration setup and a ready Factory from a goal without hands-on assistance.
• Chat client acceptance: ChatGPT / Claude client installation and a complete owner request → local work → outcome conversation.
• Recovery evidence: comprehensive unattended recovery, meaningful interruption duration and proof of work resuming where historical canonical facts are missing.
• Owner outcomes: domain-defined mission and readiness metrics need a configured definition and real measurements. No configured metric means “Owner outcome metric not configured”.
• Broader autonomy: general event-driven wakeups, automatically promoted learning rules and complete Operational Zero certification require separate evidence and governance.

Cloud and runtime have different responsibilities

Cloud guides. Local Factory executes. Evidence decides. The cloud holds project-scoped observations and owner intent. The execution host retains canonical work, authority checks and verification. A remote request cannot grant itself merge or release permission.

Read the MCP and cloud boundaries.

Real observations versus examples

Live Factories reads public-safe operational data and labels its age. It does not use a simulated backlog. How it works uses labelled product illustrations to explain the system.

The retained operating examples are simulations, including campaign workflows and synthetic metrics. No example click executes a command, deploys code or publishes an article. Technical verification and measured product benefit remain separate.

Try a bounded private pilot

Bring a goal with readable evidence and clear limits. Setup is hands-on. Request private access or follow the repository setup guide.