What
Named work
The agents about to run, and the artifacts they will produce. Not “the system will generate documentation.”
Carbon / Observability
This is the documentation run, not an infrastructure dashboard. You can see the plan, the extraction, the diff, and who signed.
Request a trialWhat
The agents about to run, and the artifacts they will produce. Not “the system will generate documentation.”
Why
“Because you checked FDA, safety runs at high intensity.” Not a vague justification.
Duration
An estimate so you can stop a phase that is about to do more than you asked. Not a cost dashboard.
Your move
Approve, modify, or go back. The phase does not begin until you answer.
0.70
Each extracted constraint keeps its source and a score. Below 0.70, it waits. It does not become a requirement by inertia.
10
More than ten files, and you approve a document map first. A zip of old decks does not become the specification.
0
Agents do not watch each other while they write. You see output at the gate, attributed.
Proposed rewrites by severity. Required items are decided one by one. Overflow is a batch, so the gate stays readable.
The score, the four passes, and the weights actually used. A surprise weighting is visible before you sign. Bands.
Append-only. Every decision, timestamp, and rewind reason. Hash-chained, so a later edit of the bundle is detectable.
Contents, section length, the score, and how much of the business requirements trace forward. A number, not a cover-letter claim.