@conarium-ai/core 0.2.46 → 0.2.47

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,30 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.2.47 - a number for the paper and the kit
4
+
5
+ v0.2.46 is on npm. Two things that are not that package now exist in
6
+ this repository, and publishing either of them under 0.2.46 would put
7
+ a new changelog and a new claims review on a number already sold.
8
+
9
+ **The two-ledgers preprint** (*Two ledgers, one window*) passed gate R2
10
+ on `docs/paper-two-ledgers`. `paper/` is not in the npm tarball. This
11
+ release does not republish the JSONL or exit-code rows already recorded
12
+ in 0.2.44–0.2.46.
13
+
14
+ **The starter kit** is `examples/starter-kit`: a local Postgres, three
15
+ mediated queries, signed receipts, and a reconcile against the
16
+ database's own counters. It is also not in the tarball. It is not a
17
+ second implementation.
18
+
19
+ `server.json` moves with `package.json` because the MCP registry reads
20
+ it and refuses a number it already holds.
21
+
22
+ `version_claim` asked npm with `--silent`. A 404 for a number that is
23
+ not on the registry arrived as an empty error, and the check printed
24
+ SKIP (registry unreachable) instead of "not tagged — nothing to
25
+ contradict". That is the state of every unpublished bump. The view is
26
+ no longer silent; E404 is "not published".
27
+
3
28
  ## 0.2.46 - three numbers that named something they were not
4
29
 
5
30
  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.
@@ -110,6 +110,11 @@
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
113
118
  }
114
119
  ]
115
120
  }
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.47",
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,8 @@
28
28
  "!examples/**/*.jsonl",
29
29
  "!examples/**/*.keyid",
30
30
  "!examples/**/conarium.tokens.json",
31
+ "!examples/starter-kit",
32
+ "!examples/starter-kit/**",
31
33
  "conformance",
32
34
  "test-vectors",
33
35
  "!test-vectors/jcs/rfc8785",