Turn a conversation into complete work that can recover, be reviewed, and be accepted.
Assistant and Studio are two experiences over the same Project, Goal, WorkItem, Run, Artifact, Evidence, and Approval state. This page defines 1.0 completion; it is not a capability promise for the current Beta.
Current v0.1.8 Beta · 26 of 64 P0s formally verified
One kernel, two experiences
Assistant and Studio target shared project, session, and run state. Current continuity remains limited to the capabilities verified on the status page.
A lighter task view for developers and AI power users, with provider, token, terminal, and DAG details hidden by default.
For product, engineering, solo-company, and complex project work, with Goals, WorkItems, digital workers, cost, diffs, evidence, and approvals.
24 end-state capabilities · 6 system surfaces
These six groups cover the complete 1.0 capability system. They describe the end state, while status labels remain tied to formal acceptance evidence.
The 1.0 target gives developers and AI power users the same Project, Goal, WorkItem, Run, Artifact, and approval state across Assistant and Studio.
The 1.0 target defines digital workers as internal CaoGen role instances and models as replaceable compute used by ModelAttempts.
The 1.0 target has CaoGen own execution semantics, context, and state while routing protocol adapters through permissions and the effect ledger. Current coverage remains bounded by the status page.
The 1.0 target does not rely on an Agent completion claim alone. Within integrated registry paths, it preserves effects, artifacts, evidence, and acceptance state for inspection, reconciliation, and recovery.
The 1.0 target requires automation, memory, Skills, and the 3D digital team to display registered real work state rather than present random animation as actual execution.
The 1.0 target gives migration, export, deletion, upgrades, and formal release assets reversible, verifiable, credential-safe processes.
CaoGen 1.0 target workflow
These ten stages define the complete 1.0 delivery state machine. The current release contains several foundations but does not yet persist and formally accept the entire chain.
Persist the objective, boundaries, budget, approvals, risks, and Acceptance criteria.
Collect traceable sources, facts, constraints, unknowns, and research evidence.
Turn research into scope, priority, contracts, and requirements that can be accepted.
Create architecture, interaction, visual, data, and decision artifacts with version relationships.
Split WorkItems, dependencies, owners, resources, risks, and verification gates.
Execute tools in controlled directories or worktrees, record Effects, and produce artifacts continuously.
An independent role inspects scope, sources, diffs, permissions, cost, risk, and effects.
A failed review creates a repair WorkItem while preserving the failure reason and original evidence.
Tests, screenshots, remote state, or user approval become Evidence. Completion follows only after retest passes.
Bundle changes, artifacts, evidence, cost, risks, remaining work, and verifiable release assets.
Product truth
CaoGen 1.0 has not reached stable release criteria. The formal status remains 26 completed P0s, 34 partially complete items, and 3 project targets. Local dirty-worktree evidence is not promoted into website completion counts before release binding.
Formal status: 2026-08-17Only P0s that pass formal acceptance with traceable evidence enter the completed count. The public release remains v0.1.8 Beta.
Code, UI, or targeted evidence exists, but complete contracts, recovery, cross-provider continuity, release binding, or human workflows remain open.
The end-state capability system defines 1.0 completion. It does not mean the current product already closes Native Runtime, Context, Artifact, Acceptance, and Supervisor loops.
Remote Supervisors, cloud Runners, desktop-closed execution, cross-device takeover, multi-user and organization policy, business connectors, Portfolio/Gantt, template markets, SSO/SCIM, and private deployment are end-state extensions.
CaoGen does not treat Codex, Claude Code, or Gemini CLI as digital workers, build foundation models, replace complete Jira, HR, CRM, ERP, Office, chat, or meeting products, fabricate work with random animation, or claim transactional exactly-once for arbitrary external systems.
Real state visualization
The current 3D control room already reads real session, task, approval, cost, provider, worktree, and Git state. The watercolor digital team is a clearly labeled 1.0 target.
Return to the current productA verifiable definition of done
The status page records the project-maintained acceptance snapshot, while the formal Release defines the published installer boundary. Implementation without bound evidence is never promoted into the verified count.
