Four documents covering the day-to-day mechanics.
Approval workflowStates, transitions, and who can approve what
Build pipelineThe four verification layers, and how a build actually runs
Trial environmentsLifecycle, seeding, regions, and teardown
Feedback and defectsTurning what you find in the trial into a fixed specification
Build pipelineThe four verification layers, and how a build actually runs
Trial environmentsLifecycle, seeding, regions, and teardown
Feedback and defectsTurning what you find in the trial into a fixed specification
The loop
The workflow is a loop, not a line, and the loop is where the platform earns its keep.
┌──────────────────────────────────────────────┐
│ │
draft ──▶ review ──▶ snapshot ──▶ build ──▶ trial ──┘
▲ │ │ │
│ │ │ └── findings ──┐
│ │ └── failed layers ────────┤
└──── revised ───────┴──────────────────────────────────┘
Each arrow has a specific behaviour:
- draft → review: the draft is only shown once, and only its diff is shown again later.
- review → snapshot: approval is scoped to clauses. Rejecting one regenerates only that clause.
- snapshot → build: the build is pinned to the snapshot. It cannot drift.
- build → trial: only a build that passed every verification layer gets an environment.
- trial → findings: a finding attaches to a clause, which regenerates that clause.
The last arrow is the one that most tools get wrong, and it is where a platform either compounds or decays.
State model
A clause moves through a small, explicit set of states:
| State | Meaning |
|---|---|
draft |
Written by the model, not yet reviewed |
in_review |
Presented for a decision |
approved |
Accepted; part of the next snapshot |
rejected |
Refused with a reason; regenerating |
deferred |
Deliberately unresolved; carried forward |
implemented |
Covered by an executed, passing scenario |
verified |
Covered by a scenario graded strong or normal, with no escaped defect |
approved and verified are different states, and the gap between them is the whole point. Approval is a human judgement about intent. Verification is a mechanical fact about the build. The platform never conflates them, and the completion map always shows both.
Approval workflowDraft, review, approve, reject, defer — and the audit trail that results.
Build pipelineQueueing, the four verification layers, reproducibility, and failure attribution.
Trial environmentsProvisioned, seeded, regional, disposable — and the same artifact you will ship.
Feedback and defectsHow a finding in the trial becomes a corrected clause — and why defect class matters more than defect count.
Build pipelineQueueing, the four verification layers, reproducibility, and failure attribution.
Trial environmentsProvisioned, seeded, regional, disposable — and the same artifact you will ship.
Feedback and defectsHow a finding in the trial becomes a corrected clause — and why defect class matters more than defect count.