Skip to content
arula

Stage 630 minutesPairs301-P · Executable intent

Survive ratification

Submit the specification for independent ratification, then revise it until it is accepted or every objection has an owner and a date.

You will produce

Ratified spec and objection log

We will demonstrate

A rejected artifact returns to its author

Done when

The spec is ratified, or every unresolved objection has an owner and a decision date.

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

Orient

Why this stage exists

No person independently ratifies a claim they authored alone. You wrote the spec, so you do not get to declare it buildable.

Define runs in parallel across product, technical, design and evaluation artifacts. A rejected artifact returns to its author and must be ratified again. This stage is where that stops being procedural.

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.

Your specification
Acceptance contract, scope boundary and decomposition.
A ratifier
An engineer, or another pair holding the technical boundary hat.
Objection classes
Feasibility, evidence, scope and cost. They resolve differently.
Demonstrate

A rejected artifact returns to its author

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

  1. Hand the spec over without narrating it.
  2. Take objections in writing, classified by type.
  3. Revise what is defective. Record what you dispute.
  4. Get explicit acceptance, or an owned objection with a date.

What this turns onYou are not defending the document. You are finding out whether it can be built and evaluated by people who were not in the room when you wrote it.

Practice

Do the work

  1. Exchange specs with another pair and ratify adversarially.
  2. Classify every objection you receive.
  3. Revise and resubmit once.
  4. Record what you did not change, and why.
Output

You produce

Artifact

Ratified spec and objection log

  • Objection
  • Class
  • Raised by
  • Resolution
  • Unresolved owner and date
Pressure-test

Challenge your own result

The ratifier says the spec is buildable but expensive. Must you resolve that?

Show how this resolves

Cost is a decision, not a defect, and it belongs to you and the counterparty rather than to the ratifier. Record it, decide it, and do not quietly re-scope to make the objection disappear.

Gate

Ready to continue when

Readiness gate
  • The spec is ratified, or every unresolved objection has an owner and a date.
  • No objection was resolved by deleting the criterion that caused it.

What transfersHand any specification to someone who was not in the room and see what survives.

Source · 07 Role by ceremony