Skip to content
arula

Stage 725 minutesIndividual501 · Ways of working

Close the loop in your own engagement

Write the operating commitment for your own engagement: who signs what, where decisions land, how release stays separate and what your team will promote into reusable defaults.

You will produce

Operating commitment

We will demonstrate

Two loops, two clocks

Done when

The commitment names real people, real records and a compounding loop that is not the interval review.

Supplied engagementMeridian Payments · Idempotent refund submissionheadless sliceStages 6 and 7 leave the fixture and use an engagement you run yourself.

Orient

Why this stage exists

Transfer is demonstrated when the worksheets are gone. This stage produces a commitment you can put in front of a counterparty.

The delivery loop produces one verified feature. The compounding loop makes the next one cheaper. Folding the second into the interval review retires it.

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.

Decomposition plan
Your own feature from stage 6.
The model and the boundary
Sections 09 and 10 of the operating process.
Your organization
The real names, records and approval paths available to you.
Demonstrate

Two loops, two clocks

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

  1. Name the five claims for your next feature and the people who will sign them.
  2. Name your three systems of record, using tools you already have.
  3. Separate acceptance from release authorization and name both owners.
  4. Define what your team will promote into reusable defaults, and on what clock.

What this turns onAI-DLC assigns the decisions. The platform operationalizes them. People sign. A tool that computes a recommendation has not made a decision, however confident the output reads.

Practice

Do the work

  1. Write the operating commitment for your engagement.
  2. Identify the one hat you cannot currently fill and the escalation that unblocks it.
  3. State the first thing your team will promote into a default, and who curates it.
  4. Name the date you will take this to your counterparty.
Output

You produce

Artifact

Operating commitment

  • Claim and signer
  • Systems of record
  • Acceptance owner
  • Release authority
  • What compounds and on what clock
  • Unfilled hat and its escalation
Pressure-test

Challenge your own result

Your counterparty says this is too much process for one feature. What do you keep?

Show how this resolves

The named counterparty, the separation of acceptance from release, and the rule that a claim states its limitation. Those three make the rest optional rather than the reverse, and none of them requires a new meeting.

Gate

Ready to continue when

Readiness gate
  • The commitment names real people and real records.
  • Acceptance and release authorization have different owners.
  • The compounding loop is not the interval review.

What transfersYou can run the operating process on an engagement nobody prepared for you.

Source · 09 The operating model · 10 Operating boundary