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.6 Beta · 21 of 64 P0s formally verified
One kernel, two experiences
Assistant and Studio share the same project, session, and run state. Switching modes must not restart work or lose context.
For office, education, research, and everyday knowledge work, with providers, tokens, terminals, 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.
Everyday and professional users share the same Project, Goal, WorkItem, Run, Artifact, and approval state.
Digital workers are internal CaoGen role instances. Models are replaceable compute used by ModelAttempts.
CaoGen owns execution semantics, context, and state. Protocol adapters cannot bypass permissions or the effect ledger.
An Agent completion claim is not completion. Effects, artifacts, evidence, and acceptance must be queryable, reconcilable, and recoverable.
Automation, memory, Skills, and the 3D digital team may project real work state only. They must not fabricate execution.
Migration, export, deletion, upgrades, and formal release assets must be reversible, verifiable, and credential-free.
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. Of 64 PRD P0s, 21 are verified, 17 are partially complete, 25 remain project targets, and 1 has only a foundation. Evidence without formal acceptance is not promoted into the website's verified count.
Formal status: 2026-07-23Only P0s that pass formal acceptance with traceable evidence enter the verified count. The public release remains v0.1.6 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.
A minimum security foundation exists, but complete scoping, process isolation, egress verification, and formal acceptance remain open, so it is not counted as verified or partially complete.
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 PRD defines the functional boundary and the acceptance matrix defines required evidence. Implementation without formally bound evidence is never promoted into the verified count.
