@conarium-ai/core 0.2.46 → 0.2.48

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,51 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.2.48 - the preprint is a claim surface
4
+
5
+ `paper/two-ledgers-one-window.md` joined `docs/claims/surfaces.json`. That
6
+ file ships in the tarball, so the number moves even though `paper/` does
7
+ not; v0.2.47 already holds the previous copy, and a tree that differs in
8
+ a shipped file from the tag it names is what `version_claim` refuses.
9
+
10
+ The preprint's text is CC BY 4.0 (`paper/LICENSE`); the software stays
11
+ MIT. The Zenodo record carries that licence. Nothing here changes a
12
+ tool.
13
+
14
+ **The Go verifier now exits like the Node verifier everywhere, not just
15
+ on the vectors.** Outside the thirteen frozen vectors, seven invocation
16
+ cases diverged: three usage exits (`--help`, no arguments, an unknown
17
+ flag), two missing targets (with and without an unrelated key flag),
18
+ valid JSON that is not JSONL, and directory mode beside a named
19
+ non-receipt JSON file. The finding, the differential guard that pins all
20
+ seven, and the fix are Iman Schrock's (EMILIA Protocol), PR #72. The
21
+ guard landed first and failed 7/7 against the unpatched tree; the fix
22
+ landed second and the same guard passes.
23
+
24
+ ## 0.2.47 - a number for the paper and the kit
25
+
26
+ v0.2.46 is on npm. Two things that are not that package now exist in
27
+ this repository, and publishing either of them under 0.2.46 would put
28
+ a new changelog and a new claims review on a number already sold.
29
+
30
+ **The two-ledgers preprint** (*Two ledgers, one window*) passed gate R2
31
+ on `docs/paper-two-ledgers`. `paper/` is not in the npm tarball. This
32
+ release does not republish the JSONL or exit-code rows already recorded
33
+ in 0.2.44–0.2.46.
34
+
35
+ **The starter kit** is `examples/starter-kit`: a local Postgres, three
36
+ mediated queries, signed receipts, and a reconcile against the
37
+ database's own counters. It is also not in the tarball. It is not a
38
+ second implementation.
39
+
40
+ `server.json` moves with `package.json` because the MCP registry reads
41
+ it and refuses a number it already holds.
42
+
43
+ `version_claim` asked npm with `--silent`. A 404 for a number that is
44
+ not on the registry arrived as an empty error, and the check printed
45
+ SKIP (registry unreachable) instead of "not tagged — nothing to
46
+ contradict". That is the state of every unpublished bump. The view is
47
+ no longer silent; E404 is "not published".
48
+
3
49
  ## 0.2.46 - three numbers that named something they were not
4
50
 
5
51
  Every item here is a figure this project printed, published, or wrote down,
@@ -0,0 +1,44 @@
1
+ # Claims review — 0.2.47
2
+
3
+ - base: v0.2.46
4
+ - head: f2372c9
5
+ - surface: sha256:b3c49849a617eb4dfab1fe4427a40f7de440516d30bf62894506be2c9c826e08
6
+ - verdict: pass
7
+ - reviewer: Claude, after the release branch merged `docs/draft-07`. The first
8
+ version of this record was written at `ea09896` by Cursor, before the draft
9
+ landed, and the gate refused it: the surfaces it described were not the ones
10
+ about to ship. Re-read from `v0.2.46` over the full set, `standards/README.md`
11
+ and `standards/draft-dogru-scitt-disclosure-evidence-07.md` included.
12
+
13
+ The version number moved because a new changelog section and this record
14
+ would otherwise ship under a number already on npm. `server.json` moves
15
+ with `package.json`. The starter kit landed as `examples/starter-kit` and
16
+ is excluded from the tarball. The two-ledgers preprint remains on
17
+ `docs/paper-two-ledgers`; `paper/` is not in this tree and is not in the
18
+ tarball. `-07` was read against the four neighbouring drafts it cites
19
+ (datatracker, 23 August 2026), against the -04 rewrite published by the
20
+ reviewer it thanks (no sentence of his entered the text), and its sentence
21
+ counts were recomputed with `test/draft_sentences.mjs`.
22
+
23
+ ## Findings
24
+
25
+ ### 1. standards/ADOPTION-EVIDENCE.md:20 — Vaara "adopted the wording"
26
+
27
+ - Claim: "Adopted the wording 'removal is detectable relative to a retained head' on the Vaara conformance / evidence page after the 21 August 2026 list exchange." — kind `wording adopted`
28
+ - Mechanism: the SCITT list archive and the Vaara page would show the sentence originating here and appearing there.
29
+ - Why it falls short: the sentence was proposed by Iman Schrock on the list (20 August 2026, `arch/msg/scitt/I5mdtYRinS-wjrnbwCnyXwwvrjU`) and endorsed in this project's reply the next morning. It appears nowhere in this repository before 23 August 2026. Vaara's `reproductions.json` credits this project with the observation that a truncated chain verifies clean, not with the wording. A citation was labelled an adoption.
30
+ - Disposition: reworded in `f2372c9` — kind `citation`, with the origin of the sentence stated and the three source URLs given.
31
+
32
+ ### 2. standards/ADOPTION-EVIDENCE.md:19 — Pablo Play "merged a partition"
33
+
34
+ - Claim: "Merged a partition of the receipt-set completeness discussion on the SCITT list (thread 'Closing omission', 21 August 2026)." — kind `citation`, URL "not retrieved in this pass"
35
+ - Mechanism: a list message from that sender citing this draft.
36
+ - Why it falls short: his three list messages of 19–20 August 2026 concern argentum-core and the coverage-attestation draft; none cites this draft. The row had no URL because there was nothing to point at.
37
+ - Disposition: row removed in `f2372c9`, with a note saying so. A row for Joel Hillier's draft announcement — whose own words call his disposition vocabulary this draft's standing ladder "now aimed at a very different question" — replaces it, with its archive URL.
38
+
39
+ ### 3. standards/ADOPTION-EVIDENCE.md:21 — Elara row without a reachable URL
40
+
41
+ - Claim: "Recorded this project's OpenSSL / ML-DSA-65 observation in Elara `SIGNING.md`" — URL "not re-fetched in this pass".
42
+ - Mechanism: the file itself.
43
+ - Why it falls short: it is a claim about a document nobody in this pass had opened. The file exists at `site/receipts/SIGNING.md` and names Emek Can Doğru and Conarium as the first verification of Elara bundles with non-Elara code — which is this project verifying Elara, the reverse direction from an adoption.
44
+ - Disposition: URL filled and the direction stated in `f2372c9`. `standards/ADOPTION-EVIDENCE.md` added to `docs/claims/surfaces.json` so the next row is read by the gate.
@@ -0,0 +1,86 @@
1
+ # Claims review — 0.2.48
2
+
3
+ - base: v0.2.47
4
+ - head: 1375041
5
+ - surface: sha256:46439a314e3f75c085c3df6e910adf0ac4f8d1dce42c0c2a9b9f9f33600dd382
6
+ - verdict: pass
7
+ - reviewer: Claude. The only surface that changed is the one that joined:
8
+ `paper/two-ledgers-one-window.md` (229 lines), read in full against the
9
+ question the gate asks. Its claim-to-source table (`paper/CLAIMS.md`,
10
+ 66 rows, 61 carrying `file:line`) was re-checked at the R2 gate on
11
+ 23 August 2026; this review re-read the prose, not the table.
12
+
13
+ The number moved for one file: `docs/claims/surfaces.json` ships in the
14
+ tarball and now lists the preprint. `paper/` itself is outside the
15
+ tarball. No tool changed.
16
+
17
+ ## Findings
18
+
19
+ ### 1. paper/two-ledgers-one-window.md:221 — the package version was pinned to the wrong mechanism
20
+
21
+ - Claim: "version `0.2.46` (declared, from the repository `package.json` at the commit that carries this preprint)."
22
+ - Mechanism: `package.json` at the carrying commit.
23
+ - Why it falls short: at the carrying commit `package.json` says `0.2.48`. The sentence would have been false the moment the branch merged. `0.2.46` is right as the release the preprint describes and the archived snapshot covers; the provenance given for it was wrong.
24
+ - Disposition: reworded in `c555243` — "the release this preprint describes and the snapshot below covers; the repository at the commit that carries this preprint names a later number". `CLAIMS.md` row updated to the npm registry as the mechanism.
25
+
26
+ ### 2. paper/two-ledgers-one-window.md:222 — the draft revision named was superseded on the day of merge
27
+
28
+ - Claim: "Individual Internet-Draft `draft-dogru-scitt-disclosure-evidence-06`".
29
+ - Mechanism: the datatracker.
30
+ - Why it falls short: `-07` was posted on 23 August 2026 (archive copy HTTP 200). Not false — `-06` exists — but a reader following the reference lands on `-07`, and the bib entry's note said the datatracker fetch had timed out.
31
+ - Disposition: `-07` in the markdown, the tex, the bib key and note, and `CLAIMS.md`, in `c555243`. The bib URL now points at the archive copy that was fetched.
32
+
33
+ ### 3. paper/BUILD.md — "the PDF was not compiled here" was about to become a stale denial
34
+
35
+ - Claim: "The PDF was **not compiled** here. Do not read `paper/arxiv/main.tex` as a file that has been shown to build."
36
+ - Mechanism: a build.
37
+ - Why it falls short: true until today; a denial left standing after the fact is the pattern `standards/README.md` carried for two days after -04 posted. The tex was compiled on 23 August 2026 in a TeX Live container (pdflatex, bibtex, pdflatex x2): exit 0, 15 pages, 0 undefined references or citations.
38
+ - Disposition: `BUILD.md` records the build and the command in `c555243`. `paper/build/` stays ignored.
39
+
40
+ ### 4. paper/two-ledgers-one-window.md:44 — the proposition pointed the reader the wrong way
41
+
42
+ - Claim: "Under assumptions A1–A7 below" — in the statement of Proposition 1.
43
+ - Mechanism: the assumptions section.
44
+ - Why it falls short: A1–A7 are stated in Section 3, above the proposition. "Below" sends a reader looking for text that is not there. Found on the pre-submission read of the compiled PDF.
45
+ - Disposition: "above", in the markdown and the tex. The same pass removed the ORCID placeholder from the title block, turned the bibliography's working notes ("opened", "confirmed on the abs page") into access dates, and removed every line that overflowed the margin (seven in the first build, none now).
46
+
47
+ ## Second pass — the surface moved after the record was written
48
+
49
+ The record above was written at `1c92b89`. Four commits then touched the
50
+ surface (`1084309`, `2a2b63e`, `edf0bf7`, `b187859`) and the gate refused the
51
+ release, correctly: the review described a text that was no longer the one
52
+ about to ship. The head and hash above are the re-read. Nothing was published
53
+ in between.
54
+
55
+ ### 5. standards/ADOPTION-EVIDENCE.md:20 — a list of figures was written as a ratio
56
+
57
+ - Claim: "at commit `a209864e`: 45 passed, 0 failed, 1 skipped over 75 cases."
58
+ - Mechanism: the Vaara conformance page, row #3.
59
+ - Why it falls short: the page writes the four figures as a list — "45 passed,
60
+ 0 failed, 1 skipped, 75 cases" — and the three outcome counts sum to 46, not
61
+ 75. "over 75 cases" invites a 45/75 reading the page does not state, and the
62
+ reading runs in our favour on a page another project maintains. Same class as
63
+ the prior-art row that was scored twice: the source's own units were replaced
64
+ with a stronger shape.
65
+ - Disposition: the page's phrasing restored, with the units named, in `1375041`.
66
+
67
+ ### Read and not a finding
68
+
69
+ - **`paper` sections renumbered** (unnumbered abstract, 1–10). The one internal
70
+ cross-reference moved with them: "the artefacts of Section 9" resolves to
71
+ `## 9. Artefacts`. No stale pointer left.
72
+ - **"two propositions" → "one conditional impossibility result and two
73
+ normative principles"**, and 2a/2b relabelled Principles throughout. The
74
+ change narrows what the paper claims: 2a and 2b are MUST-shaped rules, and
75
+ calling them propositions asserted a standing no proof in the paper carries.
76
+ - **A5 and the proof sketch now hold `G`'s internal randomness and state equal
77
+ across the two worlds.** Without it the construction leaks: a randomised
78
+ signature would differ between worlds that agree on every row. The assumption
79
+ is now stated rather than used silently, which is a narrowing, not a claim.
80
+ - **"a conditional impossibility result under seven explicit assumptions, not
81
+ an unconditional completeness theorem"** replaces "a proposition, not a
82
+ theorem". Considered as a possible upgrade of standing, since the argument
83
+ below it is labelled a proof sketch. Not recorded as a finding: every step of
84
+ the sketch cites the assumption it uses, the label carries "conditional" and
85
+ names the assumption count, and the sentence exists to deny the stronger
86
+ reading rather than to invite it.
@@ -110,6 +110,16 @@
110
110
  "path": "docs/security/NPM-PROVENANCE.md",
111
111
  "why": "Ships in the tarball and tells a reader how to check where the package came from. Unlisted until 0.2.33, by which point it had gone stale in the worst direction: it said 'this is not a published release' inside eight published releases, and pointed at a verification command that answers 404 for npm provenance. A page about how to distrust us is one a reader must be able to trust.",
112
112
  "phrasing": true
113
+ },
114
+ {
115
+ "path": "standards/ADOPTION-EVIDENCE.md",
116
+ "why": "Public on GitHub and linked from standards/README.md. Every row asserts what an outside party did with this draft; a row that overstates a citation as an adoption is the same overclaim the kind labels exist to prevent. Its first version carried one.",
117
+ "phrasing": true
118
+ },
119
+ {
120
+ "path": "paper/two-ledgers-one-window.md",
121
+ "why": "A preprint is read as the project's claim about what the method shows; it is the one surface that outlives the package.",
122
+ "phrasing": true
113
123
  }
114
124
  ]
115
125
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@conarium-ai/core",
3
- "version": "0.2.46",
3
+ "version": "0.2.48",
4
4
  "mcpName": "io.github.dogrucanemek-alt/conarium",
5
5
  "//files-artefakt": "Generated files under examples/ (private key, receipt/audit JSONL) are EXCLUDED. .gitignore does not bind npm: because the allow-list contained 'examples', `npm publish` on a machine that had run the demo was shipping _keys/audit-ed25519.pem (PRIVATE KEY) and the receipts. test/pack_artefakt.mjs locks this. The exclusions are LIMITED to examples/: receipts.jsonl and .pub.pem under test-vectors/ MUST ship, or a third party cannot run the conformance vectors.",
6
6
  "//files": "Allow-list of what enters the package. Without it npm sent everything: 296 files / 1.5 MB — CI workflows, gitleaks config, a 137 KB marketing image, the site's api/chat.js. A bank security team opens the tarball and sees those. scripts/ is here ON PURPOSE: conarium-reconcile references scripts/pg-snapshot.sql at runtime; without it the user files a support mail.",
@@ -28,6 +28,10 @@
28
28
  "!examples/**/*.jsonl",
29
29
  "!examples/**/*.keyid",
30
30
  "!examples/**/conarium.tokens.json",
31
+ "!examples/starter-kit",
32
+ "!examples/starter-kit/**",
33
+ "!examples/missing-record-demo",
34
+ "!examples/missing-record-demo/**",
31
35
  "conformance",
32
36
  "test-vectors",
33
37
  "!test-vectors/jcs/rfc8785",