@conarium-ai/core 0.2.33 → 0.2.35

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,91 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.2.35 — 2026-08-20 — two sentences that our own actions made false
4
+
5
+ Nothing in the engine changed. This release exists because publishing 0.2.34
6
+ invalidated a paragraph inside 0.2.34, which is a small thing that says something
7
+ about how documentation ages here.
8
+
9
+ - **`docs/security/NPM-PROVENANCE.md` said the full publish path had not run
10
+ yet.** It ran a few hours later, publishing 0.2.34 itself. The page now
11
+ separates the two histories: 0.2.33 carries a tarball and an attestation and no
12
+ bill of materials, because its artefacts were attached by the mode that skips
13
+ that step; 0.2.34 carries all three because the full path produced them. The
14
+ paragraph ends by pointing at the release page rather than at itself, which is
15
+ the only version of this sentence that does not expire.
16
+ - **The OpenSSF Best Practices badge is in the README, with what it is not.**
17
+ The project earned the passing badge on 2026-08-19 (project 14160, 64 of 67
18
+ criteria met, 3 not applicable and stated as such). The README says in the same
19
+ breath that this is self-certification rather than an audit, that the answers
20
+ are public and checkable, and that the Scorecard badge beside it carries a
21
+ `Code-Review` score of 0 because pull requests here are merged without a second
22
+ approver. A badge added without that sentence would be the kind of claim this
23
+ package spends its time refusing.
24
+ - One criterion was corrected before it was submitted rather than after: the
25
+ first answer for "the test suite covers most of the code" asserted coverage
26
+ that had never been measured. It now describes what is exercised and says the
27
+ ratio is not reported.
28
+
29
+ ## 0.2.34 — 2026-08-19 — the prior-art claim that got narrower
30
+
31
+ A comparative claim in this package was too strong, and the correction came from
32
+ reading a competitor's source rather than from a gate of ours catching it.
33
+
34
+ - **`docs/PRIOR-ART.md` no longer says nobody else has arrived at the idea.**
35
+ Vaara (`vaaraio/vaara`, AGPL-3.0) specifies a coverage reconciliation in
36
+ `credential-broker-spec.md` §D — joining each used credential to the receipt it
37
+ should have produced, and reading a mismatch as a bypassed broker — with its
38
+ limits stated in §E. The row is scored from source: the tree at `befdced` was
39
+ cloned, its contiguity tests run, and searched for code implementing that
40
+ design. None was found, so the column reads **"specified, not found
41
+ implemented"** rather than yes.
42
+ - **That row was scored twice, and the first scoring is left on the page.** It
43
+ first read "Yes", on the strength of the design section alone — scoring a
44
+ specification as behaviour, which is the confusion this file's own column
45
+ definitions warn about two sections above. The correction is recorded where the
46
+ row is, not quietly.
47
+ - **What survives is stated in the narrower form.** The claim stands on
48
+ implementation, which is what every other row is scored on. What it can no
49
+ longer carry is that nobody else has had the idea. Anyone quoting the file
50
+ should quote *"we have not found another implementation that masks values
51
+ before the model sees them and then reconciles what it disclosed"* — not
52
+ *"nobody else reconciles"* and not *"none of the ten has the third column"*.
53
+ - **The Microsoft row said "Merkle-chained" and their tutorial describes a linear
54
+ `parent_receipt_hash`.** Overstating a competitor's mechanism is the same defect
55
+ as overstating our own, so it is corrected in the same pass.
56
+ - **`README.md` says eleven projects, and says which way the eleventh moved the
57
+ claim.** A comparison page that only ever gains rows it wins is not evidence.
58
+ - **`docs/security/NPM-PROVENANCE.md` documents the three release artefacts the
59
+ full publish path is configured to produce** — the published tarball, a
60
+ CycloneDX bill of materials, and a build attestation written to GitHub's
61
+ attestation store — and says which of them any given release actually carries.
62
+ The artefact path first ran on 19 August in `artefacts` mode against 0.2.33,
63
+ which now carries the tarball and the attestation but no bill of materials.
64
+ - **The changelog had stopped one version short of the package again**: 0.2.33
65
+ shipped before its entry was written, and that entry is below. The publish
66
+ workflow now refuses a version whose section does not exist, so the next
67
+ occurrence is a red gate rather than a discovery.
68
+
69
+ ## 0.2.33 — 2026-08-19
70
+
71
+ Written on 2026-08-19, after 0.2.33 had already shipped without it. The gap is
72
+ recorded rather than backdated.
73
+
74
+ - **The provenance page stopped saying there was nothing to verify.**
75
+ `docs/security/NPM-PROVENANCE.md` still read *"This is not a published
76
+ release"* eight releases after the first one, and pointed readers at
77
+ `gh attestation verify`, which answers `404` for a package published with npm
78
+ provenance — that command reads GitHub's attestation store, while
79
+ `npm publish --provenance` writes to the npm registry and its transparency log.
80
+ A reader checking the honest way would have read that 404 as "no attestation",
81
+ which is the opposite of the truth.
82
+ - The working commands replaced it: `npm view … dist --json`, which returns the
83
+ `attestations` block naming `slsa.dev/provenance/v1`, and `npm audit
84
+ signatures`. The `gh` command stayed on the page as a warning with its reason,
85
+ because a reader who tries it deserves to know why it fails.
86
+ - Found by an external review, not by our own claim gate. The gate locks phrasings
87
+ already caught; this file was never in the list of surfaces it reads.
88
+
3
89
  ## 0.2.32 — 2026-08-19
4
90
 
5
91
  Tool descriptions now say what the tools do to the world, not just what they are
package/README.md CHANGED
@@ -7,6 +7,7 @@
7
7
  <a href="https://www.npmjs.com/package/@conarium-ai/core"><img src="https://img.shields.io/npm/v/@conarium-ai/core?style=for-the-badge" alt="npm" /></a>
8
8
  <a href="https://github.com/dogrucanemek-alt/conarium/actions/workflows/security.yml"><img src="https://img.shields.io/github/actions/workflow/status/dogrucanemek-alt/conarium/security.yml?branch=main&style=for-the-badge&label=CI" alt="CI" /></a>
9
9
  <a href="https://securityscorecards.dev/viewer/?uri=github.com/dogrucanemek-alt/conarium"><img src="https://api.securityscorecards.dev/projects/github.com/dogrucanemek-alt/conarium/badge" alt="OpenSSF Scorecard" /></a>
10
+ <a href="https://www.bestpractices.dev/projects/14160"><img src="https://www.bestpractices.dev/projects/14160/badge" alt="OpenSSF Best Practices" /></a>
10
11
  <a href="https://conarium.dev"><img src="https://img.shields.io/badge/Website-conarium.dev-5a8cff?style=for-the-badge" alt="Website" /></a>
11
12
  <a href="https://github.com/dogrucanemek-alt/conarium/blob/main/LICENSE"><img src="https://img.shields.io/badge/License-MIT-f2d79a?style=for-the-badge" alt="License" /></a>
12
13
  <img src="https://img.shields.io/badge/Status-Early%20Access-ff6f80?style=for-the-badge" alt="Early Access" />
@@ -421,11 +422,17 @@ is verifiable without trusting us; this particular figure is our own measurement
421
422
  and [Governance Report 001](https://conarium.dev/report-001.html) lists its limits.
422
423
 
423
424
  That claim is hedged on purpose, and [`docs/PRIOR-ART.md`](docs/PRIOR-ART.md) is the
424
- evidence behind it: ten projects checked on 6 August 2026, what each one has, the
425
- closest academic prior art ([Sello / *Notarized Agents*](https://arxiv.org/html/2606.04193v1),
426
- which names this gap better than we did), and nine things we could **not** verify. If
427
- you know of an implementation combining all three, open an issue and it will be
428
- corrected.
425
+ evidence behind it: eleven projects — ten checked on 6 August 2026 and Vaara added
426
+ on 19 August — what each one has, the closest academic prior art
427
+ ([Sello / *Notarized Agents*](https://arxiv.org/html/2606.04193v1), which names this
428
+ gap better than we did), and nine things we could **not** verify. If you know of an
429
+ implementation combining all three, open an issue and it will be corrected.
430
+
431
+ ⚠️ The Vaara row narrowed this claim rather than confirming it. That project
432
+ *specifies* a coverage reconciliation in its design documents; a search of its
433
+ tree found no code running it, so the row reads "specified, not found
434
+ implemented". The idea is not ours alone — the running code, as far as this scan
435
+ reaches, still is, and the file says so above its own table.
429
436
 
430
437
  ---
431
438
 
@@ -686,6 +693,14 @@ per-user identity bound to an identity provider rather than an operator token ma
686
693
  and coverage declarations are yours to show your own auditor, and whether they
687
694
  satisfy a given audit is between you and that auditor. If we ever hold your
688
695
  data, or an engagement turns on the certificate itself, this line changes first.
696
+ - **The OpenSSF Best Practices badge above is self-certification, not an audit.**
697
+ We answered its 67 questions and published the answers; anyone can read them at
698
+ [project 14160](https://www.bestpractices.dev/projects/14160) and check each one
699
+ against this repository. That is worth something — the answers are falsifiable —
700
+ and it is not the same thing as someone independent having looked. Three of the
701
+ 67 are marked not-applicable and say why. The Scorecard badge beside it is
702
+ machine-measured and includes a `Code-Review` score of 0, because pull requests
703
+ here are merged without a second approver.
689
704
 
690
705
  Known gaps: [LIMITATIONS.md](LIMITATIONS.md), the README above,
691
706
  [`docs/RECEIPT-SPEC.md`](docs/RECEIPT-SPEC.md),
package/docs/PRIOR-ART.md CHANGED
@@ -7,6 +7,11 @@ We make one comparative claim about Conarium:
7
7
  > enforcement, and (3) coverage reconciliation against the data source's own
8
8
  > query counters.
9
9
 
10
+ ⚠️ **Read that as a claim about implementations.** Since 19 August this file
11
+ carries a project that *specifies* part 3 without our finding it implemented —
12
+ see the Vaara row and the note under the table. The idea is not ours alone; the
13
+ running code, as far as this scan reaches, still is.
14
+
10
15
  A claim like that is unfalsifiable if we just assert it, so this file is the
11
16
  evidence behind it: what we searched, on what date, what we found, and — the part
12
17
  most comparison pages leave out — **what we could not verify.** If you know of an
@@ -16,6 +21,14 @@ implementation that does all three, open an issue and this file will be correcte
16
21
  official site, plus targeted web searches. **Source-code-level search was not
17
22
  performed on any repository** — see Limitations.
18
23
 
24
+ **Amended 19 August 2026.** Vaara was added after its author raised a related
25
+ mechanism on the SCITT mailing list. It is the one row scored from source rather
26
+ than from documentation: the repository was cloned at `befdced`, its contiguity
27
+ tests were run (`PYTHONPATH=src python -m pytest tests/credential/test_contiguity.py`
28
+ → 18 passed), the cited design sections were read, and the tree was searched for
29
+ code implementing them. That search is why the row was rescored the same day —
30
+ see the note under the table.
31
+
19
32
  ## What the three parts mean
20
33
 
21
34
  Precision matters here, because two of them are commonly confused:
@@ -37,7 +50,7 @@ perfectly intact.
37
50
 
38
51
  | Project | Enforcement | Portable signed receipt | Coverage reconciliation |
39
52
  |---|---|---|---|
40
- | [microsoft/agent-governance-toolkit](https://github.com/microsoft/agent-governance-toolkit) | Partial — Cedar allow/deny, DLP attribute ratchets; PII masking not documented | **Yes** — Ed25519, Merkle-chained, `verify_receipt_chain()` | No |
53
+ | [microsoft/agent-governance-toolkit](https://github.com/microsoft/agent-governance-toolkit) | Partial — Cedar allow/deny, DLP attribute ratchets; PII masking not documented | **Yes** — Ed25519, hash-chained (`parent_receipt_hash`), `verify_receipt_chain()`. This said "Merkle-chained" until 19 August; their tutorial describes a linear parent hash, and overstating a competitor's mechanism is the same defect as overstating our own | No |
41
54
  | [Signet](https://github.com/Prismer-AI/signet) | Partial — policy bound into the receipt; no masking | **Yes** — Ed25519, hash-chained, offline | No |
42
55
  | [Handshake.AI](https://handshake.ai/) | No | **Yes** — signed action receipts, DID-issued, offline | No |
43
56
  | [hoophq/hoop](https://github.com/hoophq/hoop) | **Yes — strongest here.** ML-based masking before bytes leave the gateway | No — session recording/replay, no signed offline-verifiable artifact found | No |
@@ -47,11 +60,42 @@ perfectly intact.
47
60
  | [lasso-security/mcp-gateway](https://github.com/lasso-security/mcp-gateway) | **Yes** — Presidio PII masking, injection filters | No — no signing mechanism documented | No |
48
61
  | [h33.ai](https://h33.ai/) | **Yes, and further** — FHE; the model never sees plaintext | **Yes** — ZK-STARK + Dilithium, verifiable "years later, offline, without the original vendor" | No |
49
62
  | [CertNode](https://certnode.io/solutions/ai-agents) | Weak — no blocking gate | **Yes** — ES256 JWS + RFC 3161 | No |
63
+ | [vaaraio/vaara](https://github.com/vaaraio/vaara) | Partial — `CredentialGateway` authorizes each tool call against a brokered credential and refuses without one; no value masking found. Its redaction is GDPR Art. 17 erasure inside the audit store, which is a different guarantee | **Yes** — signed decision record (ES256/HS256/RS256) over JCS-canonical blocks, evidence pinned by `evidenceRef.digest`, standalone checkers under `tests/vectors` that import none of their code | **Specified, not found implemented.** `docs/design/credential-broker-spec.md` §D designs the join — each used credential to a receipt on `attestationDigest`, a used credential with no matching receipt read as a bypassed broker — and §E states its limit: *"detection of a defeated broker, not a mathematical-completeness claim"*. At `befdced` we found no collector, join, CLI or test implementing it; `gateway.py` points at the design document for that residual rather than at code. **This is the only design for it we have found outside our own** |
50
64
 
51
65
  The landscape splits cleanly. One camp enforces well but issues no portable evidence
52
66
  (hoop.dev, Lasso). The other issues excellent portable evidence but does not enforce
53
- before the model (Signet, Circe, Acta, agentreceipts, Handshake, CertNode). Two
54
- projects do both — Microsoft's toolkit and h33.ai — and neither does the third.
67
+ before the model (Signet, Circe, Acta, agentreceipts, Handshake, CertNode). Three
68
+ projects do the first two — Microsoft's toolkit, h33.ai and Vaara — and none of
69
+ them was found running the third.
70
+
71
+ ### What the Vaara row cost the claim, and what it did not
72
+
73
+ This row was scored twice on 19 August, and the first scoring was wrong in a way
74
+ worth leaving on the page.
75
+
76
+ It first read **Yes** on coverage reconciliation, on the strength of
77
+ `credential-broker-spec.md` §D. That section designs the join and states its own
78
+ limit honestly, and reading it is enough to see that someone else has had this
79
+ idea and thought it through. It is not enough to see it run. A search of the tree
80
+ at `befdced` for a collector of used credentials, a join, a CLI or a test found
81
+ none, and `gateway.py` refers that residual to the design document rather than to
82
+ code. Scoring a specification as behaviour is the same confusion this file's own
83
+ column definitions warn about two sections above — *"not that the log records that
84
+ it happened, but that the value never left"* — committed by the person who wrote
85
+ them.
86
+
87
+ So the combined claim stands on implementation, which is what every other row in
88
+ this table is scored on. What it can no longer carry is the suggestion that
89
+ nobody else has arrived at the idea. Someone has, in public, with the limits
90
+ stated. The honest form:
91
+
92
+ > **We have not found another implementation that masks values before the model
93
+ > sees them and then reconciles what it disclosed against the source's own
94
+ > bookkeeping. One other project specifies such a reconciliation; we did not find
95
+ > it implemented.**
96
+
97
+ Anyone quoting this file should quote that, not "nobody else reconciles" and not
98
+ "none of the ten has the third column".
55
99
 
56
100
  ### Two near misses worth naming precisely
57
101
 
@@ -0,0 +1,119 @@
1
+ # Claims review — 0.2.34
2
+
3
+ - base: v0.2.33
4
+ - head: 0198ccf
5
+ - surface: sha256:e80fad84574da3554959e855d5e9cb4db1a32b9e4cc3f58f3dd87db369dad5c3
6
+ - verdict: pass
7
+ - reviewer: Claude (Opus 5), then an independent pass by Codex and one by Cursor
8
+ before the version was pushed
9
+
10
+ Four surfaces changed: `docs/PRIOR-ART.md`, `README.md`, `CHANGELOG.md`,
11
+ `docs/security/NPM-PROVENANCE.md`. The release is itself a claims correction, so
12
+ most of the diff removes reach. The findings below are ordered by who found them,
13
+ because that ordering is the useful part of this record: **the first pass missed
14
+ the two that mattered, and both were found by readers who had not written the
15
+ text.**
16
+
17
+ ## Findings
18
+
19
+ ### 1. docs/PRIOR-ART.md — a design section scored as behaviour
20
+
21
+ - Claim: the Vaara row read **"Yes — the only other one here"** on coverage
22
+ reconciliation, and the file, `README.md` and `CHANGELOG.md` all said that
23
+ project *reconciles*.
24
+ - Mechanism: `docs/design/credential-broker-spec.md` §D at `befdced`, which
25
+ designs a join of used credentials to receipts on `attestationDigest`.
26
+ - Why it falls short: §D is a design document. A search of that tree for a
27
+ collector of used credentials, the join, a CLI or a test found none, and
28
+ `src/vaara/credential/gateway.py` refers that residual to the design document
29
+ rather than to code. Every other row in the table is scored on what a project
30
+ is found doing. Scoring a specification as behaviour is the confusion this
31
+ file's own column definitions warn about — *"not that the log records that it
32
+ happened, but that the value never left"* — committed by the person who wrote
33
+ them, in the row that changed the headline claim.
34
+ - Disposition: rescored **"Specified, not found implemented"** in `0198ccf`,
35
+ with the first scoring left visible on the page rather than quietly replaced.
36
+ `README.md` and `CHANGELOG.md` narrowed to match. The retired phrasings are
37
+ named so they are not requoted: *"nobody else reconciles"*, *"none of the ten
38
+ has the third column"*.
39
+ - **Found by: Codex.** Not by the first pass, which had read the same section and
40
+ taken it at its word.
41
+
42
+ ### 2. docs/PRIOR-ART.md — the summary paragraph contradicted the new row
43
+
44
+ - Claim: *"Two projects do both — Microsoft's toolkit and h33.ai — and neither
45
+ does the third."*
46
+ - Mechanism: the table directly above it.
47
+ - Why it falls short: the sentence sat unchanged three lines under a row that
48
+ had just been scored **Yes** on the third column. The paragraph immediately
49
+ after it was rewritten in the same edit; this one was not. A reader opening the
50
+ file from the post's first comment meets the contradiction before the
51
+ correction.
52
+ - Disposition: rewritten in `0198ccf` to name three projects and say none was
53
+ found running the third.
54
+ - **Found by: Cursor.** The first pass edited the paragraph below it and did not
55
+ re-read the paragraph above.
56
+
57
+ ### 3. docs/security/NPM-PROVENANCE.md — a limitation that expired the same day
58
+
59
+ - Claim: *"Those steps have not run yet — 0.2.34 is the first release that will
60
+ execute them"*, and *"every version published so far has only npm's
61
+ attestation"*.
62
+ - Mechanism: the workflow runs and the release pages.
63
+ - Why it falls short: both were true when written and false a few hours later.
64
+ The `artefacts` mode added in #32 was dispatched against 0.2.33 (runs
65
+ `32295097847`, `32295276511`), which verified the registry tarball, produced a
66
+ GitHub attestation and created that release. `v0.2.33` now carries
67
+ `conarium-ai-core-0.2.33.tgz` and `.tgz.intoto.jsonl`, and
68
+ `gh attestation verify` returns 0 for it.
69
+ - Disposition: replaced in `0198ccf` with what has actually run, including that
70
+ 0.2.33 carries no bill of materials because that step is skipped in artefacts
71
+ mode, and that the full publish path has still not run.
72
+ - **Found by: Codex.** Worth noting how it expired: this was a self-correction in
73
+ the first pass (finding 5 below), written carefully, and then invalidated by
74
+ our own action. A sentence about what has not happened yet has a shelf life.
75
+
76
+ ### 4. CHANGELOG.md — three assets described as an existing state
77
+
78
+ - Claim: *"releases now carry: the published tarball, a CycloneDX bill of
79
+ materials, and a build attestation"*.
80
+ - Mechanism: `publish.yml` produces the SBOM only in `publish` mode and uploads
81
+ only the assets that exist.
82
+ - Why it falls short: no release carries all three. 0.2.33 carries two; 0.2.34
83
+ was not on npm when this was written.
84
+ - Disposition: narrowed to what the publish path is *configured* to produce, with
85
+ 0.2.33's actual contents named. The neighbouring *"stops one version short …
86
+ again"* was in the present tense for a past event and is now *"had stopped"*.
87
+ - **Found by: Codex.**
88
+
89
+ ### 5. docs/security/NPM-PROVENANCE.md — an artefact described before it existed
90
+
91
+ - Claim: *"From 0.2.34 the publish workflow attaches three files to the GitHub
92
+ release"*, over a table of them.
93
+ - Mechanism: the steps added in #28, which had never executed.
94
+ - Why it falls short: it described an intention as an artefact — the defect
95
+ 0.2.33 was published to fix, with the sign reversed.
96
+ - Disposition: reworded in `d816ce1`, then superseded by finding 3 once the steps
97
+ actually ran.
98
+ - **Found by: the first pass**, which is recorded here mainly to be honest about
99
+ its hit rate: it caught the claim it had just written, and missed the two that
100
+ came from reading someone else's code and re-reading its own file.
101
+
102
+ ### 6. docs/PRIOR-ART.md — a competitor's mechanism overstated
103
+
104
+ - Claim: the Microsoft row read *"Ed25519, **Merkle-chained**"*.
105
+ - Mechanism: their own tutorial, which describes a linear `parent_receipt_hash`.
106
+ - Why it falls short: it is wrong, and wrong in their favour. A comparison table
107
+ that inflates a competitor is no more trustworthy than one that inflates its
108
+ author; both mean the rows were not checked.
109
+ - Disposition: corrected in `0198ccf`, with the previous wording named.
110
+ - **Found by: Cursor.**
111
+
112
+ ## Verification note
113
+
114
+ Vaara's contiguity tests were run during the first pass —
115
+ `PYTHONPATH=src python -m pytest tests/credential/test_contiguity.py` → 18
116
+ passed, at `befdced`. Codex could not reproduce that (`rfc8785` missing, no
117
+ package import environment) and correctly flagged that the claim had no command
118
+ recorded against it. The command and result are now in `docs/PRIOR-ART.md` beside
119
+ the claim rather than only in a session transcript.
@@ -0,0 +1,65 @@
1
+ # Claims review — 0.2.35
2
+
3
+ - base: v0.2.34
4
+ - head: ee31d7b
5
+ - surface: sha256:ad95f3ab81fa4cd74ce025a76e3cc9095ecbc5bfefaace3eec763e809eb7d02b
6
+ - verdict: pass
7
+ - reviewer: Claude (Opus 5)
8
+
9
+ Two surfaces changed: `README.md` and `docs/security/NPM-PROVENANCE.md`. Both
10
+ changes are corrections of claims that this project's own actions falsified
11
+ within hours, which is the pattern worth recording more than the diff.
12
+
13
+ ## Findings
14
+
15
+ ### 1. docs/security/NPM-PROVENANCE.md — corrected, and the correction is the release
16
+
17
+ - Claim, as of 0.2.34: *"The full path, producing all three, has not run yet."*
18
+ - Mechanism: the workflow runs and the release pages.
19
+ - Why it fell short: it was true when written and false a few hours later,
20
+ because publishing 0.2.34 ran that path. Verified from the destination: run
21
+ `32298849184` completed every step including the bill of materials; the
22
+ `v0.2.34` release page carries `conarium-ai-core-0.2.34.tgz` (764,893 bytes),
23
+ `.cdx.json` (70,245) and `.tgz.intoto.jsonl` (11,032); the tarball's sha512
24
+ matches the registry's `dist.integrity`; `gh attestation verify` returns 0.
25
+ - Disposition: rewritten to separate the two histories — 0.2.33 has two assets
26
+ because its artefacts came from the mode that skips the SBOM, 0.2.34 has three
27
+ — and to end by pointing at the release page rather than at itself. That is
28
+ the only form of the sentence with no expiry date.
29
+ - Note on the class: this is the second time in two releases that a sentence
30
+ about what *has not happened yet* went stale. The first was caught by an
31
+ external reviewer, this one by knowing to look. A statement of that shape
32
+ should carry the thing that answers it, not the answer.
33
+
34
+ ### 2. README.md — a badge, and what it is not, in the same paragraph
35
+
36
+ - Claim: the OpenSSF Best Practices badge is displayed in the badge row.
37
+ - Mechanism: `bestpractices.dev` project 14160 — a **self-certification**
38
+ questionnaire, not an assessment by anyone else.
39
+ - Why it could fall short: a badge in a row of badges reads as certification. The
40
+ Scorecard badge beside it is machine-measured; this one is us answering 67
41
+ questions about ourselves.
42
+ - Disposition: added with the qualification attached rather than in a footnote —
43
+ self-certification not an audit, answers public and falsifiable at project
44
+ 14160, 3 of 67 marked not applicable with reasons, and the neighbouring
45
+ Scorecard `Code-Review` score of 0 named in the same paragraph. Accepted.
46
+
47
+ ### 3. The badge answers themselves — one corrected before submission
48
+
49
+ - Claim: the `test_most` criterion was first answered by asserting the test suite
50
+ covers most of the code.
51
+ - Mechanism: a coverage measurement.
52
+ - Why it fell short: coverage is not reported as a percentage in this project,
53
+ so the assertion had nothing behind it. It was an easy sentence to write and
54
+ nobody outside would have checked it.
55
+ - Disposition: rewritten before the form was submitted to describe what is
56
+ exercised — the policy gate, masking, the receipt chain and verifier, the
57
+ reconciliation tool, every documented CLI surface, and the documented quickstart
58
+ on three Node majors — and to say the ratio is not measured. Recorded here
59
+ because the badge answers are a claim surface that lives outside this
60
+ repository and no gate here can see them.
61
+
62
+ ## What did not change
63
+
64
+ The engine, the receipt format, the policy gate, the reconciliation tool and the
65
+ conformance vectors are untouched. `run-checks` and the suite pass unchanged.
@@ -57,6 +57,55 @@ two commands above.
57
57
  If a version has **no** attestation, it was not published through this workflow
58
58
  (or predates it). Treat that as undeclared origin — not as "verified".
59
59
 
60
+ ## What a release page carries
61
+
62
+ The publish workflow is configured to attach three files to the GitHub release.
63
+ Which of them a given version actually carries is answered by its release page,
64
+ not by this table:
65
+
66
+ | Asset | What it is |
67
+ |---|---|
68
+ | `conarium-ai-core-<version>.tgz` | the published tarball, **downloaded from the registry**, not rebuilt |
69
+ | `conarium-ai-core-<version>.cdx.json` | CycloneDX bill of materials, read from the lockfile the release was built against |
70
+ | `conarium-ai-core-<version>.tgz.intoto.jsonl` | a build attestation over that tarball, also written to GitHub's attestation store |
71
+
72
+ The tarball is fetched rather than packed again on purpose. `npm pack` is not
73
+ byte-reproducible across environments — file modes, line endings and the gzip
74
+ implementation differ — so a rebuilt asset can be a lookalike of the release
75
+ rather than the release. Its sha512 is checked against the registry's
76
+ `dist.integrity` before anything is attested or uploaded.
77
+
78
+ **What has actually run.** The artefact path first executed on 19 August 2026 in
79
+ the workflow's `artefacts` mode — a dispatch that attaches files to a version
80
+ already on npm and skips publishing, tagging and the registry entirely. It was
81
+ run against **0.2.33**, whose release page had been left empty when that version
82
+ shipped. So **0.2.33 carries the tarball and the attestation and no bill of
83
+ materials**: that step is skipped in artefacts mode, because the lockfile in the
84
+ tree belongs to a later version.
85
+
86
+ The full path, producing all three, first ran for **0.2.34** later the same day.
87
+ Its release page carries the tarball, the CycloneDX bill of materials and the
88
+ attestation, and the tarball's sha512 matches the registry's `dist.integrity`.
89
+
90
+ Which means the table above describes two different histories depending on the
91
+ version you are holding, and the release page — not this document — is what
92
+ answers for any particular one.
93
+
94
+ ⛔ **The `gh` command below works only for versions whose release page actually
95
+ carries the `.intoto.jsonl` asset** — check the page, do not assume from the
96
+ version number. That attestation is a second one, written to GitHub's store; it
97
+ does not replace npm's. For a version without it, the 404 explanation above still
98
+ applies.
99
+
100
+ ```bash
101
+ # only for a version whose release page lists the .intoto.jsonl asset
102
+ gh attestation verify conarium-ai-core-<version>.tgz --repo dogrucanemek-alt/conarium
103
+ ```
104
+
105
+ Two attestations over the same bytes are not redundancy for its own sake: one is
106
+ checkable without GitHub, the other without npm, and the bill of materials is
107
+ checkable without either.
108
+
60
109
  ## Publisher configuration
61
110
 
62
111
  Auth is **npm Trusted Publishing (OIDC)**, not a stored token. npm hands the
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@conarium-ai/core",
3
- "version": "0.2.33",
3
+ "version": "0.2.35",
4
4
  "mcpName": "io.github.dogrucanemek-alt/conarium",
5
5
  "//files-artefakt": "examples/ altindaki uretilmis dosyalar (ozel anahtar, makbuz/denetim JSONL) ELENIR. .gitignore npm'i baglamaz: izin listesinde 'examples' oldugu icin demoyu kosturmus bir makinede 'npm publish' _keys/audit-ed25519.pem'i (OZEL ANAHTAR) ve makbuzlari yayinliyordu. test/pack_artefakt.mjs bunu kilitler. Elemeler examples/ ile SINIRLI: test-vectors/ altindaki receipts.jsonl ve .pub.pem YAYINLANMAK ZORUNDA, yoksa ucuncu taraf konformans vektorlerini kosturamaz.",
6
6
  "//files": "Pakete NE gireceginin izin listesi. Liste olmadan npm her seyi gonderiyordu: 296 dosya / 1.5 MB — CI workflowlari, gitleaks ayari, 137 KB pazarlama gorseli, sitenin api/chat.js dosyasi. Bir bankanin guvenlik ekibi tarball'i acip bunlari gorur. scripts/ BILEREK var: conarium-reconcile calisirken scripts/pg-snapshot.sql'e atif yapiyor, olmazsa kullanici destek maili yazar.",