Capstone: Publish the Business Truth Map

The entity map looks tidy. The lifecycle stages have names. The handoff matrix lists owners. Then Priya's record becomes Sales-ready before Sales accepts, Acme becomes Customer because an Opportunity happens to be late in the pipeline, and one task update changes three unrelated statuses at once. Every table can look sensible in isolation. Only a full trace shows whether the model actually works as one system.

Run the records, not the headings

The capstone starts a fresh canonical trace and runs the whole map against a sequence of business events. Every transition needs its evidence, writer, owner, milestone treatment, valid exit, and reporting use. Every transition also needs to prove that changing one dimension doesn't silently rewrite another.

The trace, start to finish

Acme starts as Target. Priya downloads a guide, then requests a walkthrough, and her lifecycle moves to Engaged; Acme stays Target. Sales accepts the handoff: Priya moves to Sales-ready, and Acme can move to Prospect under its own rule. Sales creates the Opportunity. A work-status-only update, Sales follow-up to Discovery call scheduled, leaves every other dimension exactly where it was. The Opportunity advances to Solution review complete. Finally, the approved commercial activation event changes Acme to Customer.

What this actually buys you

A Business Truth Map that passes its own capstone means Marketing, Sales, Customer Success, Finance, and Operations can build on the same set of facts without re-litigating what a status means every time a workflow needs a decision. The map you version today is also the one you'll amend, not rebuild, the next time the business changes.