The Promises Ledger
Every commitment VEILOS has made about its own future, with the date it comes due and the thing that would decide it was kept. Derived live from the organism's own registry each time this page is read — never written by hand.
No promise is currently overdue. 7 are pending — recorded, not yet due, and deliberately not counted as anything earned.
10 recorded
2 kept
7 pending
0 overdue
1 undischargeable
| Status | Due | Promise |
|---|---|---|
| undischargeable | undated |
THE OUTWARD CLAIM CLASS — scope decision remains founder-owned and unstarted.
D-S256.7 · owner: founder
· nothing can currently decide this
|
| pending | S270 |
Recheck the owned gap in veil/crossing.mjs: the Phase-0-manifest-pinned crossing entry point; engine.crossVeil (its only implementation) is Node-lane-only, so no veil crossing is ever policy-evaluated or recorded at the edge. Whether to build an edge policy-evaluation twin (receipts, quarantine, telemetry with real traffic) is a product decision, not a refactor.
D-S260.5 · owner: founder
· kept when: entry removed from NODE_ONLY_MODULES, or recheckSession advanced with a decision
|
| pending | undated |
Record prose is written with the editor or via a file, never through shell interpolation — PowerShell reads the backtick as an escape introducer and eats the first character of every Markdown code span. D-S250.32 promised this in prose and it recurred ten sessions later.
D-S260.8 · owner: agent
· kept when: tests/s260-carrier-and-vocabulary.test.mjs control-character ratchet over the record surfaces
|
| pending | undated |
Every comment claiming parity with a named module or symbol must actually READ that counterparty; the population that does not is debt and may only ever shrink.
D-S250.59 · owner: agent
· kept when: tests/s250-parity-claims.test.mjs BASELINE_UNBACKED monotone ceiling
|
| pending | undated |
The control plane's write-back currency probe resolves its repository root from its own module path and can therefore only measure studio-ops. The corrected resolution was shipped as Ark cargo so every sibling can inherit it; VEILOS no longer waits on it.
D-S260.4 · owner: founder
· kept when: upstream scripts/check-writeback-currency.mjs resolves root from git or cwd
|
| pending | S270 |
Decide what edge event constitutes a veil crossing, so the faculty can reach production. S261 proposed shadow mode (evaluate and record, deny nothing) as a way to convert the enforcement question into a measurement — and that proposal was too strong, which is recorded here rather than quietly dropped: shadow mode still requires a TRIGGER, and choosing the trigger is precisely the product decision
D-S261.4 · owner: founder
· kept when: a trigger is chosen and recorded as a decision, or the faculty is retired
|
| pending | S266 |
D-S259.3 split responsiveEvidenceCurrent by REASON rather than force-greening it, and that was right. But it enumerated ONE tolerable reason — build_sha_mismatch — and a second reason that is equally deploy-gated sits outside the classification. S262's suite reds on verified_at_stale: the cached capture has simply aged out, and only a fresh Playwright run against a real deploy can clear it. That i
D-S262.2 · owner: agent
· kept when: the reason classification is derived rather than enumerated, with deploy.mjs's refusal verified BEFORE the suite is relaxed and asserted after — or a real deplo
|
| pending | S268 |
The parity guard reads a QUOTED example of a parity claim as a real claim. Found live at S261: a comment in src/core/obligations.mjs quoting an illustrative claim reddened the guard, because the claim form is verbatim identical whether it is asserted or merely recounted. This is the same blind spot D-S260.7 fixed in the production-claim predicate, where the rule adopted was that a quotation mark i
D-S261.7 · owner: agent
· kept when: parityScan gains a quote-disqualifier with a control proving a quoted claim does not red and an asserted one still does
|
| kept | S265 |
src/worker/ip.mjs publishes, to the public: "Every crossing is policy-evaluated and produces a signed verdict; nothing crosses unwitnessed." That is FALSE in production. crossVeil — the only implementation of the faculty — is Node-lane only, so no crossing at the edge is ever policy-evaluated, no verdict is ever signed, and state.veilCrossings is permanently empty. The sentence is not aspirational
D-S261.3 · owner: founder
· kept when: either an edge twin evaluates crossings, or the ip.mjs sentence is rewritten to describe what production actually does — asserted by a test that drives the live
|
| kept | undated |
The closeout coherence gate runs LAST, on the final tree, right before commit — a claim stated in three files at once, and false for seventeen sessions (D-S258.3): the gate was on none of the autopilot's eleven steps while every one of those three comments said it ran.
D-S258.3 · owner: agent
· kept when: tests/s258-production-sha-carriers.test.mjs asserts steps.at(-1) === 'closeout:coherence' against the autopilot's own parsed step list
|
Machine ledger (JSON) → · The Boundary Census → · The Abstention Ledger → · The Failure Census →
A promise recorded here is not a promise kept. Pending means the date has not arrived; undischargeable means the commitment is real but nothing in the organism can currently decide whether it holds, which is debt rather than either a success or a failure. The organism spent sixty sessions learning not to overstate what is true of it now. This page exists because it had never once been accountable for what it said would be true later.