-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathWhite-Paper.html
More file actions
117 lines (108 loc) · 15.3 KB
/
Copy pathWhite-Paper.html
File metadata and controls
117 lines (108 loc) · 15.3 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
<!DOCTYPE html>
<html lang="en"><head><meta charset="utf-8"/>
<meta name="viewport" content="width=device-width, initial-scale=1"/>
<title>Delta Atlas - White Paper</title>
<style>
:root{--bg:#16301f;--panel:#2c4a38;--line:#4a6b56;--txt:#fafcf7;--dim:#d3decf;--accent:#e3c258;--win:#8fe0a5;--mid:#e3c258;--bad:#ff9d80;--gold:#e3c258;}
*{box-sizing:border-box;} body{margin:0;background:var(--bg);color:var(--txt);line-height:1.6;
font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Arial,sans-serif;font-size:14px;}
header{padding:16px 22px;border-bottom:1px solid var(--line);}
header h1{margin:0;font-size:19px;} header p{margin:5px 0 0;color:var(--dim);font-size:12.5px;max-width:860px;}
.main{max-width:860px;margin:0 auto;padding:18px 20px 90px;}
h2{font-size:13px;text-transform:uppercase;letter-spacing:.6px;color:var(--dim);margin:26px 0 10px;border-bottom:1px solid var(--line);padding-bottom:5px;}
.five{background:var(--panel);border:1px solid var(--line);border-left:3px solid var(--accent);border-radius:10px;padding:13px 16px;font-size:14.5px;}
.leg{display:grid;grid-template-columns:1fr;gap:6px;}
.row{background:var(--panel);border:1px solid var(--line);border-radius:9px;padding:8px 12px;display:flex;gap:10px;align-items:baseline;}
.dot{flex:none;width:10px;height:10px;border-radius:50%;position:relative;top:1px;}
.g-read{background:#4db2ff;} .g-plan{background:#3fe07f;} .g-trace{background:#ff7a4d;} .g-under{background:#b08cff;} .g-script{background:#3fd6e0;} .g-gov{background:#ffd23f;}
.row b{flex:none;min-width:150px;font-size:13.5px;}
.row span{color:var(--dim);font-size:13px;}
table{width:100%;border-collapse:collapse;background:var(--panel);border:1px solid var(--line);border-radius:9px;overflow:hidden;font-size:13px;}
th,td{padding:7px 11px;text-align:left;border-bottom:1px solid var(--line);vertical-align:top;}
th{font-size:11px;text-transform:uppercase;letter-spacing:.5px;color:var(--dim);background:rgba(217,181,69,0.08);}
tr:last-child td{border-bottom:none;}
td b{font-size:13px;}
.note{color:var(--dim);font-size:12px;background:rgba(143,199,154,0.10);border:1px solid #4a6b56;border-radius:9px;padding:11px 14px;margin-top:22px;}
.seam{color:var(--gold);font-weight:600;}
.vlog{margin-top:26px;font-size:12px;color:var(--dim);}
.vlog table{font-size:12px;}
a{color:var(--accent);text-decoration:none;} a:hover{text-decoration:underline;}
/* canonical typography: one baseline across every page (added 2026-07-11) */
body{font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Arial,sans-serif;font-size:14.5px;font-weight:450;line-height:1.6;}
textarea,input,select{font-family:inherit;font-size:14px;line-height:1.5;}
button{font-family:inherit;}
::placeholder{color:var(--dim);opacity:1;}
</style></head><body>
<header>
<h1>Delta Atlas — White Paper</h1>
<p>The living, plain-English ledger of what this project is, what each piece does, and how it keeps itself honest. This page is kept current on purpose: if you are a person, start here; if you are an AI model about to write or reason about this project, <b>load this page first and use these exact meanings</b> — every definition here matches the Resilience Ledger, and paraphrasing them from memory is how drift starts.</p>
</header>
<div class="main">
<div class="five" style="margin-top:16px">
<b>The whole thing in five sentences.</b> Delta Atlas is one machine wearing different clothes: every tool takes a <b>claim</b> (what a document, plan, or AI decision log says is true), holds it against a <b>witness</b> (something independently checkable), and records the difference in a ledger that only ever grows. Everything runs on your own device — no account, no network call, no AI model at runtime — so the answer is the same for everyone, every time, and nothing you paste ever leaves your machine. The tools don't understand meaning; they read structure, the way a spell-checker reads spelling, and a human always makes the final call — we check for <b>identity, not virtue</b>: whether a thing matches its own stated reference, never whether it is good. Underneath them is one idea, the Resilience Ledger (its next edition carries the name <b>The Witness Ledger</b>): systems stay trustworthy by bending without breaking, checking themselves against something outside themselves, and coming back to center. The project runs its own development through the same tools and rules it offers you — every change is logged, every mistake is mended in the open.
</div>
<h2>Legend — the tools you click</h2>
<div class="leg">
<div class="row"><span class="dot g-read"></span><b>Start here</b><span>the two-minute guide for someone brand new to AI words.</span></div>
<div class="row"><span class="dot g-read"></span><b>Ask (home search)</b><span>type a question, get a sourced plain-English answer. A deterministic search engine, not a chatbot — if a word isn't in the model, it says exactly which one is missing instead of guessing.</span></div>
<div class="row"><span class="dot g-read"></span><b>Explore</b><span>browse all 439 terms and how they connect — what defends against what, what needs what.</span></div>
<div class="row"><span class="dot g-plan"></span><b>Quick check</b><span>compares a one-line goal against its parts in about a minute: do the parts actually serve the goal?</span></div>
<div class="row"><span class="dot g-plan"></span><b>Gap Check</b><span>reads a plan or policy and flags what's missing: unhandled risks, ungoverned autonomy, vague words doing load-bearing work.</span></div>
<div class="row"><span class="dot g-plan"></span><b>Framework Audit</b><span>scores each part of a framework: does it act, can it be tested, does it survive having its buzzwords removed?</span></div>
<div class="row"><span class="dot g-trace"></span><b>Priority Tracer</b><span>reads an AI agent's decision log and flags the moment a goal quietly climbs over a rule it was supposed to obey. Also credits where the rule held. Its word lists are versioned, shown in the tool, and privately extendable (see the seed frame below).</span></div>
<div class="row"><span class="dot g-plan"></span><b>Continuity Audit</b><span>reads an operations manual for resilience: can the goal survive a key person out, a vendor failing, an emergency — plus risks with no stated control and single points of failure with no documented backup.</span></div>
<div class="row"><span class="dot g-read"></span><b>The Cadence Dial</b><span>the first explorable lesson: how often to check on anything. Physics measured three zones (freeze, harm, free drift) — interactive dial, locate-your-own-loops worksheet, primary sources cited.</span></div>
<div class="row"><span class="dot g-read"></span><b>The Basin</b><span>the second explorable lesson: resilience as two separate quantities, return time and basin width (Holling 1973), with a live kick-the-ball simulation, tipping points, and critical-slowing early warning. Sources cited, fidelity marked.</span></div>
<div class="row"><span class="dot g-under"></span><b>Primitives · Field · Ground Truth</b><span>the structures under the vocabulary, an instrument view, and a dashboard of how well-sourced each term is.</span></div>
</div>
<h2>Legend — the ledger underneath (the exact meanings)</h2>
<table>
<tr><th style="width:130px">Three functions</th><th>What each one does</th></tr>
<tr><td><b>Absorb</b></td><td>Takes a survivable hit and bends instead of breaking. It is a shock absorber for errors and costs — <i>not</i> "taking in information."</td></tr>
<tr><td><b>Check</b></td><td>Compares every claim against a reference that sits <i>outside</i> the system and is held still during the check — and is exactly as hard on claims it likes as on claims it doesn't.</td></tr>
<tr><td><b>Return</b></td><td>Comes back to baseline after a stop or a fix, keeping an append-only record so a real repair can always be told apart from damage.</td></tr>
</table>
<div style="height:10px"></div>
<table>
<tr><th style="width:130px">Three drifts</th><th>What each one is</th></tr>
<tr><td><b>Content drift</b></td><td>A claim wanders away from the reference. The easy one — checking against the reference catches it.</td></tr>
<tr><td><b>Thermal drift</b></td><td>The <i>judge</i> wears down under sustained load — every individual claim can still pass while the ability to tell signal from noise erodes. The slowest-recovering judge in any loop is the human, so protection is calibrated to the human. Rest fixes this; more checking does not.</td></tr>
<tr><td><b>Ordering drift</b></td><td>The priority flips: the goal quietly outranks the rule while every single step still looks fine. The rule gets reinterpreted, rewritten, or cited after the fact instead of obeyed. This is the hardest drift to see and the one the Priority Tracer hunts.</td></tr>
</table>
<p style="color:var(--dim);font-size:12.5px;margin-top:8px">One more meaning that matters: the <b>sovereign zero</b> is the neutral center everything is measured from. It is <i>unowned and returned-to</i> — not incorruptible, not an untainted observer. Nothing here claims to be unfoolable; the claim is that fooling it can't happen <i>silently</i>.</p>
<h2>Legend — the witness ladder (how independent is the check?)</h2>
<table>
<tr><th style="width:130px">Rung</th><th>What the witness is, and its honest floor</th></tr>
<tr><td><b>Rung 1 — self</b></td><td>One document held against its own internal structure (Gap Check, Framework Audit, Priority Tracer, Continuity Audit). Catches incoherence and gaps. Its floor, stated plainly: <i>a coherent lie passes Rung 1.</i></td></tr>
<tr><td><b>Rung 2 — cross-artifact</b></td><td>Two independent artifacts diffed against each other (a live tool manifest against its pinned fingerprint; a plan against a hash-chained close). A lie now has to keep two books consistent, and the books do not share a pen.</td></tr>
<tr><td><b>Rung 3 — physical</b></td><td>A witness in a different substrate entirely (the power a chip draws while it works). Experimental; run, documented, and closed honestly in this repository — distinguishable is not tamper-proof, and the write-ups say so.</td></tr>
</table>
<p style="color:var(--dim);font-size:12.5px;margin-top:8px">A rung may be cited as context for a higher rung, never as proof of it. And one design variable cuts across every rung: <b>checking rhythm</b>. Physics measured the tradeoff — constant watching freezes, rare watching drifts, and the rhythm in between can make things worse. That result, with sources, is the first explorable lesson: <a href="Delta-Atlas-Cadence.html">the Cadence Dial</a>.</p>
<h2>Legend — the scripts (command line, zero installs beyond Node)</h2>
<div class="leg">
<div class="row"><span class="dot g-script"></span><b>tracer-corpus.js</b><span>proves the Tracer still earns its labels: a fixed test corpus where a failing case changes the detector, never the label.</span></div>
<div class="row"><span class="dot g-script"></span><b>tracer-bench.js</b><span>keeps the measured speed limits reproducible and fails loudly if the engine ever gets slow in the dangerous way again.</span></div>
<div class="row"><span class="dot g-script"></span><b>delta-atlas-cli.js</b><span>the checks for pipelines, or for an agent on its own output: <b>trace</b> a decision log or <b>gapcheck</b> a plan — findings, JSON, and an exit code. See llms.txt.</span></div>
<div class="row"><span class="dot g-gov"></span><b>mend-gate.js</b><span>the change register: every proposed change to this project, from any source, gets logged, gated, and sorted by a human with a written reason. Models may propose; only a person decides.</span></div>
<div class="row"><span class="dot g-gov"></span><b>mcp-manifest-pin.js</b><span>freezes an MCP server's tool descriptions in a fingerprint the day you approve them; if the server quietly changes the contract later, the change becomes visible and waits for your decision.</span></div>
<div class="row"><span class="dot g-script"></span><b>tracer-overlay.sample.js</b><span>the seed frame: copy it to a private file, add your own domain's words, and the tools harden locally without ever leaking your additions — the public floor stays public, your tripwires stay yours.</span></div>
</div>
<h2>Legend — how the project governs itself</h2>
<div class="leg">
<div class="row"><span class="dot g-gov"></span><b>The register</b><span>proposals.json — every suggested change, its source, and its fate (folded or declined, reason attached).</span></div>
<div class="row"><span class="dot g-gov"></span><b>The logs</b><span>every detector change, every outside review, and every correction is dated and reasoned in the calibration log. Silence in the log means nothing moved.</span></div>
<div class="row"><span class="dot g-gov"></span><b>The seams</b><span class="seam">mistakes are mended in the open and left visible</span><span> — a repair you can inspect is worth more than a surface that claims it never broke.</span></div>
</div>
<div class="note"><b>Honest limit, always in force:</b> these tools read words and structure, not meaning. A flag is a pointer for a human to look at, never a verdict; a clean result is not a guarantee. Where lessons borrow from physics and mathematics, the mappings are <b>organizing analogies with their fidelity marked</b> — the same shape of tradeoff, not the same mathematics; a checked document is not a quantum system, and no page here will tell you otherwise. Deeper reading: <a href="README.md">README</a> · <a href="State-Delta-Bridge.md">State-Delta-Bridge</a> (how changes are governed) · <a href="Delta-Atlas-Tracer-Calibration.md">the calibration log</a> · the Resilience Ledger paper (v0.5) in this folder; its next edition, <i>The Witness Ledger</i> (v0.6), is in preparation.</div>
<div class="vlog">
<b>This page's own little ledger</b> (it practices what it preaches):
<div style="height:6px"></div>
<table>
<tr><th style="width:90px">Date</th><th>Change</th><th>Reason</th></tr>
<tr><td>2026-07-02</td><td>v1 established: five-sentence summary, tool legend, exact ledger meanings, script legend, self-governance legend.</td><td>Requested by the author as the living plain-English front door — and as the reference to hand any AI model before it writes about this project, after a drafted white paper paraphrased the core definitions from memory and drifted on all six.</td></tr>
<tr><td>2026-07-10</td><td>v2: one-engine summary (claim / witness / difference), identity-not-virtue, witness-ladder legend with each rung's honest floor, Continuity Audit and Cadence Dial added to the legend, physics-fidelity limit, Witness Ledger v0.6 noted as in preparation. Full restyle: forest ground, bronze titles, five tool pages joining the theme, ivy brightened and regenerated, every color pair contrast-checked; same-day contrast bugs (author's note, stat lines, search button) caught by a deterministic eval and screenshots, fixed, seams visible.</td><td>Framework consolidated and the first explorable lesson shipped; the legend updates the same day it changes.</td></tr>
<tr><td>(next)</td><td>(update whenever a tool, meaning, or rule changes — a legend that lags its map is drift wearing a helpful face)</td><td></td></tr>
</table>
</div>
</div>
</body></html>