Skip to content
arula

Stage 825 minutesIndividual, joint where possible301-P · Executable intent

Receive the escalation and decide

Take the F8 escalation, make the policy decision, and state what it changes downstream.

You will produce

Policy decision record

We will demonstrate

The decision no check can make

Done when

The decision is made, owned and dated, and its release impact is stated.

Sibling repository../payments-validation-fixture836a75dShared with course 301. You work from specs/product/payments.md rather than the diff.

Orient

Why this stage exists

F8 is reserved for a person by design. Course 301 ends by escalating it. This course begins by receiving it.

A property test can enforce idempotency only after someone decides that idempotency is required.

Start from

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.

The escalation
The engineers’ human decision record, or the supplied one.
Evidence reading
Your typed results from stage 7.
Domain SME
Payments operations on what clients do, as opposed to what the spec assumed.
Demonstrate

The decision no check can make

One worked pass, so the shape of the work is visible before you do it on your own.

  1. Read what the engineers established and what they refused to decide.
  2. Decide the policy: is a second submission with the same key a no-op or a second refund?
  3. Record the decision, its owner and its date.
  4. State what changes in the spec, the evaluation plan and the release claim.

What this turns onDeciding is the job. Routing it back to engineering as "use your judgment" is how an undecided policy ships.

Practice

Do the work

  1. Make the decision and record it.
  2. Write the criterion the decision now makes writable.
  3. State the release impact: does this hold the slice, or bound the claim?
  4. Run the handover live with an engineering pair if both courses are in the building.
Output

You produce

Artifact

Policy decision record

  • Unresolved behavior
  • Decision
  • Owner
  • Date
  • New or changed criterion
  • Release impact
Pressure-test

Challenge your own result

Can you defer the decision and ship behind a flag?

Show how this resolves

Sometimes, and it is still a decision. A flag bounds who is exposed. It does not answer what the behavior should be. Record the deferral, its owner and the date it must resolve, or it is not deferred, it is forgotten.

Gate

Ready to continue when

Readiness gate
  • The decision is made, owned and dated.
  • A criterion now exists that the decision made writable.
  • The release impact is stated.

What transfersWhen every check passes, ask what the requirement never decided.

Source · 06 Process and ceremonies