Every number on this page is computed by the Chapter 16 notebook's own code, on the book's 100,000 paths (seed 8); the twin's drift is the notebook's declaration (seed 26116). Your notes stay on this page until you leave it; copy the memo before you go.
Meridian's board will decide whether to commission an optimization platform and learning tools for its transformation. You prepare the readiness pack: the four gates, their artifacts, and the work orders, on the Meridian model.
Use AXIOM to run the readiness chain end to end, trace a result to its foundations, and hand a certified instance to Volume II.
Worked Example 16.1: the digital program approved with Chapter 15's risk package, a $170 million standby line and a delay of two months; the declaration as it stood after Chapter 8 and as it stands now; Chapter 14's coupling register; Chapter 8's 100,000 paths (seed 8).
Walk the volume's map and the five ledgers' contracts on Meridian; open the coupling register and the inventory of commitments.
The seven moves of the DCT Map run as a loop (Definition 16.2); the gates sit where the representation is handed to analysis (R1), where the unified system is handed to certification (R2), and before anything is optimized (R3, R4). Click a move.
Meridian's evidence recomputed from the declarations by the Chapter 16 notebook.
Worked Example 4.1: two engineering units with the same declared headcount of 500 but different skill mixes. A model that declares only totals gives both the same answer.
Run the readiness chain (R1)–(R4) interactively. Reproduce the (R1) gaps (the levers' prices and the scorecard's scale) and the (R2) failure of the joint check; then apply the Chapter 15 package and watch the certificates issue.
Inject a drift into one gain of the feedback core and watch the gain audit flag it; attribute the violation and list the certificates it voids. Then declare the phase-two link at 0.40 and read the stability certificate fail.
10,000 models that keep every sign and size within the ceilings, Aij = Mijuij with uij uniform on [−1, 1]: the largest total echo of a $10 million shock at Digital, quarter by quarter, against the register's own, 10 × 0.8k (Online Appendix 16.B.2).
The risk office reads the four links each quarter with an error of ±0.02; the Digital–engineering link drifts up 0.02 a quarter from quarter 4. Within 0.02 of the ceiling is a thin pass; more than 0.02 above it is a flag. The book prints no numbers for this part: the scenario is the notebook's declaration (seed 26116).
Trace Theorem 16.4 to the results it rests on; find the longest chain of citations and where it ends.
Each dot is a numbered result, placed by chapter (left to right) and by the length of the longest chain of citations below it (bottom to top). Click a dot to trace it. Filled: the results it rests on; the line: its longest chain (Online Appendix 16.B.1).
Rows cite, columns are cited, chapters 1–16. Every count lies on or below the diagonal.
Export the certified instance in the canonical form that Volume II's method modules consume.
A consumer that reads only the document, regenerates the environment from its declaration and solves the problem finds the certified package again: the export is complete.
Readiness is won mostly by declarations (Theorem 16.4); the register's certificates hold for every model within its ceilings (Theorem 16.5(ii)); and a pass is only as strong as its margin against the error of the reading behind it.
The four gates with their artifacts and grades; the work orders with their owners; the certified instance; and the conditions under which the certificate lapses.