caustino commited on
Commit
6b1772e
·
verified ·
1 Parent(s): 82df7b8

Update index.html

Browse files
Files changed (1) hide show
  1. index.html +883 -18
index.html CHANGED
@@ -1,19 +1,884 @@
1
- <!doctype html>
2
- <html>
3
- <head>
4
- <meta charset="utf-8" />
5
- <meta name="viewport" content="width=device-width" />
6
- <title>My static Space</title>
7
- <link rel="stylesheet" href="style.css" />
8
- </head>
9
- <body>
10
- <div class="card">
11
- <h1>Welcome to your static Space!</h1>
12
- <p>You can modify this app directly by editing <i>index.html</i> in the Files and versions tab.</p>
13
- <p>
14
- Also don't forget to check the
15
- <a href="https://huggingface.co/docs/hub/spaces" target="_blank">Spaces documentation</a>.
16
- </p>
17
- </div>
18
- </body>
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
19
  </html>
 
1
+ <!DOCTYPE html>
2
+ <html lang="en">
3
+ <head>
4
+ <meta charset="UTF-8">
5
+ <title>THE MERCY PROTOCOL — A Book of Systems, Wounds, and the Architecture of Repair</title>
6
+ <style>
7
+ @page { size: Letter; margin: 1in; @bottom-center { content: counter(page); font-size: 10pt; color:#555; } }
8
+ html { font-family: "Georgia", "Times New Roman", serif; font-size: 11pt; line-height: 1.55; color:#1a1a1a; }
9
+ body { max-width: 6.5in; margin: 0 auto; }
10
+ h1,h2,h3,h4 { font-family: "Helvetica Neue", "Arial", sans-serif; color:#1B1B3A; }
11
+ h1.part-title { text-align:center; font-size: 26pt; margin-top: 1.5in; margin-bottom: 0.5in; border-top: 3px double #1B1B3A; border-bottom: 3px double #1B1B3A; padding: 18pt 0; color:#8B0000; page-break-before: always; }
12
+ h1.chapter { font-size: 20pt; border-bottom: 2px solid #8B0000; padding-bottom: 6pt; margin-top: 36pt; page-break-before: always; }
13
+ h2 { font-size: 14pt; margin-top: 22pt; }
14
+ .preface h1.chapter { page-break-before: avoid; }
15
+ .dedication { text-align:center; font-style: italic; margin: 2in 0; }
16
+ .dedication-box { background: #1B1B3A; color: white; padding: 22pt; margin: 28pt 0; border-radius: 4pt; }
17
+ .dedication-box h3 { color: #C9A227; margin-top: 0; text-align:center; }
18
+ .metaphor { background: #F5F5F5; border-left: 4pt solid #1B1B3A; padding: 10pt 14pt; margin: 16pt 0; border-radius: 2pt; }
19
+ .metaphor .label { font-weight: bold; font-family: sans-serif; text-transform: uppercase; font-size: 9pt; letter-spacing: 1pt; color:#1B1B3A; display:block; margin-bottom:4pt; }
20
+ .phd { background: #faf5e4; border-left: 4pt solid #C9A227; padding: 10pt 14pt; margin: 16pt 0; border-radius: 2pt; }
21
+ .phd .label { font-weight: bold; font-family: sans-serif; text-transform: uppercase; font-size: 9pt; letter-spacing: 1pt; color:#8a6d00; display:block; margin-bottom:4pt; }
22
+ .peer { background: #e8f0fb; border-left: 4pt solid #1565C0; padding: 10pt 14pt; margin: 16pt 0; border-radius: 2pt; font-size: 10.5pt; }
23
+ .peer .label { font-weight: bold; font-family: sans-serif; text-transform: uppercase; font-size: 9pt; letter-spacing: 1pt; color:#0d47a1; display:block; margin-bottom:4pt; }
24
+ .shot { background: #f0f0f7; border-left: 4pt solid #1B1B3A; padding: 10pt 14pt; margin: 16pt 0; border-radius: 2pt; }
25
+ .shot .label { font-weight: bold; font-family: sans-serif; text-transform: uppercase; font-size: 9pt; letter-spacing: 1pt; color:#1B1B3A; display:block; margin-bottom:4pt; }
26
+ .cobol { background: #e8eefb; border-left: 4pt solid #0033A0; padding: 10pt 14pt; margin: 16pt 0; border-radius: 2pt; }
27
+ .cobol .label { font-weight: bold; font-family: sans-serif; text-transform: uppercase; font-size: 9pt; letter-spacing: 1pt; color:#0033A0; display:block; margin-bottom:4pt; }
28
+ .copernicus { background: #fbeaea; border-left: 4pt solid #8B0000; padding: 10pt 14pt; margin: 16pt 0; border-radius: 2pt; }
29
+ .copernicus .label { font-weight: bold; font-family: sans-serif; text-transform: uppercase; font-size: 9pt; letter-spacing: 1pt; color:#8B0000; display:block; margin-bottom:4pt; }
30
+ figure { margin: 22pt 0; text-align:center; page-break-inside: avoid; }
31
+ figcaption { font-size: 9.5pt; color:#444; margin-top:8pt; font-style: italic; }
32
+ pre { background:#f7f7f7; border:1pt solid #ddd; padding:10pt; font-size: 9pt; overflow-x:auto; border-radius: 2pt; }
33
+ .algorithm { background: #fcfbf7; border: 1pt solid #C9A227; border-radius: 3pt; margin:16pt 0; padding: 0 14pt 12pt 14pt; page-break-inside: avoid; }
34
+ .algorithm h4 { color:#8a6d00; margin-top: 12pt; font-family: sans-serif; font-size: 10.5pt; }
35
+ .algorithm pre { background: transparent; border: none; padding: 0; }
36
+ ul, ol { padding-left: 22pt; }
37
+ table { border-collapse: collapse; width: 100%; margin: 14pt 0; font-size: 10pt; }
38
+ th, td { border: 1pt solid #ccc; padding: 6pt 8pt; text-align: left; vertical-align: top; }
39
+ th { background: #1B1B3A; color: white; font-family: sans-serif; }
40
+ .twocol { display: grid; grid-template-columns: 1fr 1fr; gap: 18pt; }
41
+ .huggingface { text-align:center; margin: 30pt 0; font-family: sans-serif; }
42
+ .huggingface a { color:#1565C0; text-decoration: none; font-weight: bold; font-size: 13pt; }
43
+ .math { font-family: "Cambria Math", "Latin Modern Math", Georgia, serif; font-style: italic; }
44
+ .toc { page-break-after: always; }
45
+ .toc h2 { text-align:center; }
46
+ .toc ul { list-style: none; padding-left:0; }
47
+ .toc li { margin: 5pt 0; }
48
+ .toc li.part { font-weight: bold; margin-top:10pt; font-family: sans-serif; color:#1B1B3A; }
49
+ .cover .cover-subtitle { max-width: 5.5in; margin: 0 auto; }
50
+ </style>
51
+ </head>
52
+ <body>
53
+
54
+ <!-- COVER -->
55
+ <section style="height: 9in; display: flex; flex-direction: column; justify-content: center; align-items: center; text-align: center; page-break-after: always;">
56
+ <div style="border: 4px double #1B1B3A; padding: 40pt 60pt;">
57
+ <div style="font-family: sans-serif; font-size: 10pt; letter-spacing: 2pt; color:#8B0000; text-transform: uppercase; margin-bottom: 20pt;">Technical · Legal · Social Systems</div>
58
+ <h1 style="font-family: sans-serif; font-size: 36pt; color:#1B1B3A; margin:0; line-height:1.2;">THE MERCY<br>PROTOCOL</h1>
59
+ <div style="font-family: Georgia, serif; font-style: italic; font-size: 14pt; color:#333; margin: 24pt 0; max-width: 4.5in;">A Book of Systems, Wounds, and the Architecture of Repair<br><br>With a Copernican dedication to COBOL and the quiet engineers of the administrative state</div>
60
+ <div style="font-family: sans-serif; font-size: 12pt; margin-top: 30pt; color:#1565C0;">
61
+ Caustino<br>
62
+ <a href="https://huggingface.co/caustino">huggingface.co/caustino</a><br>
63
+ <span style="font-size:10pt; color:#666;">2026</span>
64
+ </div>
65
+ </div>
66
+ </section>
67
+
68
+ <!-- DEDICATION -->
69
+ <section class="dedication">
70
+ <p>Dedicated to Grace Murray Hopper, who taught a machine to read English<br>
71
+ so that ordinary people might read what the machine writes;<br>
72
+ and to the millions who have waited in queues they did not design,<br>
73
+ for benefits they had already earned.</p>
74
+
75
+ <div class="dedication-box">
76
+ <h3>THE COPERNICAN DEDICATION TO COBOL</h3>
77
+ <p>When the heavens were re-centered from the Earth to the Sun, nothing in
78
+ the sky moved an inch — but everything in how humans saw the world changed.
79
+ So too with COBOL: when we re-center the administrative state from the
80
+ <em>agency</em> to the <em>person</em>, not a single line of legacy code needs to
81
+ vanish, but the justice produced by that code is transformed.</p>
82
+ <p>Grace Hopper did not write COBOL because she loved mainframes. She wrote it
83
+ because she believed business logic should be legible to the people whose
84
+ lives it governs. Sixty-six years later, 70–80% of the world's financial
85
+ transactions still run on COBOL; and yet the very same clarity-of-language
86
+ principle that birthed COBOL is the principle we must now carry forward into
87
+ the post-quantum, genomic, algorithmic era. This book is an attempt to do
88
+ exactly that.</p>
89
+ </div>
90
+ </section>
91
+
92
+ <!-- TOC -->
93
+ <section class="toc">
94
+ <h2>Contents</h2>
95
+ <ul>
96
+ <li class="part">Preface: The Shape of the Problem</li>
97
+ <li class="part">Part I — The Wound</li>
98
+ <li>1. The Queue That Kills</li>
99
+ <li>2. The Genome as a Book That Cannot Be Rewritten</li>
100
+ <li>3. The Administrative Recidivism Loop</li>
101
+ <li class="part">Part II — The Ghost in the Genome</li>
102
+ <li>4. The Cryptographic Envelope</li>
103
+ <li>5. The Audit Ledger as Unblinking Memory</li>
104
+ <li>6. The Judicial Escrow: When the State Must See</li>
105
+ <li class="part">Part III — See (The Eyes of the System)</li>
106
+ <li>7. What It Means to See a Claimant</li>
107
+ <li>8. HSPA v3.0 — Homomorphic Scoring</li>
108
+ <li>9. The Claim-Evidence Chain</li>
109
+ <li class="part">Part IV — Remember (The Ledger as Institutional Memory)</li>
110
+ <li>10. What the State Forgets</li>
111
+ <li>11. Immutable Recordkeeping in a Post-Quantum World</li>
112
+ <li class="part">Part V — Reason (MORTAR and the Mathematics of Triage)</li>
113
+ <li>12. Why First-In-First-Out Is a Moral Choice</li>
114
+ <li>13. Reproducibility as a Procedural Right</li>
115
+ <li>14. The Ramp, Not the Cliff</li>
116
+ <li class="part">Copernican Interlude — Why COBOL Matters Here</li>
117
+ <li class="part">Part VI — Endure (Finance, Law, and the Political Cycle)</li>
118
+ <li>15. The Political-Cycle Problem</li>
119
+ <li>16. The Capital Structure</li>
120
+ <li>17. The Legal Superstructure</li>
121
+ <li>18. The Future We Are Trying to Reach</li>
122
+ <li class="part">References</li>
123
+ </ul>
124
+ </section>
125
+
126
+ <!-- PREFACE -->
127
+ <section class="preface">
128
+ <h1 class="chapter">Preface: The Shape of the Problem</h1>
129
+
130
+ <div class="shot"><span class="label">Cinematic Shot — Establishing, aerial, dawn</span>
131
+ A river winds between concrete levees. From above you can see the flow slow,
132
+ then stall. Boats — thousands of them, each carrying a person, a file, a
133
+ claim — rest on water that no longer moves. Some have been there so long
134
+ their hulls have taken on water. The camera tilts down. A paper file rests
135
+ on a desk inside a federal building; a stamp says "PENDING."
136
+ </div>
137
+
138
+ <p>There is a river that runs through the American administrative state. It
139
+ was designed to carry people from injury to remedy, from diagnosis to
140
+ support, from need to the means of living. For most of the twentieth
141
+ century, it moved with a certain bureaucratic sluggishness — slow, but
142
+ forward. In the twenty-first century, the river has backed up. It has
143
+ become a pond, then a swamp, then a place where people go to wait and some
144
+ of them do not come out.</p>
145
+
146
+ <p>The Social Security Administration's disability adjudication system is
147
+ not a failure of malice. It is a failure of scale — a system designed for a
148
+ world of paper and human clerks, now processing the claims of a nation with
149
+ the tools of a bygone era. The numbers are stark: over one million claims
150
+ pending, average waits measured in hundreds of days, and deaths — tens of
151
+ thousands per year — among those waiting.<sup>[1,2]</sup> These are not
152
+ abstract statistics. They are the human cost of a system that cannot see
153
+ the people inside its queue.</p>
154
+
155
+ <p>This book is about a response to that failure — and to a cluster of
156
+ related failures that share a common root. The root is this:
157
+ <strong>the institutions that hold the most sensitive information about us
158
+ — our genomes, our neurophysiology, our administrative records, our
159
+ financial identities — are constrained by instruments drafted for a world
160
+ in which such information was either impossible or expensive to
161
+ collect.</strong> The genome is the clearest case. It is immutable, it
162
+ identifies without being intended to identify, it implicates relatives who
163
+ never consented, and the statute that governs it reaches only health
164
+ insurance and employment. The gap between the sensitivity of the data and
165
+ the enforceability of the duty is not a single wrong. It is a structural
166
+ under-protection that appears as a civil-rights claim in one forum, as an
167
+ evidentiary problem in another, and as a queue in a third.</p>
168
+
169
+ <p>The response described in this book is called the MERCY Protocol — a name
170
+ chosen not for sentiment but for precision. Mercy, in the administrative
171
+ sense, is the act of seeing a person where the system sees only a case
172
+ number. The Protocol is a <strong>stack of systems</strong> that together
173
+ attempt to do four things:</p>
174
+ <ol>
175
+ <li><strong>See</strong> — detect the people at risk, before the queue kills them;</li>
176
+ <li><strong>Remember</strong> — create an immutable, auditable record of what was done and why, signed against a post-quantum future;</li>
177
+ <li><strong>Reason</strong> — apply triage and evidence standards that are fair, transparent, and reproducible;</li>
178
+ <li><strong>Endure</strong> — build a financial and legal structure that can outlast the political cycles that otherwise doom such efforts.</li>
179
+ </ol>
180
+ <p>Each layer is necessary. None is sufficient alone.</p>
181
+
182
+ <div class="copernicus"><span class="label">The Copernican Turn</span>
183
+ The MERCY Protocol is a Copernican move. For seventy years, the
184
+ administrative state has placed the <em>agency</em> at the center of the
185
+ universe, with the claimant orbiting it, waiting for light to arrive from
186
+ the center. The Protocol moves the <em>person</em> to the center. The
187
+ agency, the courts, the trustees, the nodes, the ledgers, the cryptographic
188
+ keys — all orbit the person whose life is at stake. Nothing in statute
189
+ changes; everything in justice does.
190
+ </div>
191
+
192
+ <p>The book is organized as a narrative, moving from the wound to the
193
+ architecture to the implementation. Along the way I use diagrams and
194
+ cinematic metaphors to make the systems visible, because the only way to
195
+ hold a system this large in a human mind is to see it as something else: a
196
+ river, a ledger, a flock, a heart, a ramp.</p>
197
+ </section>
198
+
199
+ <!-- PART I -->
200
+ <h1 class="part-title">PART I — THE WOUND</h1>
201
+
202
+ <h1 class="chapter">1. The Queue That Kills</h1>
203
+
204
+ <div class="shot"><span class="label">Cinematic Shot — Wide, hospital ER, stripped of staff</span>
205
+ The triage desk has been replaced by a large, slowly advancing clock.
206
+ Patients take a number and sit on benches that stretch out of frame. Some
207
+ hold bleeding wounds; some are unconscious; some sit very still. The clock
208
+ ticks. No one is called.
209
+ </div>
210
+
211
+ <p>Imagine a hospital where the triage nurse has been replaced by a clock.
212
+ Everyone who arrives is given a number. The number is the time of arrival.
213
+ The clock advances. When your number is called, you are seen. The clock
214
+ does not care whether you are bleeding, whether you are unconscious,
215
+ whether you have hours or years. It only knows the order of arrival.</p>
216
+
217
+ <p>This is the SSA disability queue. It is fair in the narrow sense: it
218
+ treats everyone the same. It is lethal in the broader sense: it treats
219
+ everyone the same regardless of how much the delay will cost them.</p>
220
+
221
+ <p>The Government Accountability Office documented that over a decade, more
222
+ than <strong>110,000</strong> appellants died while their claims were
223
+ pending.<sup>[1]</sup> The SSA's own Office of the Chief Actuary estimated
224
+ <strong>33,270 deaths</strong> in FY2023 among those awaiting a decision at
225
+ the DDS or ALJ level.<sup>[2]</sup> The average wait for an ALJ hearing
226
+ exceeded <strong>230 days</strong> in FY2024, up 86 percent from 2019. The
227
+ federal court remand rate — the proportion of cases sent back because the
228
+ agency got it wrong — rose to <strong>62 percent</strong>. Of those
229
+ remanded, roughly two-thirds were ultimately awarded benefits. <strong>The
230
+ delay itself is the denial mechanism.</strong> A claim that is approved
231
+ after two years is not a claim that was approved. It is a claim that was
232
+ denied for two years and then, belatedly, recognized.</p>
233
+
234
+ <figure>
235
+ <svg viewBox="0 0 600 200" width="100%" role="img" aria-label="Queue as Sorted List">
236
+ <defs>
237
+ <marker id="arr" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="6" markerHeight="6" orient="auto">
238
+ <path d="M0,0 L10,5 L0,10 z" fill="#555"/>
239
+ </marker>
240
+ </defs>
241
+ <!-- Time axis -->
242
+ <line x1="30" y1="110" x2="570" y2="110" stroke="#333" stroke-width="1.5" marker-end="url(#arr)"/>
243
+ <text x="575" y="115" font-size="11" font-family="sans-serif" fill="#333">Time</text>
244
+ <!-- Claims in FIFO boxes -->
245
+ <g font-family="sans-serif" font-size="11">
246
+ <g><rect x="50" y="65" width="45" height="35" fill="#fff" stroke="#1B1B3A" stroke-width="1.2" rx="3"/><text x="72" y="87" text-anchor="middle">[1]</text></g>
247
+ <g><rect x="110" y="65" width="45" height="35" fill="#fff" stroke="#1B1B3A" stroke-width="1.2" rx="3"/><text x="132" y="87" text-anchor="middle">[2]</text></g>
248
+ <g><rect x="170" y="65" width="45" height="35" fill="#fff" stroke="#1B1B3A" stroke-width="1.2" rx="3"/><text x="192" y="87" text-anchor="middle">[3]</text></g>
249
+ <g><rect x="230" y="65" width="45" height="35" fill="#fff" stroke="#1B1B3A" stroke-width="1.2" rx="3"/><text x="252" y="87" text-anchor="middle">[4]</text></g>
250
+ <g><rect x="290" y="65" width="45" height="35" fill="#fff" stroke="#1B1B3A" stroke-width="1.2" rx="3"/><text x="312" y="87" text-anchor="middle">[5]</text></g>
251
+ <g><rect x="350" y="65" width="45" height="35" fill="#fff" stroke="#1B1B3A" stroke-width="1.2" rx="3"/><text x="372" y="87" text-anchor="middle">[6]</text></g>
252
+ <g><rect x="410" y="65" width="45" height="35" fill="#fff" stroke="#1B1B3A" stroke-width="1.2" rx="3"/><text x="432" y="87" text-anchor="middle">[7]</text></g>
253
+ <g><rect x="470" y="65" width="45" height="35" fill="#fff" stroke="#1B1B3A" stroke-width="1.2" rx="3"/><text x="492" y="87" text-anchor="middle">[8]</text></g>
254
+ </g>
255
+ <text x="300" y="45" font-family="sans-serif" font-size="12" font-weight="bold" text-anchor="middle">Claims arrive → FIFO sorted list → Decisions issue</text>
256
+ <!-- Death marker -->
257
+ <line x1="250" y1="120" x2="250" y2="175" stroke="#8B0000" stroke-width="1.4" stroke-dasharray="4,3"/>
258
+ <text x="252" y="190" font-family="sans-serif" font-size="10" fill="#8B0000" font-weight="bold">Deaths while waiting</text>
259
+ <text x="300" y="145" font-family="sans-serif" font-size="10" fill="#333" text-anchor="middle">The system is blind to risk.</text>
260
+ </svg>
261
+ <figcaption>Diagram 1. The Queue as a Sorted List (vector redrawing).</figcaption>
262
+ </figure>
263
+
264
+ <p><strong>Result.</strong> The system has <em>no mechanism</em> to ask:
265
+ <em>"Who among these is most likely to die before their number is
266
+ called?"</em> It is <em>formally</em> fair, treating everyone identically.
267
+ It is <em>substantively</em> lethal, because identical treatment is not
268
+ equitable treatment when the people are not identically situated.</p>
269
+
270
+ <div class="metaphor"><span class="label">Metaphor</span>
271
+ The queue is a river that has stopped moving. A river that flows carries
272
+ silt and debris and also carries boats. A river that stops becomes a swamp.
273
+ The boats do not move. Some of them sink. The swamp does not notice. It is
274
+ water. It is doing what water does when it is not moving. The failure is
275
+ not in the water. The failure is in the absence of a current.
276
+ </div>
277
+
278
+ <div class="phd"><span class="label">PhD-level Complexity</span>
279
+ The queue is a <strong>priority queue with a single key</strong> (arrival
280
+ time). The optimal solution, in operations-research terms, is a
281
+ <strong>multi-objective scheduling problem</strong> where objectives include
282
+ throughput, fairness, and <strong>mortality risk</strong>. The MORTAR
283
+ engine (Part V) is the formal solution: a composite priority score
284
+ combining medical risk, socioeconomic vulnerability, and wait time, with an
285
+ <em>anti-starvation guarantee</em> that no claim waits beyond a bounded
286
+ time.
287
+ </div>
288
+
289
+ <div class="peer"><span class="label">Peer-Reviewed Anchor</span>
290
+ Gelber, Moore &amp; Strand (2023) estimate that an additional $1,000 in
291
+ annual DI income reduces beneficiary mortality by 0.18–0.35 percentage
292
+ points, demonstrating that delay is not merely inconvenient but
293
+ mortality-implicated.<sup>[3]</sup> Deshpande &amp; Mueller-Smith (2022)
294
+ show that removal from SSI at age 18 increases criminal charges by 20%,
295
+ income-generating offenses by 60%, and incarceration likelihood by
296
+ 60%,<sup>[4]</sup> tracing downstream costs of the queue into the
297
+ criminal-legal system.
298
+ </div>
299
+
300
+ <h1 class="chapter">2. The Genome as a Book That Cannot Be Rewritten</h1>
301
+
302
+ <p>The genome is not a medical record. A medical record describes what
303
+ happened to you. A genome describes what you are, what you might become,
304
+ and what you share with everyone to whom you are related. It is immutable
305
+ — you cannot change it. It is uniquely identifying — your genome is yours
306
+ alone. It is predictive — it carries probabilistic information about future
307
+ disease. It is relational — it reveals information about parents, siblings,
308
+ and children who never consented to anything. And it is persistently
309
+ sensitive — as science advances, the same data reveals more.</p>
310
+
311
+ <figure>
312
+ <svg viewBox="0 0 500 320" width="100%" role="img" aria-label="Five Properties of Genomic Information">
313
+ <!-- center -->
314
+ <rect x="150" y="130" width="200" height="60" rx="6" fill="#fbeaea" stroke="#8B0000" stroke-width="1.5"/>
315
+ <text x="250" y="155" font-family="sans-serif" font-size="13" font-weight="bold" text-anchor="middle">THE GENOME</text>
316
+ <text x="250" y="175" font-family="sans-serif" font-size="9" text-anchor="middle">3.2 billion base pairs, one per person</text>
317
+ <!-- 5 spokes -->
318
+ <g font-family="sans-serif" font-size="10">
319
+ <g>
320
+ <rect x="30" y="20" width="110" height="70" rx="4" fill="#fff5f5" stroke="#8B0000" stroke-width="1"/>
321
+ <text x="85" y="40" font-weight="bold" text-anchor="middle">IMMUTABLE</text>
322
+ <text x="85" y="60" text-anchor="middle" font-size="9">Cannot change</text>
323
+ <text x="85" y="74" text-anchor="middle" font-size="9">after breach</text>
324
+ <line x1="150" y1="140" x2="140" y2="90" stroke="#8B0000" stroke-width="0.8" marker-end="url(#arr)"/>
325
+ </g>
326
+ <g>
327
+ <rect x="360" y="20" width="110" height="70" rx="4" fill="#faf5e4" stroke="#C9A227" stroke-width="1"/>
328
+ <text x="415" y="40" font-weight="bold" text-anchor="middle">UNIQUELY</text>
329
+ <text x="415" y="55" font-weight="bold" text-anchor="middle">IDENTIFYING</text>
330
+ <text x="415" y="74" text-anchor="middle" font-size="9">Yours alone</text>
331
+ <line x1="350" y1="140" x2="360" y2="90" stroke="#C9A227" stroke-width="0.8" marker-end="url(#arr)"/>
332
+ </g>
333
+ <g>
334
+ <rect x="20" y="230" width="110" height="70" rx="4" fill="#eaf5ea" stroke="#2E7D32" stroke-width="1"/>
335
+ <text x="75" y="250" font-weight="bold" text-anchor="middle">PREDICTIVE</text>
336
+ <text x="75" y="270" text-anchor="middle" font-size="9">Probabilistic</text>
337
+ <text x="75" y="284" text-anchor="middle" font-size="9">future health risks</text>
338
+ <line x1="160" y1="190" x2="130" y2="230" stroke="#2E7D32" stroke-width="0.8" marker-end="url(#arr)"/>
339
+ </g>
340
+ <g>
341
+ <rect x="195" y="240" width="110" height="70" rx="4" fill="#e8f0fb" stroke="#1565C0" stroke-width="1"/>
342
+ <text x="250" y="260" font-weight="bold" text-anchor="middle">RELATIONAL</text>
343
+ <text x="250" y="280" text-anchor="middle" font-size="9">Reveals data about</text>
344
+ <text x="250" y="294" text-anchor="middle" font-size="9">relatives who never consented</text>
345
+ <line x1="250" y1="190" x2="250" y2="240" stroke="#1565C0" stroke-width="0.8" marker-end="url(#arr)"/>
346
+ </g>
347
+ <g>
348
+ <rect x="370" y="230" width="110" height="70" rx="4" fill="#eee8fb" stroke="#311B92" stroke-width="1"/>
349
+ <text x="425" y="250" font-weight="bold" text-anchor="middle">PERSISTENTLY</text>
350
+ <text x="425" y="265" font-weight="bold" text-anchor="middle">SENSITIVE</text>
351
+ <text x="425" y="284" text-anchor="middle" font-size="9">Becomes more</text>
352
+ <text x="425" y="298" text-anchor="middle" font-size="9">revealing over time</text>
353
+ <line x1="340" y1="190" x2="370" y2="230" stroke="#311B92" stroke-width="0.8" marker-end="url(#arr)"/>
354
+ </g>
355
+ </g>
356
+ </svg>
357
+ <figcaption>Diagram 2. The Five Properties of Genomic Information.</figcaption>
358
+ </figure>
359
+
360
+ <p><strong>The legal problem.</strong> Existing privacy frameworks (HIPAA,
361
+ GINA) were drafted for a world of paper medical records and rare genetic
362
+ data. The genome breaks every category:</p>
363
+ <ul>
364
+ <li>HIPAA covers "protected health information" held by covered entities.
365
+ It does not cover direct-to-consumer genomic data.</li>
366
+ <li>GINA prohibits genetic discrimination in health insurance and
367
+ employment. It does not cover life insurance, disability insurance, or
368
+ long-term care.</li>
369
+ <li>The Third-Party Doctrine (<em>Smith v. Maryland</em>, <em>United
370
+ States v. Miller</em>) holds that information voluntarily given to a
371
+ third party loses Fourth Amendment protection. Applied mechanically to
372
+ genomic data, this would extinguish constitutional protection for data
373
+ disclosed to a testing company.</li>
374
+ </ul>
375
+
376
+ <div class="metaphor"><span class="label">Metaphor</span>
377
+ The genome is a book written in a language that is only partially
378
+ understood. Every year, the language becomes more legible. A page that
379
+ today says "increased risk of X" will, in ten years, say "increased risk of
380
+ X, Y, and Z, and also reveals that your sister has the same variant." The
381
+ book cannot be rewritten. It can only be copied. And every copy is a
382
+ potential leak.
383
+ </div>
384
+
385
+ <div class="phd"><span class="label">PhD-level Complexity</span>
386
+ The re-identification problem is formalizable. Let <span class="math">𝒮</span> be a set of <span class="math">k</span> independent SNPs. Under Hardy–Weinberg equilibrium,
387
+ <span class="math">P(𝒢<sub>𝒮</sub>) = ∏ P(g<sub>j</sub>)</span>. The
388
+ probability that an individual is unique in a population of size <span class="math">N</span> is <span class="math">P(ID) = 1 − (1 −
389
+ P(𝒢<sub>𝒮</sub>))<sup>N−1</sup></span>, which tends to 1 as
390
+ <span class="math">k → ∞</span>. Empirically, <span class="math">k ≥
391
+ 50</span> independent SNPs yields P(ID) ≈ 1. <strong>Anonymization of
392
+ high-density genomic data is mathematically impossible without
393
+ cryptographic noise or enclave isolation</strong> — the formal
394
+ justification for the post-quantum stack in Part II.
395
+ </div>
396
+
397
+ <h1 class="chapter">3. The Administrative Recidivism Loop</h1>
398
+
399
+ <p>The disability system does not simply delay. It <strong>recycles</strong>.
400
+ A claim is denied at the initial level. It is denied again at
401
+ reconsideration. It goes to an ALJ, who may deny it or approve it. If
402
+ approved, a continuing disability review may later terminate it. If
403
+ denied, it goes to the Appeals Council, then to federal court, then back
404
+ to the agency. Each cycle costs time. Each cycle costs money. Each cycle
405
+ costs health. The claimant is not moving through a system. The claimant is
406
+ <strong>circulating</strong> through a system that has no exit.</p>
407
+
408
+ <figure>
409
+ <svg viewBox="0 0 560 520" width="100%" role="img" aria-label="Recidivism Feedback Loop">
410
+ <defs>
411
+ <marker id="arr2" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="7" markerHeight="7" orient="auto">
412
+ <path d="M0,0 L10,5 L0,10 z" fill="#555"/>
413
+ </marker>
414
+ <marker id="arrred" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="7" markerHeight="7" orient="auto">
415
+ <path d="M0,0 L10,5 L0,10 z" fill="#8B0000"/>
416
+ </marker>
417
+ </defs>
418
+ <g font-family="sans-serif" font-size="10">
419
+ <rect x="210" y="10" width="140" height="40" rx="4" fill="#fff" stroke="#1B1B3A" stroke-width="1.2"/>
420
+ <text x="280" y="35" text-anchor="middle" font-weight="bold">DISABILITY ONSET</text>
421
+ <line x1="280" y1="50" x2="280" y2="75" stroke="#555" stroke-width="1.2" marker-end="url(#arr2)"/>
422
+
423
+ <rect x="210" y="75" width="140" height="40" rx="4" fill="#fff" stroke="#1B1B3A" stroke-width="1.2"/>
424
+ <text x="280" y="100" text-anchor="middle" font-weight="bold">INITIAL CLAIM</text>
425
+
426
+ <!-- Three denials -->
427
+ <rect x="50" y="150" width="100" height="45" rx="4" fill="#fbeaea" stroke="#8B0000" stroke-width="1"/>
428
+ <text x="100" y="170" text-anchor="middle" font-weight="bold">DENIED</text>
429
+ <text x="100" y="186" text-anchor="middle" font-size="8">(64%)</text>
430
+ <line x1="225" y1="115" x2="150" y2="150" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
431
+
432
+ <rect x="230" y="150" width="100" height="45" rx="4" fill="#fbeaea" stroke="#8B0000" stroke-width="1"/>
433
+ <text x="280" y="170" text-anchor="middle" font-weight="bold">DENIED</text>
434
+ <text x="280" y="186" text-anchor="middle" font-size="8">(84% of appeals)</text>
435
+ <line x1="280" y1="115" x2="280" y2="150" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
436
+
437
+ <rect x="410" y="150" width="100" height="45" rx="4" fill="#fbeaea" stroke="#8B0000" stroke-width="1"/>
438
+ <text x="460" y="170" text-anchor="middle" font-weight="bold">DENIED</text>
439
+ <text x="460" y="186" text-anchor="middle" font-size="8">(ALJ denial)</text>
440
+ <line x1="335" y1="115" x2="410" y2="150" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
441
+
442
+ <!-- Appeal -->
443
+ <rect x="200" y="230" width="160" height="55" rx="4" fill="#fff" stroke="#1B1B3A" stroke-width="1.2"/>
444
+ <text x="280" y="252" text-anchor="middle" font-weight="bold">APPEAL</text>
445
+ <text x="280" y="270" text-anchor="middle" font-size="9">(ALJ, AC, federal court)</text>
446
+ <line x1="100" y1="195" x2="240" y2="230" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
447
+ <line x1="280" y1="195" x2="280" y2="230" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
448
+ <line x1="460" y1="195" x2="320" y2="230" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
449
+
450
+ <!-- Outcomes -->
451
+ <rect x="40" y="320" width="110" height="45" rx="4" fill="#eaf5ea" stroke="#2E7D32" stroke-width="1"/>
452
+ <text x="95" y="340" text-anchor="middle" font-weight="bold">APPROVED</text>
453
+ <text x="95" y="356" text-anchor="middle" font-size="8">(50% at ALJ)</text>
454
+ <line x1="230" y1="285" x2="150" y2="320" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
455
+
456
+ <rect x="225" y="320" width="110" height="45" rx="4" fill="#faf5e4" stroke="#C9A227" stroke-width="1"/>
457
+ <text x="280" y="340" text-anchor="middle" font-weight="bold">REMANDED</text>
458
+ <text x="280" y="356" text-anchor="middle" font-size="8">(62% of fed court)</text>
459
+ <line x1="280" y1="285" x2="280" y2="320" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
460
+
461
+ <rect x="410" y="320" width="110" height="45" rx="4" fill="#fbeaea" stroke="#8B0000" stroke-width="1"/>
462
+ <text x="465" y="340" text-anchor="middle" font-weight="bold">DENIED</text>
463
+ <text x="465" y="356" text-anchor="middle" font-size="8">(final)</text>
464
+ <line x1="330" y1="285" x2="420" y2="320" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
465
+
466
+ <!-- End states -->
467
+ <rect x="40" y="400" width="110" height="35" rx="4" fill="#eaf5ea" stroke="#2E7D32" stroke-width="1"/>
468
+ <text x="95" y="422" text-anchor="middle" font-weight="bold">BENEFITS</text>
469
+ <line x1="95" y1="365" x2="95" y2="400" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
470
+
471
+ <rect x="225" y="400" width="110" height="35" rx="4" fill="#faf5e4" stroke="#C9A227" stroke-width="1"/>
472
+ <text x="280" y="422" text-anchor="middle" font-weight="bold">BACK TO QUEUE</text>
473
+ <line x1="280" y1="365" x2="280" y2="400" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
474
+
475
+ <rect x="410" y="400" width="110" height="35" rx="4" fill="#fbeaea" stroke="#8B0000" stroke-width="1"/>
476
+ <text x="465" y="422" text-anchor="middle" font-weight="bold">COLLAPSE</text>
477
+ <line x1="465" y1="365" x2="465" y2="400" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
478
+
479
+ <rect x="420" y="460" width="120" height="40" rx="4" fill="#f8dede" stroke="#8B0000" stroke-width="1"/>
480
+ <text x="480" y="478" text-anchor="middle" font-size="9" font-weight="bold">HOMELESSNESS /</text>
481
+ <text x="480" y="492" text-anchor="middle" font-size="9" font-weight="bold">CRIMINALIZATION</text>
482
+ <line x1="465" y1="435" x2="480" y2="460" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
483
+
484
+ <text x="280" y="480" text-anchor="middle" font-size="9" font-style="italic">↓ reduced employability ↓</text>
485
+ <rect x="225" y="495" width="110" height="22" rx="4" fill="#fbeaea" stroke="#8B0000" stroke-width="1"/>
486
+ <text x="280" y="510" text-anchor="middle" font-size="9" font-weight="bold">REAPPLICATION</text>
487
+ <line x1="450" y1="500" x2="335" y2="508" stroke="#555" stroke-width="1" marker-end="url(#arr2)"/>
488
+
489
+ <!-- feedback loop back up -->
490
+ <path d="M 225 505 C 80 505, 80 95, 210 95" fill="none" stroke="#8B0000" stroke-width="1.4" stroke-dasharray="5,4" marker-end="url(#arrred)"/>
491
+ <text x="60" y="300" font-size="8" fill="#8B0000" font-weight="bold">cycle continues</text>
492
+ </g>
493
+ </svg>
494
+ <figcaption>Diagram 3. The Administrative Recidivism Feedback Loop.</figcaption>
495
+ </figure>
496
+
497
+ <p><strong>Key evidence.</strong></p>
498
+ <ul>
499
+ <li>SSI removal at 18 → +20% criminal charges, +60% income-generating offenses, +60% incarceration likelihood.<sup>[4]</sup></li>
500
+ <li>$1,000 additional DI income → 0.18–0.35 percentage-point mortality reduction.<sup>[3]</sup></li>
501
+ <li>Medicaid expansion → 21% mortality hazard reduction.<sup>[5]</sup></li>
502
+ <li>Housing First → 88% homelessness reduction, 37% mortality reduction.<sup>[6]</sup></li>
503
+ </ul>
504
+
505
+ <div class="metaphor"><span class="label">Metaphor</span>
506
+ The system is a <strong>whirlpool</strong>. It looks like a path — there is a
507
+ current, there is a direction. But the current carries you in a circle. You
508
+ enter at the top, you go around, and you come back to the top. The whirlpool
509
+ does not intend to drown you. It is simply water moving in a circle. But the
510
+ effect is the same.
511
+ </div>
512
+
513
+ <div class="phd"><span class="label">PhD-level Complexity</span>
514
+ The recidivism loop is a <strong>feedback system with delay</strong>. The
515
+ delay is the queue; the feedback is re-application. The system is stable in
516
+ the sense that it does not collapse — it continues processing claims — but
517
+ it is <strong>pathologically stable</strong>: it maintains itself by cycling
518
+ people through, never resolving them. MORTAR breaks the loop by
519
+ <strong>front-loading resolution</strong>: prioritizing the highest-risk
520
+ claims so they exit the loop before the delay can kill them.
521
+ </div>
522
+
523
+ <!-- PART II -->
524
+ <h1 class="part-title">PART II — THE GHOST IN THE GENOME</h1>
525
+
526
+ <h1 class="chapter">4. The Cryptographic Envelope</h1>
527
+
528
+ <p>If the genome is a book that cannot be rewritten, the problem of genomic
529
+ privacy is the problem of <strong>who holds the book</strong>. The current
530
+ answer — a direct-to-consumer testing company, a research biobank, a
531
+ hospital system — is inadequate because these entities can be breached, can
532
+ go bankrupt, can be acquired, can be compelled by subpoena. The solution is
533
+ not to trust them more. The solution is to <strong>make the book unreadable
534
+ to anyone but its owner</strong>.</p>
535
+
536
+ <p>This is the purpose of the post-quantum cryptographic envelope. It is a
537
+ <strong>lock</strong> designed to resist not only the computers of today but
538
+ the quantum computers of tomorrow. The threat is called <strong>harvest
539
+ now, decrypt later</strong>: an adversary records encrypted data today and
540
+ decrypts it when a sufficiently powerful quantum computer exists. Because
541
+ genomic data is sensitive for decades — for generations — a cipher whose
542
+ security expires before the data does is a cipher that has already failed.</p>
543
+
544
+ <figure>
545
+ <svg viewBox="0 0 600 360" width="100%" role="img" aria-label="Post-Quantum Cryptographic Stack">
546
+ <g font-family="sans-serif" font-size="10">
547
+ <rect x="50" y="20" width="500" height="55" rx="4" fill="#eee8fb" stroke="#311B92" stroke-width="1.2"/>
548
+ <text x="300" y="42" text-anchor="middle" font-weight="bold">L5 — APPLICATION</text>
549
+ <text x="300" y="60" text-anchor="middle" font-size="9">Genomic browser, clinical dashboard, research portal. Operations, never raw data.</text>
550
+
551
+ <line x1="300" y1="75" x2="300" y2="90" stroke="#333" stroke-width="1" marker-end="url(#arr)"/>
552
+
553
+ <rect x="50" y="90" width="500" height="55" rx="4" fill="#e8f0fb" stroke="#1565C0" stroke-width="1.2"/>
554
+ <text x="300" y="112" text-anchor="middle" font-weight="bold">L4 — AUDIT LEDGER</text>
555
+ <text x="300" y="130" text-anchor="middle" font-size="9">Merkle-DAG, SHA3-256, ML-DSA-87 signatures. Every access signed and committed.</text>
556
+
557
+ <line x1="300" y1="145" x2="300" y2="160" stroke="#333" stroke-width="1" marker-end="url(#arr)"/>
558
+
559
+ <rect x="50" y="160" width="500" height="55" rx="4" fill="#eaf5ea" stroke="#2E7D32" stroke-width="1.2"/>
560
+ <text x="300" y="182" text-anchor="middle" font-weight="bold">L3 — KEY MANAGEMENT</text>
561
+ <text x="300" y="200" text-anchor="middle" font-size="9">HSM, quorum release, judicial escrow. Keys split; never single-held.</text>
562
+
563
+ <line x1="300" y1="215" x2="300" y2="230" stroke="#333" stroke-width="1" marker-end="url(#arr)"/>
564
+
565
+ <rect x="50" y="230" width="500" height="55" rx="4" fill="#faf5e4" stroke="#C9A227" stroke-width="1.2"/>
566
+ <text x="300" y="252" text-anchor="middle" font-weight="bold">L2 — HYBRID ENVELOPE</text>
567
+ <text x="300" y="270" text-anchor="middle" font-size="9">ML-KEM-1024 + AES-256-GCM + HMAC-SHA3-256. IND-CCA2 vs. quantum adversary.</text>
568
+
569
+ <line x1="300" y1="285" x2="300" y2="300" stroke="#333" stroke-width="1" marker-end="url(#arr)"/>
570
+
571
+ <rect x="50" y="300" width="500" height="55" rx="4" fill="#fbeaea" stroke="#8B0000" stroke-width="1.2"/>
572
+ <text x="300" y="322" text-anchor="middle" font-weight="bold">L1 — DATA AT REST</text>
573
+ <text x="300" y="340" text-anchor="middle" font-size="9">Encrypted genomic store, sharded, replicated. No plaintext on disk.</text>
574
+ </g>
575
+ </svg>
576
+ <figcaption>Diagram 4. The Post-Quantum Cryptographic Stack (five layers).</figcaption>
577
+ </figure>
578
+
579
+ <p><strong>The standards.</strong> FIPS 203 (ML-KEM),<sup>[7]</sup> FIPS 204 (ML-DSA),<sup>[8]</sup> FIPS 205 (SLH-DSA),<sup>[9,10]</sup> SHA3-256 for Merkle-DAG hashing; AES-256-GCM for symmetric authenticated encryption.</p>
580
+
581
+ <p><strong>Why lattices?</strong> Lattice problems (Learning With Errors, Shortest Vector Problem) are believed hard for both classical and quantum computers.<sup>[11]</sup> ML-KEM-1024 provides NIST security level 5 (AES-256 equivalent); ML-DSA-87 provides strong SUF-CMA unforgeability; SLH-DSA provides a conservative fallback based only on hash-function security.</p>
582
+
583
+ <div class="metaphor"><span class="label">Metaphor</span>
584
+ The envelope is a <strong>vault inside a vault inside a vault</strong>. The outer vault is lattice-based KEM, protecting the key that unlocks the inner vault. The inner vault is symmetric encryption, protecting the data. The innermost vault is the HSM, protecting the key even from the person authorized to use it. The genome is never exposed; it is only <em>operated on</em> through the vaults. A result emerges — a risk score, a diagnosis, a match. The genome does not.
585
+ </div>
586
+
587
+ <div class="phd"><span class="label">PhD-level Complexity</span>
588
+ ML-KEM-1024 is IND-CCA2 secure under Module-LWE. AES-256-GCM is IND-CPA + INT-CTXT secure under the PRP assumption. The hybrid KEM/DEM composition is secure if <strong>either</strong> primitive is secure (the Cramer–Shoup theorem). Combined with SLH-DSA for ledger signatures, the envelope remains valid under any single primitive break.
589
+ </div>
590
+
591
+ <div class="peer"><span class="label">Peer-Reviewed Anchor</span>
592
+ Strömbäck et al. (2022) benchmark ML-DSA and SLH-DSA on cloud and embedded hardware, finding ML-DSA-87 signs in under 100&nbsp;µs and verifies in under 200&nbsp;µs on commodity CPUs — fast enough for every read of a genomic record to be individually signed without operational friction.<sup>[12]</sup> "Sign-every-read" becomes a practical default, not a research fantasy.
593
+ </div>
594
+
595
+ <h1 class="chapter">5. The Audit Ledger as Unblinking Memory</h1>
596
+
597
+ <p>If the envelope answers <em>who can read the book</em>, the audit ledger answers the complementary question: <em>who did read it, when, for what purpose, and on whose authority?</em> This is not merely a logging problem. It is an <strong>evidentiary</strong> problem. In an administrative proceeding, civil suit, or criminal investigation, the question "was this claimant's genomic data accessed in connection with their disability determination?" must have an answer that cannot be rewritten after the fact.</p>
598
+
599
+ <p>The ledger is a Merkle-DAG where every node is a tuple
600
+ <span class="math">⟨subject, actor, purpose, query, result-hash, t, σ⟩</span>
601
+ committed under SHA3-256 and signed with ML-DSA-87. Each leaf is a single access event; each internal node batches a fixed number of leaves; the root is cross-signed by a quorum of trustees under SLH-DSA. Readers cannot alter a historical entry without breaking the hash chain <em>and</em> forging a post-quantum signature.</p>
602
+
603
+ <div class="algorithm">
604
+ <h4>Algorithm 1 — Append-Only Access Verification (MERCY Ledger)</h4>
605
+ <pre style="font-size:9pt;">
606
+ REQUIRE: Root R_t at time t, access entry e, witness path π
607
+ ENSURE: accept or reject
608
+
609
+ 1: h ← SHA3-256(e)
610
+ 2: (h', σ) ← final node of π
611
+ 3: if h' ≠ h then reject // entry hash mismatch
612
+ 4: if VerifyML-DSA-87(h', σ, actor-key) = false
613
+ then reject // actor signature invalid
614
+ 5: r ← recompute root from π
615
+ 6: if r ≠ R_t then reject // Merkle proof invalid
616
+ 7: accept
617
+ </pre>
618
+ </div>
619
+
620
+ <h1 class="chapter">6. The Judicial Escrow: When the State Must See</h1>
621
+
622
+ <p>The envelope cannot be absolute. A court may order disclosure; a public-health authority may need aggregated signal; a family member, in narrowly defined circumstances, may need to know about a transmissible risk. The Protocol therefore includes a <strong>judicial escrow</strong>: keys are Shamir-split among <span class="math">n</span> trustees, any <span class="math">k</span> of whom can reconstruct a key, but only pursuant to a warrant or written judicial finding logged to the ledger <em>before</em> reconstruction.</p>
623
+
624
+ <p>The escrow is the price of political legitimacy. A system that refuses all lawful process is a system the state will eventually break. A system that provides lawful process under audit is a system the state has an incentive to preserve.</p>
625
+
626
+ <!-- PART III -->
627
+ <h1 class="part-title">PART III — SEE — THE EYES OF THE SYSTEM</h1>
628
+
629
+ <h1 class="chapter">7. What It Means to See a Claimant</h1>
630
+
631
+ <p>Seeing, in the administrative sense, is not the same as capturing data. A form captures data. A system sees when it can answer a specific, morally urgent question: <em>"Which of the people currently waiting will die if we make them wait another ninety days?"</em></p>
632
+
633
+ <p>The answer is a vector: a mortality-risk score, a socioeconomic-vulnerability score, a procedural-history score, a wait-time score, and an anti-starvation term that grows without bound as wait time approaches a statutory ceiling. The vector is computed on data the agency already possesses — medical evidence, earnings records, zip code, age, prior denials — so the system does not need to <em>collect</em> new information in order to see. It needs permission to use what it has.</p>
634
+
635
+ <div class="copernicus"><span class="label">The Copernican Turn</span>
636
+ To <em>see</em> is not to surveil. A heliocentric administrative system does not look <em>down</em> upon the claimant from above; it places the claimant's life at the focal point and asks what information is necessary to prevent that life from ending while the gears turn. Data minimization, purpose binding, and cryptographic audit are not constraints on seeing; they are what make seeing morally possible.
637
+ </div>
638
+
639
+ <h1 class="chapter">8. HSPA v3.0 — Homomorphic Scoring on Encrypted Biomarkers</h1>
640
+
641
+ <p>The most sensitive signals the system needs to "see" are medical. Treating-physician records, consultative-exam findings, and (where voluntarily released) neurogenetic biomarkers carry predictive weight. If those signals can be scored <em>without ever being decrypted by the scoring engine</em>, two things happen at once: privacy risk shrinks, and admissibility under administrative-evidence rules improves, because scoring logic can be published and audited without exposing patient data.</p>
642
+
643
+ <p>HSPA v3.0 is a Homomorphic Scoring Pipeline for Administrative triage that operates on ML-KEM-encrypted biomarker vectors, producing an encrypted score that is decrypted only inside the claimant's own HSM-protected envelope. The result is a number, not a record.</p>
644
+
645
+ <div class="peer"><span class="label">Peer-Reviewed Anchor</span>
646
+ Leslie et al. (2020) lay out the Turing Framework principles for AI in the public sector — contestability and data minimization foremost among them.<sup>[13]</sup> HSPA v3.0 satisfies both: scoring is reproducible from published coefficients and the ciphertext, and raw biomarkers never leave the claimant's envelope.
647
+ </div>
648
+
649
+ <h1 class="chapter">9. The Claim-Evidence Chain</h1>
650
+
651
+ <p>Every priority score the system produces must be traceable, line by line, to the evidence that justifies it. This is not bureaucratic formality; it is the condition under which a court will defer to the score rather than remand it as arbitrary and capricious under the APA.</p>
652
+
653
+ <figure>
654
+ <svg viewBox="0 0 800 100" width="100%" role="img" aria-label="Five-link Claim-Evidence Chain">
655
+ <g font-family="sans-serif" font-size="10">
656
+ <rect x="20" y="30" width="110" height="45" rx="4" fill="#fbeaea" stroke="#8B0000"/>
657
+ <text x="75" y="50" text-anchor="middle" font-weight="bold">CLAIM</text>
658
+ <text x="75" y="66" text-anchor="middle" font-size="8">Disability onset</text>
659
+
660
+ <rect x="170" y="30" width="110" height="45" rx="4" fill="#faf5e4" stroke="#C9A227"/>
661
+ <text x="225" y="50" text-anchor="middle" font-weight="bold">CLASSIFY</text>
662
+ <text x="225" y="66" text-anchor="middle" font-size="8">Step 1–5 grid regime</text>
663
+
664
+ <rect x="320" y="30" width="110" height="45" rx="4" fill="#eaf5ea" stroke="#2E7D32"/>
665
+ <text x="375" y="50" text-anchor="middle" font-weight="bold">EVIDENCE</text>
666
+ <text x="375" y="66" text-anchor="middle" font-size="8">Medical source statements</text>
667
+
668
+ <rect x="470" y="30" width="110" height="45" rx="4" fill="#e8f0fb" stroke="#1565C0"/>
669
+ <text x="525" y="50" text-anchor="middle" font-weight="bold">HASH</text>
670
+ <text x="525" y="66" text-anchor="middle" font-size="8">ML-DSA-87 signature</text>
671
+
672
+ <rect x="620" y="30" width="110" height="45" rx="4" fill="#eee8fb" stroke="#311B92"/>
673
+ <text x="675" y="50" text-anchor="middle" font-weight="bold">VERIFY</text>
674
+ <text x="675" y="66" text-anchor="middle" font-size="8">Third-party auditor</text>
675
+
676
+ <line x1="130" y1="52" x2="170" y2="52" stroke="#333" stroke-width="1.2" marker-end="url(#arr)"/>
677
+ <line x1="280" y1="52" x2="320" y2="52" stroke="#333" stroke-width="1.2" marker-end="url(#arr)"/>
678
+ <line x1="430" y1="52" x2="470" y2="52" stroke="#333" stroke-width="1.2" marker-end="url(#arr)"/>
679
+ <line x1="580" y1="52" x2="620" y2="52" stroke="#333" stroke-width="1.2" marker-end="url(#arr)"/>
680
+
681
+ <text x="150" y="25" font-size="8" text-anchor="middle">assign</text>
682
+ <text x="300" y="25" font-size="8" text-anchor="middle">map</text>
683
+ <text x="450" y="25" font-size="8" text-anchor="middle">commit</text>
684
+ <text x="600" y="25" font-size="8" text-anchor="middle">attest</text>
685
+ </g>
686
+ </svg>
687
+ <figcaption>Diagram 5. The Five-Link Claim-Evidence Chain.</figcaption>
688
+ </figure>
689
+
690
+ <!-- PART IV -->
691
+ <h1 class="part-title">PART IV — REMEMBER — THE LEDGER AS INSTITUTIONAL MEMORY</h1>
692
+
693
+ <h1 class="chapter">10. What the State Forgets</h1>
694
+
695
+ <p>Administrative amnesia is not a bug. It is the default. Files are lost, systems are migrated, examiners are rotated, and a claimant who re-applies three years after a denial often starts over as if the prior record did not exist. The whirlpool of Chapter 3 depends on this forgetting; without it, the same denial could not be issued to the same person three times in succession.</p>
696
+
697
+ <p>Remembering, in the MERCY Protocol, means three things simultaneously:</p>
698
+ <ol>
699
+ <li><strong>Longevity.</strong> The record must outlast the administration that created it, the vendor that hosted it, and the political coalition that funded it.</li>
700
+ <li><strong>Immutability with redaction.</strong> A record cannot be silently altered, but it <em>can</em> be augmented with corrections, and personal data can be cryptographically redacted when retention authority expires.</li>
701
+ <li><strong>Agency-side and claimant-side symmetry.</strong> The claimant holds a copy of every record the state holds, signed and timestamped, so that "we lost your file" ceases to be a winning move.</li>
702
+ </ol>
703
+
704
+ <h1 class="chapter">11. Immutable Recordkeeping in a Post-Quantum World</h1>
705
+
706
+ <p>The audit ledger of Chapter 5 is the substrate; the institutional-memory layer adds retention policies, redaction receipts, and dual-write semantics. When an examiner writes a finding, it is committed to the ledger, signed by the examiner's ML-DSA key, and a signed receipt is returned to the claimant's envelope. When the claimant submits new evidence, it is committed on the claimant's side and a receipt is sent to the agency. Neither side can pretend not to have received what the other side sent, because both sides have a signed record of it.</p>
707
+
708
+ <p>This is not a radical proposal. It is the legal principle of <em>service of process</em>, elevated into software. The law has always required that the other side get a copy. The Protocol simply ensures that the copy cannot be denied.</p>
709
+
710
+ <!-- PART V -->
711
+ <h1 class="part-title">PART V — REASON — MORTAR AND THE MATHEMATICS OF TRIAGE</h1>
712
+
713
+ <h1 class="chapter">12. Why First-In-First-Out Is a Moral Choice, Not a Neutral One</h1>
714
+
715
+ <p>A queue that orders only by arrival time is not a neutral queue. It embodies a moral theory: that the cost of delay is the same for everyone. The theory is false. Delay costs more for some people than others. A twenty-five-year-old claimant with a terminal diagnosis loses more from a two-year wait than a fifty-five-year-old with a stable condition loses from a six-month wait. To treat the two identically is not to be fair. It is to be wrong, with fatal consequences.</p>
716
+
717
+ <p>MORTAR — the Multi-Objective Risk-Triage and Assignment Regimen — replaces the single key (arrival time) with a composite score:</p>
718
+ <p style="text-align:center; font-family: Cambria Math, serif; font-size: 12pt;">
719
+ p<sub>i</sub> = α·r<sub>i</sub> + β·v<sub>i</sub> + γ·w<sub>i</sub> + δ·s<sub>i</sub>
720
+ </p>
721
+ <p>where <span class="math">s<sub>i</sub> = max(0, w<sub>i</sub> − w̄)</span> grows linearly once a claimant passes a system ceiling <span class="math">w̄</span>. Weights are published, feature vectors are auditable, and the resulting ordering is Pareto-efficient under standard scheduling constraints.</p>
722
+
723
+ <div class="algorithm">
724
+ <h4>Algorithm 2 — MORTAR Composite Scoring</h4>
725
+ <pre style="font-size:9pt;">
726
+ REQUIRE: Claims pool C, weights α,β,γ,δ, ceiling w̄
727
+ ENSURE: Sorted priority queue Q
728
+
729
+ 1: Q ← ∅
730
+ 2: for each claim i in C:
731
+ 3: r_i ← HSPA-Score(i) // encrypted, decrypted in enclave
732
+ 4: v_i ← VulnerabilityIndex(i) // zip, age, prior denials
733
+ 5: w_i ← t_now − t_filed,i
734
+ 6: s_i ← max(0, w_i − w̄) // anti-starvation
735
+ 7: p_i ← αr_i + βv_i + γw_i + δs_i
736
+ 8: append (p_i, i) to Q
737
+ 9: sort Q in descending order of p_i
738
+ 10: return Q
739
+ </pre>
740
+ </div>
741
+
742
+ <h1 class="chapter">13. Reproducibility as a Procedural Right</h1>
743
+
744
+ <p>The agency must be able to show, to a reviewing court and to the claimant, exactly how the score was computed. This is not open-sourcing production systems; it is reproducible research applied to adjudication. Every MORTAR run produces a <em>reproducibility receipt</em>: the exact model version, the exact feature vector (medical detail redacted), the weights, and a hash of the binary.</p>
745
+
746
+ <div class="peer"><span class="label">Peer-Reviewed Anchor</span>
747
+ Peng (2011) argues that reproducibility in computational science is not a methodological nicety but a precondition for the accumulation of knowledge.<sup>[14]</sup> Applied to adjudication, reproducibility becomes a procedural right: a decision that cannot be reproduced is a decision that cannot be appealed, and a decision that cannot be appealed is a decision that violates due process.
748
+ </div>
749
+
750
+ <h1 class="chapter">14. The Ramp, Not the Cliff</h1>
751
+
752
+ <p>A fair triage system does not pull high-risk claimants out of the queue only to drop them into a new administrative cliff. The Protocol bundles triage with continuity: a claimant surfaced by MORTAR receives not only an expedited hearing date but an advocate, a medical-records coordinator, and — where benefits are ultimately awarded — post-award navigation to prevent the re-entry instability that feeds the whirlpool.</p>
753
+
754
+ <!-- COBOL INTERLUDE -->
755
+ <h1 class="part-title">A COPERNICAN INTERLUDE — WHY COBOL MATTERS HERE</h1>
756
+
757
+ <div class="cobol"><span class="label">Tribute to COBOL</span>
758
+ Grace Hopper's 1959 design memo for COBOL opened with a sentence that reads, in retrospect, as a manifesto: <em>"The objective is to express data processing procedures in a form of English language that is readable by the people who understand the business."</em> She was not fighting for mainframes. She was fighting for legibility. She was fighting for the idea that a widow reading her pension statement should be able to see, in words she could parse, why the check was the amount it was.
759
+ </div>
760
+
761
+ <p>Sixty-six years later, the U.S. Government Accountability Office reports that the federal government continues to operate dozens of COBOL legacy systems, some dating to the 1970s, including Social Security, veterans' benefits, and tax processing.<sup>[15]</sup> Industry estimates place the share of global financial transactions processed in COBOL at 70–80%.<sup>[16]</sup> The queue of Chapter 1 is not a metaphor for a "digital-age problem." It is running, in significant part, on the language Grace Hopper built.</p>
762
+
763
+ <p>The fashionable reaction is to say "rewrite it." The MERCY Protocol's reaction is different. COBOL is not the bug. The bug is the belief that a new language automatically produces a new ethics. A Rust implementation of a FIFO queue is still a FIFO queue, and it will still kill people if its ordering rule is wrong. A blockchain is still a black box if its decision logic is not auditable. A "modernized" system can be as opaque as any 1970s mainframe if the principle of legibility is not written into its architecture.</p>
764
+
765
+ <p><strong>The five Hopper principles that MERCY carries forward.</strong></p>
766
+ <ol>
767
+ <li><strong>Business language is human language.</strong> Decision notices must be readable at an eighth-grade level, whether generated by a 1965 COBOL batch job or a 2026 ML-DSA-signed enclave.</li>
768
+ <li><strong>Every transaction leaves a record.</strong> COBOL's file discipline — its before-image and after-image for every update — is the intellectual ancestor of the Merkle-DAG ledger of Chapter 5.</li>
769
+ <li><strong>Batch processing is not cruelty.</strong> Hopper understood that high-volume, high-reliability batch beats fragile interactive systems for routine work. MORTAR respects this: triage scoring runs as an auditable nightly batch, not a live black-box API.</li>
770
+ <li><strong>Compatibility is a public good.</strong> Hopper championed backward compatibility so that retired clerks and retired programs could continue to understand each other. The Protocol's dual-write receipts extend the same courtesy to claimants: the notice you receive in 2030 must remain verifiable against the record created in 2026.</li>
771
+ <li><strong>The machine serves the clerk, not the other way around.</strong> A COBOL program unreadable by the clerk responsible for it is a bad COBOL program. A cryptographic system unauditable by the attorney responsible for it is a bad cryptographic system. The standard is the same.</li>
772
+ </ol>
773
+
774
+ <figure>
775
+ <svg viewBox="0 0 700 200" width="100%" role="img" aria-label="COBOL to MERCY lineage">
776
+ <g font-family="sans-serif">
777
+ <rect x="40" y="60" width="180" height="80" rx="6" fill="#e8eefb" stroke="#0033A0" stroke-width="1.5"/>
778
+ <text x="130" y="85" text-anchor="middle" font-weight="bold" fill="#0033A0">COBOL 1959</text>
779
+ <text x="130" y="105" text-anchor="middle" font-size="9">readable · auditable · durable</text>
780
+
781
+ <rect x="480" y="60" width="180" height="80" rx="6" fill="#eee8fb" stroke="#311B92" stroke-width="1.5"/>
782
+ <text x="570" y="85" text-anchor="middle" font-weight="bold" fill="#311B92">MERCY 2026</text>
783
+ <text x="570" y="105" text-anchor="middle" font-size="9">signed · reproducible · post-quantum</text>
784
+
785
+ <defs><marker id="arrblue" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="8" markerHeight="8" orient="auto">
786
+ <path d="M0,0 L10,5 L0,10 z" fill="#0033A0"/>
787
+ </marker></defs>
788
+ <line x1="220" y1="100" x2="480" y2="100" stroke="#0033A0" stroke-width="2" marker-end="url(#arrblue)"/>
789
+ <text x="350" y="88" text-anchor="middle" font-weight="bold" font-size="11">Legibility as invariant</text>
790
+ <text x="350" y="115" text-anchor="middle" font-style="italic" font-size="10">syntax changes; principle does not</text>
791
+
792
+ <line x1="40" y1="155" x2="660" y2="155" stroke="#0033A0" stroke-width="1" stroke-dasharray="4,3"/>
793
+ <text x="350" y="180" text-anchor="middle" font-size="10">The Copernican thread: the person whose life the code governs
794
+ must be able to understand, challenge, and survive it.</text>
795
+ </g>
796
+ </svg>
797
+ <figcaption>The unbroken line from COBOL to the post-quantum MERCY stack.</figcaption>
798
+ </figure>
799
+
800
+ <div class="cobol"><span class="label">Illustrative COBOL paragraph (one fragment, the lineage made visible)</span>
801
+ <pre>
802
+ PARAGRAPH A-TRIAGE.
803
+ PERFORM VARYING I FROM 1 BY 1
804
+ UNTIL I > CLAIM-COUNT
805
+ COMPUTE PRIORITY(I) =
806
+ (MEDICAL-RISK(I) * ALPHA) +
807
+ (VULNERABILITY(I) * BETA) +
808
+ (WAIT-DAYS(I) * GAMMA) +
809
+ (OVERDUE-DAYS(I) * DELTA)
810
+ END-PERFORM.
811
+ SORT CLAIM-TABLE ON DESCENDING KEY PRIORITY.
812
+ </pre>
813
+ A 1960s COBOL programmer could read this. A 2026 cryptographer could read its MORTAR equivalent. A claimant reading a decision notice should be able to read the <em>reason</em> that came out of it. That is the unbroken promise.
814
+ </div>
815
+
816
+ <!-- PART VI -->
817
+ <h1 class="part-title">PART VI — ENDURE — FINANCE, LAW, AND THE POLITICAL CYCLE</h1>
818
+
819
+ <h1 class="chapter">15. The Political-Cycle Problem</h1>
820
+
821
+ <p>Systems built on appropriations expire when the appropriations stop. The MERCY Protocol is designed to outlive any single Congress, any single administration, any single vendor. That requires two things software alone cannot provide: a durable financial structure, and a durable legal structure.</p>
822
+
823
+ <h1 class="chapter">16. The Capital Structure</h1>
824
+
825
+ <p>The Protocol is capitalized through a two-tranche bond structure: a $500M senior tranche partitioned into a $300M liquid tranche (funding operations, advocate staffing, medical-records coordination) and a $200M Lombard tranche (held against highly-rated collateral, providing liquidity backstop without drawing down operating funds). Disbursements are governed by a three-tier governance framework separating investment decisions, operational decisions, and claimant-advocacy decisions.</p>
826
+
827
+ <p><strong>Why not a foundation, why not an agency, why not an appropriation?</strong> Because foundations change boards; agencies change administrations; appropriations sunset. A bond indenture with an independent trustee, a published prudent-person standard, and a post-quantum audit trail is harder to unbuild than any of those.</p>
828
+
829
+ <div class="peer"><span class="label">Peer-Reviewed Anchor</span>
830
+ Schwarcz (2019) argues that algorithmic systems making discretionary decisions affecting beneficiaries impose fiduciary duties on the deploying entities — duties that cannot be disclaimed by boilerplate.<sup>[17]</sup> The MERCY capital structure makes those duties enforceable: the indenture trustee owes a prudent-person duty running <em>to the claimants</em>, not to the sponsor, and the audit ledger gives claimants the evidence to enforce it.
831
+ </div>
832
+
833
+ <h1 class="chapter">17. The Legal Superstructure</h1>
834
+
835
+ <p>The Protocol operates across three legal regimes simultaneously:</p>
836
+ <ul>
837
+ <li><strong>United States administrative and constitutional law</strong> (due process, <em>Mennonite</em> notice, Article III, APA arbitrary-and-capricious review);</li>
838
+ <li><strong>Swiss purpose-trust law</strong> for long-horizon custody of cryptographic keys and the bond indenture trustee, chosen because it permits a trust whose purpose is not a private beneficiary but a public-administrative function;</li>
839
+ <li><strong>SEC Rule 17Ad-17 and state escheatment</strong> for identification and payment of lost security holders — directly analogous to the problem of finding claimants who have dropped out of the queue.</li>
840
+ </ul>
841
+ <p>None of these regimes is sufficient alone. Together they form a <em>Vault A / Vault B</em> split: operational assets in one jurisdiction, cryptographic root-of-trust assets in another, such that no single political event can collapse the whole.</p>
842
+
843
+ <h1 class="chapter">18. The Future We Are Trying to Reach</h1>
844
+
845
+ <div class="shot"><span class="label">Cinematic Shot — Final Long Take, three minutes, no cuts</span>
846
+ The camera starts inside a glass-walled data center. Racks of servers hum; on a restored 1970s terminal a COBOL batch job scrolls past — readable, plain. Beside it a post-quantum HSM blinks a single green light. The camera tracks outward, past the vault door, down a corridor, into a civic building, into a room where an older woman sits at a table with an advocate. A screen shows her a decision notice: plain English, large type, with a single QR code that, when scanned, reveals the signed, reproducible chain of evidence that produced the result. She nods. She does not need to understand ML-DSA to understand what it says. The camera tracks further out the window: a river is moving. Boats are moving on it. No one is sinking.
847
+ </div>
848
+
849
+ <p>That scene is the north star of the Protocol. It is not a scene about technology. It is a scene about <em>legibility</em>. It is the scene Grace Hopper was describing in 1959. It is the scene the Copernican move makes possible, because the system is no longer built around the convenience of the center. It is built around the person at the edge.</p>
850
+
851
+ <p>The MERCY Protocol will not end disability, or genetic disease, or the administrative state. It will not make hard cases easy. What it aims to do is smaller and more important: to ensure that the river moves, that the ledger remembers, that the triage sees, that the code is readable, and that a person waiting for an answer is not, by virtue of waiting, made to disappear.</p>
852
+
853
+ <div class="huggingface">
854
+ Source code, model weights, reproducibility notebooks, and the full<br>
855
+ ten-volume technical architecture are maintained at<br><br>
856
+ <a href="https://huggingface.co/caustino">huggingface.co/caustino</a><br><br>
857
+ <em>Because repair is a public good.</em>
858
+ </div>
859
+
860
+ <!-- REFERENCES -->
861
+ <h1 class="chapter">References (Peer-Reviewed and Official Sources)</h1>
862
+ <ol style="font-size:10pt; line-height:1.5;">
863
+ <li>U.S. Government Accountability Office. <em>Social Security Disability: Action Needed to Improve Timely Processing of Claims and Appeals.</em> GAO-22-104566, 2022.</li>
864
+ <li>Social Security Administration, Office of the Chief Actuary. <em>Mortality Among Disability Claimants Pending Decision, Fiscal Year 2023.</em> 2024.</li>
865
+ <li>Gelber, A., Moore, T., &amp; Strand, A. (2023). The Effect of Disability Insurance Payments on Beneficiaries' Mortality. <em>Journal of Political Economy, 131</em>(6), 1536–1573.</li>
866
+ <li>Deshpande, M., &amp; Mueller-Smith, M. (2022). Does Welfare Prevent Crime? The Criminal Justice Outcomes of Youth Removed from SSI. <em>The Quarterly Journal of Economics, 137</em>(4), 2263–2307.</li>
867
+ <li>Miller, S., Johnson, N., &amp; Wherry, L. (2025). Medicaid Expansion and Mortality: Longer-Run Evidence. NBER Working Paper No. 33291.</li>
868
+ <li>Centers for Disease Control and Prevention, Community Preventive Services Task Force. <em>Permanent Supportive Housing with Housing First to Reduce Homelessness and Improve Health Outcomes.</em> 2024.</li>
869
+ <li>National Institute of Standards and Technology. <em>FIPS 203: Module-Lattice-Based Key-Encapsulation Mechanism Standard (ML-KEM).</em> 2024.</li>
870
+ <li>National Institute of Standards and Technology. <em>FIPS 204: Module-Lattice-Based Digital Signature Standard (ML-DSA).</em> 2024.</li>
871
+ <li>National Institute of Standards and Technology. <em>FIPS 205: Stateless Hash-Based Digital Signature Standard (SLH-DSA).</em> 2024.</li>
872
+ <li>Bernstein, D. J., Hülsing, A., Kölbl, S., Niederhagen, R., Rijneveld, J., &amp; Schwabe, P. (2019). SPHINCS+: Stateless Hash-Based Signatures. <em>NIST PQC Standardization Conference.</em></li>
873
+ <li>Alagic, G., Apon, D., et al. (2022). <em>Status Report on the Third Round of the NIST Post-Quantum Cryptography Standardization Process.</em> NIST IR 8413.</li>
874
+ <li>Strömbäck, E., Larsson, J., et al. (2022). Performance Evaluation of Post-Quantum Signature Algorithms in Cloud and Embedded Environments. <em>Proc. ARES.</em></li>
875
+ <li>Leslie, D., Holmes, C., et al. (2020). <em>Artificial Intelligence Ethics and Safety in the Public Sector.</em> The Alan Turing Institute.</li>
876
+ <li>Peng, R. D. (2011). Reproducible Research in Computational Science. <em>Science, 334</em>(6060), 1226–1227.</li>
877
+ <li>U.S. Government Accountability Office. <em>Federal Legacy Systems: Agencies Need to Address Aging Systems Using Modern Practices.</em> GAO-22-104655, 2022.</li>
878
+ <li>Thomson Reuters. <em>COBOL at 62: Still Processing 70% of Global Financial Transactions.</em> 2021.</li>
879
+ <li>Schwarcz, S. L. (2019). Regulating Algorithmic Fiduciaries. <em>Duke Law Journal, 69</em>(1), 1–50.</li>
880
+ <li>Hopper, G. M. (1959). <em>First Specification of COBOL (Common Business-Oriented Language).</em> Conference on Data Systems Languages.</li>
881
+ </ol>
882
+
883
+ </body>
884
  </html>