01Verified live
Dispatch
One repository, one writer.A task starts only after its scope, owner, and acceptance check are visible.
Operating skills
AI work needs receipts.
Six small procedures keep ownership, evidence, approvals, and finished work visible.
Operating contract
Clear work. Human gates.
- Ownership
- Every task names one active writer and one approval owner.
- Evidence
- A test, capture, or artifact supports every completion claim.
- Boundaries
- Publishing, deployment, credentials, payments, and originals stop for approval.
- Forecasts
- Suggested work remains a proposal until a person starts it.
The workflow
A task earns its way forward.
- 01RequestState the outcome.
- 02ObserveCollect evidence.
- 03PlanName the checks.
- 04GateAsk when required.
- 05BuildKeep one writer.
- 06VerifyInspect behavior.
- 07ReceiptRecord the result.
Six reusable skills
Failure modes, written down.
02Verified dry
Independent review
Separate conclusions stay separate.Reviewers examine the same brief independently so agreement and disagreement remain legible.
03Verified live
Closeout
The record beats scrollback.A finished task records the change, the check, the blocker, and the next decision.
04Audited
Release gate
Stop at the irreversible edge.Build and verification can continue while release and distribution wait for approval.
05Audited
Proof-backed copy
Drafts are not published.Public notes come from commits, artifacts, and captures instead of invented metrics.
06Audited
Visible verification
A real screen beats a green check.Tests sit beside the fresh-user path, the packaged app, and the visible result.