Every number on this page is computed by the Chapter 13 notebook's own code. The breach odds are Worked Example 8.1's paths, drawn with the book's seed 8. Your notes stay on this page until you leave it; copy the memo before you go.
Meridian's board wants one integrated view of the digital program before it approves the second phase. Treasury, the transformation office, and the risk office each bring a model and a sign-off; the chair wants to know whether the models describe one company, whether a problem in one office can become a problem in another, and whether the sign-offs hold together. You are on the team that builds the integrated view.
Use AXIOM to assemble Meridian's unified architecture, trace cross-ledger effects, audit the declaration's consistency, and compare separated decisions with the integrated one.
Worked Example 13.1; Table 13.1: Chapter 9's skeleton with the capital, performance, risk and transformation layers on it; the digital program of Chapters 1 and 8.
In the UETA assembler, attach the layers to Meridian's skeleton in two different orders, confirm that the result is the same, and read the compatibility checks (C1)–(C5) at each attachment.
(C1) every carrier, support, write set and buffer is a component; (C2) an indicator read by two layers carries one contract; (C3) every risk buffer is named to a declared capital stock; (C4) the layers' constraints have a joint solution, for Meridian the claims on treasury cash; (C5) operator domains recomputed against it (Definition 13.4).
In the interaction-matrix editor, enter coupling gains between layers and watch ρ(M) and the share owed to each block; build a case in which every layer is stable and the whole is not.
Three layers, capital → performance → risk → capital, rows receiving: ℓk+1 = M ℓk. Left: the cumulative bill of a unit loss at capital, quarter by quarter, against each layer alone. The spectral report splits ρ(M) between the diagonal blocks and the cross-layer blocks (Theorem 13.3(ii); Online Appendix 13.B.1).
In the layered wavefront simulator, seed the digital program at Digital and a demand shock at the market in the same quarter, and record the first quarter in which each ledger can respond.
A readout moves no sooner than the distance from the seed to its support, and never if its support cannot be reached (Proposition 13.2; Theorem 13.4(iii)). Supports: capital (Table 9.1), performance (Table 11.4), risk (Tables 9.3 and 12.2).
In the consistency auditor, load the funding, buffer, and schedule sign-offs of Worked Example 13.1; confirm that each bilateral check passes and the joint check fails, then repair it three ways.
Chapter 8's quarterly plan against the buffer line, the floor plus the closure buffer: where liquidity runs inside it, the buffer is promised and spent at once.
In the integrated program theater, run the program through all ledgers on one clock and compare the separated verdicts with the unified one.
Chapter 1's model, month by month, read in three ledgers: capital (liquidity against the $350 million floor), performance (the CFO's scorecard against today's 37.0), risk (strategic risk against its ceiling of 75, measured to ±6).
Each repair read in every ledger: the joint check of the claims on treasury cash, and the breach odds over Chapter 8's 100,000 paths (seed 8) against the 5 percent appetite (Proposition 13.5).
The layers are returned unchanged by the assembly (Theorem 13.1(iii)); the whole can be unstable while every layer is stable (Theorem 13.3(ii)); no ledger responds before its layered distance allows (Theorem 13.4(iii)); bilateral checks pass on a cycle that the joint check fails (Theorem 13.5(iii)); and separated decisions lose exactly what the couplings carry (Proposition 13.5).
The coupling register; the interaction matrix's zero blocks and spectral report; the ledger-clock table for the digital program; the consistency audit with the capital–performance–risk cycle walked as one constraint; and the integrated recommendation, with the cost of deciding separately.