Run the loop to a signed verdict
Take the slice through Define to Judge, then produce a signed confidence package whose claims are bounded by the evidence that actually exists.
Signed confidence package
A claim no stronger than the evidence beneath it
Every signed claim states its limitation, and the release decision is separate and unsigned.
Supplied engagementMeridian Payments · Idempotent refund submissionheadless sliceStages 6 and 7 leave the fixture and use an engagement you run yourself.
Why this stage exists
Four claims are ready to sign. The fifth is contested: the evidence is statistical and nobody has said so.
The exit gates are what make the loop more than a sequence of meetings. Unverifiable is a risk state, never a soft pass.
What you start from
Work from these inputs only. Anything not on this list is either a later stage’s concern or a decision you do not own.
- Handshake map
- Your completed boundary from stage 4.
- The ceremonies
- Sections 06 and 07 of the operating process, five ceremonies and the role view.
- The evidence bundle
- A clean property run over 500 generated sequences, one refuted finding, and silence on the policy class.
A claim no stronger than the evidence beneath it
One worked pass, so the shape of the work is visible before you do it on your own.
- Check the Define exit gate: does every acceptance criterion have an evaluation path, including the explicitly unverifiable ones?
- Read the evidence bundle for what was not examined before reading what was found.
- Draft each of the four claims with its signer and its stated limitation.
- Decide the verdict: confirmed, missing, divergent or unverifiable.
What this turns onA passing gate is evidence. It is not acceptance, release approval or a declaration of production readiness, and the confidence package has to say which of the three it is.
Do the work
- Produce the confidence package for the supplied slice.
- Write the evidence-sufficiency claim so it survives the statistical limitation instead of hiding it.
- Route the unresolved policy question to its owner rather than absorbing it.
- Schedule the release decision as a separate event and name who calls it.
You produce
Signed confidence package
- Claim
- Signer
- What the claim covers
- Stated limitation
- Verdict
- Residual and its owner
Challenge your own result
Four claims are signed and the counterparty accepts. Can the slice go to production?
Show how this resolves
Not on that basis. Acceptance is one decision, release authorization is another and production readiness is a third. The client release authority has not been asked, and the data owner has not seen the ledger retention change. Acceptance is real; it is just not promotion.
Ready to continue when
- Every signed claim states its limitation.
- The release decision is separate, scheduled and unsigned at this point.
- The unresolved policy question has a named owner.
What transfersSign what the evidence supports, name what it does not, and never let a green run stand in for a decision.
Source · 06 Process and ceremonies · 07 Role by ceremony