The demo works

A clinic manager asks for an intake dashboard. Twenty minutes later she has one.

There is a form. Patients fill it in. There is a queue, and the staff can see it. There is a text message that confirms the appointment, and it arrives. She clicks through a normal patient, then another, then a third. Everything works. The page renders, the form submits, the dashboard is clean, and the system says it is ready.

Now try a patient who reports chest pain. The form submits. The queue shows the name, in arrival order, between a routine follow-up and a prescription renewal. Nothing flagged it, because nothing was told to. Now read the confirmation text. It says: "Your appointment for chest pain is confirmed." A visit reason, sent in the clear, to a phone that might not be the patient's.

Neither failure was visible on the happy path. Nothing in the demo was wrong. The manager asked for a dashboard and got one; the system built what it was asked for. The requirement that urgent symptoms route to a nurse, and the rule that a text must not carry a diagnosis, were never stated because in her world they do not need stating. They are the water the clinic swims in.

An artifact is a proposal. Readiness requires evidence of behavior.

The clinic is the paper's running example, and it runs through every chapter here. It is intentionally ordinary. Swap the world and the structure holds: self-approval in an expense tool, refund authority in a support agent, a repository invariant no visible test covers.