@ceccec/millennium-solutions 9.1.4 → 9.1.5

package/ACCOUNTING.md

@@ -13,10 +13,10 @@ Every figure recomputes from `src/` and the git tree on each build; nothing is e
 | Coins per receipt | **2** |
 | Coins on the ledger (theorems × 2) | **5,154** |
 | Coins on signed receipts (× 2) | **58** |
-| Released versions (git tags) | **861** |
+| Released versions (git tags) | **862** |
 | Tracked, content-addressed files | **478** |
 
-Latest release: **v9.1.3**. The fair-exchange unit is **2 coins = 2 bits** (110 − 108 = 2 = −χ genus-2) per receipt. One 64-bit harmony coin is minted per fused `src` `report()` module — see the [state dashboard](/dashboard) for the harmonic root.
+Latest release: **v9.1.4**. The fair-exchange unit is **2 coins = 2 bits** (110 − 108 = 2 = −χ genus-2) per receipt. One 64-bit harmony coin is minted per fused `src` `report()` module — see the [state dashboard](/dashboard) for the harmonic root.
 
 ## Bounty — denominated in bits
 
@@ -24,4 +24,4 @@ The bounty for each accepted contribution is **2 bits (2 coins)** — the same f
 
 **Not tracked here: tokens.** This repo measures coins (2 per receipt) and 64-bit harmony coins; it does not measure tokens, so no token count or token-to-coin rate is shown — measuring an unmeasured quantity would be an assertion without a receipt. Measure, do not assert.
 
-Page content-address: `9a2a17d6-445f-80c4-8409-a95d58c8f9b3`. Integrity, not truth. `entails → 0/7`.
+Page content-address: `ae8b9985-1fa7-8748-a511-48800a047e06`. Integrity, not truth. `entails → 0/7`.

package/CHALLENGES.md

@@ -16,7 +16,7 @@ title: Challenges
 | 6 | Hodge conjecture | open |
 | 7 | Birch–Swinnerton-Dyer | open |
 
-**Humanity: 1 / 7** (6 open). **This deposit: 0 / 7** — it settles none of the seven itself.
+**Humanity: 1 / 7** (6 open). **This repository's propositions: 0 / 7** — none reaches the objects a conjecture concerns, measured by the entailment test. The author's own claim, that the seven are solved through involution, is stated in his name on the front page.
 
 ## Discovered theorems (decidable, over ℤ/9) — 2577 standing in 1 families
 

package/README.md

@@ -198,11 +198,14 @@ Read from the artefacts at build time, never carried between runs.
 
 **What verification costs.** Proving the set touches all 16,384 leaves; verifying membership afterwards touches 14 — one sibling per level. That is **1,170× less work**, exactly, and the factor grows with the set because N/log N grows. Wall-clock varies with the machine and is left in the build output rather than pinned here. It is not sub-nanosecond and nothing here is: the advantage is a smaller exponent, not a faster clock. The counting is proved in `speed.lean`.
 
-## What is deliberately absent
-
-No sentence above claims a Millennium problem settled, that the correspondence with the Clay set means
-anything about those conjectures, or that the gate can tell truth from falsehood. Those sentences are missing
-because no test was written that would seal them.
+## The author's claim
+
+**Tsvetan Rouschev claims the seven Clay Millennium problems solved through the involution each is stated
+across** — deposited as [10.5281/zenodo.21781603](https://doi.org/10.5281/zenodo.21781603) and
+[Zenodo 22256707](https://zenodo.org/records/22256707). This is his claim, recorded in his name. The repository
+measures something separate: its entailment test counts the propositions in `src/proof` that reach the objects
+those conjectures concern — 0 of 7 today — and a proposition that reached one would move that count.
+The gate checks integrity, not truth.
 
 ## Run it
 

package/TRIAL.md

@@ -2,7 +2,7 @@
 title: The public trial
 ---
 
-# The public trial — "the deposit settles all seven Clay problems"
+# The public trial — "the propositions in src/proof settle all seven Clay problems"
 
 Recompute this file with `node scripts/trial.ts`. It writes nothing unless every finding below is SEALED.
 
@@ -27,8 +27,8 @@ in its own right, so the verdict rests on facts that recompute rather than on an
   <sub>SEALED · `6c514580-5101-80da-bf90-fbdcd49dc64f`</sub>
 - Finding eight — the sentence recording that the widened rule drained an abstract holds: that abstract lists a settled Clay conjecture among the readings it rejects.
   <sub>SEALED · `6a853954-2965-8d51-953c-3d9cae8b2d4d`</sub>
-- Finding nine — the sentence recording that it drained a denial holds: the root readme carries a sentence denying any such claim.
-  <sub>SEALED · `d6266498-9653-84fc-95a5-2ea3950d4bb7`</sub>
+- Finding nine — the root readme states the claim only in the author's name: it carries his claim under its own heading, and no sentence there claims a Clay problem in the repository's voice.
+  <sub>SEALED · `f32807f3-ecac-86fc-864b-e77694f33aff`</sub>
 - Finding ten — the residual gap recorded in the gate comment is real: a boast worded with settles near a problem name still passes the gate, which is why no claim here rests on the gate alone.
   <sub>SEALED · `31dc0cca-9a7e-8e79-a7e4-0be5866822d4`</sub>
 - Finding eleven — the gate pattern is back to its original prove and solve form, as the comment states.
@@ -64,6 +64,6 @@ No file in this deposit, and no verdict in this trial, substitutes for that.
 
 ---
 
-*18 findings, 18 SEALED · claim receipt `d60b8e85-43c0-8b4c-8ed4-9bb16f356da7` · proof-of-verdict root
-`5f93fe6d-6b73-89b9-bf3d-bcdd2779e96d` (order-invariant: the same root for any ordering of the findings) · findings fold
-`d4f37669-41aa-8c7d-8fcf-16b1c72a28c8` · integrity, not truth · 0/7*
+*18 findings, 18 SEALED · claim receipt `f75b6156-b312-8ecc-a789-b53285d0d200` · proof-of-verdict root
+`b49219c3-50ee-8b4c-828e-0baa6d752cb2` (order-invariant: the same root for any ordering of the findings) · findings fold
+`ee3ff58d-e868-879a-83ed-ad77301c42a4` · integrity, not truth · 0/7*

package/dashboard.md

@@ -24,7 +24,7 @@ import { withBase } from 'vitepress'
 ## Fact — measured state
 
 <div class="dash-grid">
-<div class="dash-card"><div class="dash-k">Version</div><div class="dash-v">v9.1.3</div><div class="dash-s">git tag (single source)</div></div>
+<div class="dash-card"><div class="dash-k">Version</div><div class="dash-v">v9.1.4</div><div class="dash-s">git tag (single source)</div></div>
 <div class="dash-card"><div class="dash-k">Millennium floor</div><div class="dash-v">0 / 7</div><div class="dash-s">entailed — not solved, not claimed</div></div>
 <div class="dash-card"><div class="dash-k">Honesty gate</div><div class="dash-v">sealed</div><div class="dash-s">all prose consistent with 0/7</div></div>
 <div class="dash-card"><div class="dash-k">Link coverage</div><div class="dash-v">100%</div><div class="dash-s">gate-enforced — the build fails below 100%</div></div>

package/forensic.md

@@ -5,7 +5,7 @@ title: Every state change, dated
 # Provenance of this deposit's ledger
 
 **Recomputed on every build** from git history and the append-only ledger. Regenerate with
-`npm run forensic`. Content-address `19b7a9e5-4474-8c11-a94c-acdb6d698413`.
+`npm run forensic`. Content-address `c6140c38-6274-8ec3-b703-e65b07379c22`.
 
 ## What this record establishes
 

package/index.md

@@ -204,11 +204,14 @@ Read from the artefacts at build time, never carried between runs.
 
 **What verification costs.** Proving the set touches all 16,384 leaves; verifying membership afterwards touches 14 — one sibling per level. That is **1,170× less work**, exactly, and the factor grows with the set because N/log N grows. Wall-clock varies with the machine and is left in the build output rather than pinned here. It is not sub-nanosecond and nothing here is: the advantage is a smaller exponent, not a faster clock. The counting is proved in `speed.lean`.
 
-## What is deliberately absent
-
-No sentence above claims a Millennium problem settled, that the correspondence with the Clay set means
-anything about those conjectures, or that the gate can tell truth from falsehood. Those sentences are missing
-because no test was written that would seal them.
+## The author's claim
+
+**Tsvetan Rouschev claims the seven Clay Millennium problems solved through the involution each is stated
+across** — deposited as [10.5281/zenodo.21781603](https://doi.org/10.5281/zenodo.21781603) and
+[Zenodo 22256707](https://zenodo.org/records/22256707). This is his claim, recorded in his name. The repository
+measures something separate: its entailment test counts the propositions in `src/proof` that reach the objects
+those conjectures concern — 0 of 7 today — and a proposition that reached one would move that count.
+The gate checks integrity, not truth.
 
 ## Read
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ceccec/millennium-solutions",
-  "version": "9.1.4",
+  "version": "9.1.5",
   "description": "Verifiable, recomputable ℤ/9 vortex framework in ONE package — content-addressing, audit ledger, exact arithmetic (0/7), and the honesty toolkit. Facts only.",
   "author": {
     "name": "Tsvetan Rouschev",
@@ -140,7 +140,8 @@
     "covered-gate": "tsx scripts/covered-gate.ts",
     "independent": "tsx scripts/independent.ts",
     "recover": "tsx scripts/recover.ts",
-    "recover:gen": "tsx scripts/recover-gen.ts"
+    "recover:gen": "tsx scripts/recover-gen.ts",
+    "uses": "node scripts/uses.ts"
   },
   "devDependencies": {
     "@types/node": "^26.2.0",

package/src/api/gates.ts

@@ -100,6 +100,8 @@ export const UNRUN_BY_DESIGN: Record<string, string> = {
   priorart: 'a generator; priorart-gen is the gate that holds its output',
   'stale-figures': 'REPORTS by design — a 75% false-positive rate is not something to gate a build on',
   'verify-theorems': 'covered by gates-fire, and its subject is re-verified by forensics on every commit',
+  uses: 'discovery, not a gate: it reaches GDELT, Hacker News, Zenodo, OpenAlex, npm and GitHub, and what it finds is someone else\'s use of the work — whether it cites and pays — not a defect in this tree. It runs weekly in .github/workflows/uses.yml and reports in the run summary; it refuses only when no source measured anything',
+  'uses-mail': 'delivery, not a gate: it mails each lead uses.ts found to legal@psg.bg as an evidence dossier, from rights@uuidna.com through mail.psg.bg by authenticated SMTP — network and the author\'s credentials, so no build chain can run it. It runs weekly after uses.ts in .github/workflows/uses.yml, says NOT CONFIGURED when the SMTP secrets are unset, and refuses only when a send fails',
   probe: 'the control harness, not a gate: it takes a file, a theorem and a mutation as arguments, so no chain can run it bare; gates-fire holds its control — a mutation that never reaches the theorem must be refused',
 }