26 completed P0s
Only P0s that pass formal acceptance with traceable evidence enter the completed count. The public release remains v0.1.8 Beta.
Public status
Look past marketing copy and inspect the current evidence boundary.
This project-maintained aggregate snapshot is published with the website. Strictly verified, partially complete, planned, and release-qualified states are never collapsed into one number; it is not independent release proof.
P0 strictly verified26/64
P0 still open38
P1 strictly verified4/38
P1 still open34
Snapshot date2026-08-17
How this number is produced
26 / 64 P0 items strictly verified
A project-maintained script aggregates acceptance states and publishes the snapshot as /status.json before the website build. Qualified verified states count as partial, not strictly complete; formal distribution facts remain bounded by the GitHub Release.
- P0 partial / qualified
- 34
- P0 project targets
- 3
- P0 foundation
- 1
- P1 partial / qualified
- 33
Product truth
The end-state requirements are not the current completion state.
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.
34 partially complete
Code, UI, or targeted evidence exists, but complete contracts, recovery, cross-provider continuity, release binding, or human workflows remain open.
3 project targets
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, cross-device, and multi-user work
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.
No external Agent launcher or universal collaboration suite
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.
Evidence