Reference model

The other sections explain one element at a time. This one asks how they work together. It follows a single fictional demand, DU-001: online booking for a barbershop. It is an illustration of the model, not a universal process, and not evidence that the model works. A simple case was chosen on purpose; it does not limit the model to small businesses.

How to read the case

The case keeps the causal direction of the model. AI could reduce the effort of learning, preparing context, producing, evaluating and deciding; capacity organized around that reduction is what would allow smaller advances and real choices about continuing. The operational detail shows how that relationship can be carried out. The fictional prices do not show that it is already economical.

Case conventions

Each page in this section refers to the same commitments, stages, outputs and acceptance decisions.

Reference	Meaning in the case
C0	Discovery for 20. Authorizes S1 and S2, with a useful result even if nothing is built.
C1	Booking for 80. Authorizes S3, S4 and S5, including corrections under the agreed rules.
S1 / A1 / Q1	Clarification / the rules / acceptance of the clarification.
S2 / A2 / Q2	Design / prototype and architecture / acceptance of the basis for continuing.
S3 / A3 / Q3	Implementation / an identified change / acceptance within its local scope.
S4 / A4 / Q4	Integrated validation / the results / integrated acceptance.
S5 / A5 / Q5	Deployment / the record and checks / acceptance of the stage.

The identifiers organize the reading. They do not create new terms or a sequence every demand must follow.

Shared rules

An appointment lasts 30 minutes and must fit within the availability registered for the chosen professional. Confirmed appointments for the same professional cannot overlap; different professionals can work at the same time; a confirmed cancellation frees the slot. Repeating the same request must not create a second booking. The integration identified during design is the barbershop’s calendar service, which stores bookings and cancellations.

Commercial consistency

The offer with reminders costs 95, which is 80 plus 15. A mandate of up to 90 more after discovery allows booking at 80 to be chosen when its other conditions hold. That leaves 10 unused; the aggregate contracted price is 100 and the aggregate authorized ceiling is 110. All values are fictional and kept separate from the provider’s cost, from billing and from payment. Taking advance payments for the barbershop’s services is left out of every offer.

Fulfilling C0 without buying C1 concludes a discovery. Stages that were never contracted are not left waiting and are not counted as failures. Interrupting an active C1 before it is fulfilled is a different outcome, and its effects and remaining obligations have to be dealt with.

Hybrid and autonomous configurations use the same case. The authorities of the buyer, the provider and the environment stay distinct even when decisions are delegated.

In this section

• Intent to production follows the demand from the first request through discovery, the offer, the choice to continue, production and deployment.
• Reference pipeline details the five transformations, their contracts, acceptances, returns and two configurations of execution.
• Reference architecture organizes the records and responsibilities that let the pipeline be carried out.
• State machine makes the demand’s situation concrete, as one possible illustration.
• Example Delivery Unit gathers the whole case: rules, commitments, amounts, evidence and the alternative endings.