Showcase · governed operating system
Agent work does not become progress until the evidence says so.
DAOS is DBAI's internal operating system, shown here through its verified production release. The program board is authenticated and the wider 18-phase program remains governed by its gates; this page does not present the program as complete.
DAOS turns a long agent-assisted build into an accountable operating record. Work is assigned to a program and phase. Lifecycle events report their own scope, gates require measured evidence, dependencies are enforced by the same server-side path, and final phase authority remains with the owner. The result is a board that distinguishes activity from accepted progress.
- Property
- DAOS — DBAI's governed operating system for agent-assisted programs
- Role
- Program architecture, tracker implementation, evidence model, telemetry and production release
- Access
- Google-authenticated production board with an explicit owner allowlist
- Checked status
- P00 implementation released; owner signoff remained pending in the September 2026 release record
The program definition
A finite program with evidence at every boundary.
These figures describe the checked source package, production migration and isolated lifecycle validation. They measure the operating system around the work, not completion of the wider DAOS program.
- phases in the source-controlled program
18
phases in the source-controlled program
- verbatim evidence gates carried into production
103
verbatim evidence gates carried into production
- preexisting records fingerprint-matched after migration
5,312
preexisting records fingerprint-matched after migration
across 27 existing tables; no original row changed or disappeared
- independent hook-session identities validated
Two
independent hook-session identities validated
real lifecycle probes on the disposable validation branch, with tools disabled
01 · What the system governs
One record from assigned work to accepted progress.
DAOS keeps the definition, execution trail and approval state together so the board can answer what happened, where it happened and who accepted it.
Program-scoped work
Phases, tasks, activity, session records, decisions, blockers and usage carry a program identity. DAOS activity cannot silently land in the agency site's historical records.
Evidence-gated completion
CLI, interface, API and imports converge on the same server-side rules for dependencies, evidence and owner signoff. A different entry point cannot bypass the gate.
Session attribution
Lifecycle hooks attach a known program and phase to session start, stop and end events. Unknown explicit programs fail instead of contaminating another program's history.
Owner-held authority
Implementation tasks can finish while the phase remains active. Evidence informs the decision; only an authenticated owner can sign the phase complete.
02 · The governed path
The system records more than an agent's last message.
A completed response is activity. DAOS turns it into progress only after the surrounding controls agree.
- 01
Assign
Bind the work to a known program, phase and task before execution begins.
- 02
Observe
Record session lifecycle and usage against the same scope without inventing unsupported telemetry.
- 03
Prove
Attach measured evidence to the exact gate it supports, preserving the source and time of the check.
- 04
Enforce
Check dependencies, missing gates and authorization through the shared completion service.
- 05
Sign
Expose completion to the authenticated owner only after the program's requirements are satisfied.
03 · What was verified
The release was tested against the ways a tracker can lie.
The acceptance work checked production behavior, preservation, authorization and refusal paths rather than treating a populated board as proof by itself.
| Surface | Result | Boundary |
|---|---|---|
| Production board | Released | Authenticated board served all 18 phases and 103 gates at build.dbai.agency |
| Existing site data | Preserved | 5,312 original rows across 27 tables matched their pre-migration fingerprints |
| Lifecycle attribution | Passed | A production probe and two isolated real-session probes wrote scoped start and end events |
| Completion refusal | Passed | The next phase exited nonzero and named its missing gates, dependency and owner-signoff requirement |
The two isolated sessions ran with tools disabled. They prove unattended lifecycle attribution across distinct session identities; they do not prove a DAOS work cycle or grant owner approval.
Why it is on this site
The difficult part of agent work is deciding what counts.
A transcript can show effort while leaving no durable answer to whether the right system changed, whether a check passed, or whether a person with authority accepted the result. DAOS gives those questions explicit places in the operating record.
That pattern applies anywhere agents work across repositories, services and long-running programs. Scope the work before it starts, preserve evidence as it moves, enforce the gate in code, and keep final authority visible.
The production board
Open the authenticated DAOS program board.
The production route requires an authorized Google account. Public visitors can read the verified release story here; operating detail, phase controls and owner actions remain inside the authenticated tracker.
The DAOS program runs in DBAI's build command center: build.dbai.agency/programs/daos (opens in a new tab)
Need proof around the agents doing the work?
Bring us the workflow where activity is easy to produce and hard to verify. We will map the program, evidence gates and decision rights it needs.
Book a Discovery Call