OSS SINGULARITY · DESIGN VISION · SYNTHETIC DATA

04 · Acceptance & QA

The proposed flow — delivery, revision request, new delivery, acceptance — as one portable decision trail. Every decision names its actor, role and the exact delivery and criteria versions it binds; a stale approval is shown refused, not silently superseded.

Design candidate. Illustrates the planned acceptance stage's release criteria with synthetic content. Not a live API, dispute process or settlement arrangement — see the vision index for scope.

Journey view · policy before work

The acceptance policy, visible from the start

Agreed before work begins, rendered where every participant can point at it: who decides what, which evidence is required, and what independence concretely means here.

Coordinator
@aria — checks scope against the bound criteria version
QA role
@sana — checks evidence; assigned by @aria, never self-granted
Required evidence
Delivery manifest rev N + two independent byte verifications
Independence
QA is a distinct person with no delivery authorship in this milestone — a second account alone would not satisfy this
Approval threshold
Scope check + QA check, both on the same delivery revision
Escalation
Revision request unanswered after 10 days → named dispute path

Criteria addressed
Acceptance policy agreed before work begins · coordinator, reviewer roles, evidence, approval threshold, revision process and escalation deadline named · independence requirements concrete, not a second account.

Journey view · the decision trail

Delivery → revision → new delivery → acceptance

One trail, newest last. Each decision binds the exact delivery revision and criteria version; revisions produce a new version and cannot inherit a stale approval.

  • Step 1 · 12 Sep

    Delivery rev 1 submitted

    @kofi delivers manifest rev 1 with synthetic artifact and evidence references.

  • Step 2 · 13 Sep

    Revision requested

    @sana (QA): evidence missing one independent byte verification. Decision binds rev 1 × criteria v3 · result: revision · reason recorded. Scope untouched; nothing inherited by a future delivery.

  • Step 3 · 15 Sep

    Delivery rev 2 submitted

    @kofi delivers rev 2 with a second verification run. A new version — the revision request's approval does not carry over.

  • Step 4 · 15 Sep

    Accepted

    @aria (coordinator, scope) and @sana (QA, evidence) both bind rev 2 × criteria v3 · result: accept · reasons recorded. Settlement, if separately enabled, would consume its own authorization — a delivery is never permission to pay.

    threshold met
    2 of 2 required roles

Criteria addressed
Proposed flow: delivery → revision requested → new delivery → acceptance, with a portable decision trail · each decision binds the exact delivery and criteria version, result and reasons · delivery alone does not change the milestone to accepted · settlement consumes its own authorization.

Journey view · refused states

What refusal looks like

The failure paths are drawn states, so they can be reviewed before they exist in code. Color is paired with words; every refusal names the rule it enforces.

Approval for rev 1refused · stale version

Rev 2 exists; this approval bound rev 1. Stale-version rejection: a superseded delivery cannot hold a live approval.

Approval by @kofirefused · role

@kofi authored the delivery and holds no QA role in this milestone. No self-granted reviewer authority.

Duplicate decisionrejected

@sana's scope+evidence decision on rev 2 is already recorded; a second, identical decision adds no threshold unit.

Absent reviewerwaiting

QA slot empty past the escalation deadline → the named dispute path is opened automatically. Unavailable decision-makers are a designed state, not an exception.

Criteria addressed
Release criteria: stale-version and duplicate decision rejection · authorization checked at the decision point · conflicting approvals, absent reviewers, role revocation and disputed evidence exercised · no self-granted reviewer authority.