@conarium-ai/core 0.3.8 → 0.3.9

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,17 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.3.9 - a boundary item over the bound either way is observed-without-receipt
4
+
5
+ When a boundary item's `exceededIfAdmitted` is `true`, the item is over the
6
+ declared bound under either reading of the clock, so the clock does not decide
7
+ it. Following draft-08, `/2` reports it as `observed-without-receipt` with
8
+ reason `multiplicity-exceeded`, the offset and the bound, where draft-07
9
+ required `indeterminate`. Issue #101 reported the case: 10,000 statements
10
+ against one Receipt, a bound of 1, one `indeterminate` item. Thanks to
11
+ giskard09 for the report. `/1` still exits 41 for it, and without a declared
12
+ bound no item leaves `indeterminate` this way. The conformance case
13
+ `v2-window-boundary-bound-exceeded` now expects `observed-without-receipt`.
14
+
3
15
  ## 0.3.8 - the patterns beside a join that a Receipt names in part are decided together
4
16
 
5
17
  0.3.7 said its comparison errs toward `indeterminate` for a pattern over
package/LIMITATIONS.md CHANGED
@@ -348,8 +348,11 @@ because this tool has no way to know which of the two happened. That is a
348
348
  limit, not a verdict: 41 is a failure and the run does not pass, but nothing
349
349
  is proven either way. Under a declared bound the `/2` item says whether the
350
350
  statement count exceeds it even if every receipt naming its objects were
351
- admitted (`multiplicity.exceededIfAdmitted`). The outcome does not change: the
352
- item stays `indeterminate`, and `false` is not a pass.
351
+ admitted (`multiplicity.exceededIfAdmitted`). When it does, both readings of the
352
+ clock give the same answer, so the clock does not decide the item: `/2` reports
353
+ it as `observed-without-receipt` with reason `multiplicity-exceeded`, the offset
354
+ and the bound (draft-08). The `/1` result and exit 41 do not change. When it
355
+ does not, the item stays `indeterminate`, and `false` is not a pass.
353
356
 
354
357
  The exculpation is bounded by the window's own length — an offset larger than
355
358
  the window cannot be a boundary artefact, and the report says so instead of
package/LIMITATIONS.tr.md CHANGED
@@ -364,8 +364,11 @@ kapsayacak olan makbuz pencerenin dışına düşerse sonuç `indeterminate` olu
364
364
  bilemez. Bu bir hüküm değil, bir sınır: 41 başarısızlıktır, koşu geçmez, ama
365
365
  hiçbir yön kanıtlanmış olmaz. Sınır beyan edilmişse `/2` kalemi, nesnelerini
366
366
  adlandıran her makbuz kabul edilse bile ifade sayısının sınırı aşıp aşmadığını yazar
367
- (`multiplicity.exceededIfAdmitted`). Sonuç değişmez, kalem yine `indeterminate`
368
- kalır; `false` değeri de geçti anlamına gelmez.
367
+ (`multiplicity.exceededIfAdmitted`). Aşıyorsa saatin iki okuması da aynı sonucu
368
+ verir, yani kalemi saat belirlemez: `/2` onu `observed-without-receipt` olarak,
369
+ `multiplicity-exceeded` gerekçesi, fark ve sınırla raporlar (draft-08). `/1`
370
+ sonucu ve 41 çıkış kodu değişmez. Aşmıyorsa kalem `indeterminate` kalır;
371
+ `false` değeri de geçti anlamına gelmez.
369
372
 
370
373
  Aklama, pencerenin kendi uzunluğuyla sınırlı: pencereden uzun bir fark sınır
371
374
  etkisiyle açıklanamaz ve rapor bunu mazeret göstermek yerine açıkça yazar.
@@ -898,17 +898,31 @@ export function projectResultV2(result, ctx) {
898
898
  throw new Error('projectResultV2: the result carries no receipt counts; pass the value reconcile() returned')
899
899
  }
900
900
 
901
- // The temporal rule keeps a boundary item indeterminate whatever its size, so
902
- // the outcome alone shows 1 statement and 10,000 as the same finding. The item
903
- // carries the objects and, under a declared bound, what admitting every
904
- // Receipt that names them would and would not settle.
901
+ // The temporal rule keeps a boundary item indeterminate, because the clock
902
+ // decides it. Under a declared bound, an item whose count exceeds the bound
903
+ // even with every Receipt naming its objects admitted is over it under either
904
+ // reading of the clock, so the clock does not decide it: draft-08 makes it
905
+ // observed-without-receipt and requires the offset and the bound on the item
906
+ // (#101). Otherwise the item carries what admitting those Receipts would and
907
+ // would not settle.
905
908
  for (const d of result.indeterminate) {
909
+ const multiplicity = max != null ? boundaryMultiplicity(d, naming, max) : null
910
+ if (multiplicity?.exceededIfAdmitted) {
911
+ push('observed-without-receipt', {
912
+ pattern: patternDigest(d.query),
913
+ reason: 'multiplicity-exceeded',
914
+ requiredSkewMs: d.requiredSkewMs,
915
+ objects: d.uncoveredTables,
916
+ multiplicity,
917
+ })
918
+ continue
919
+ }
906
920
  push('indeterminate', {
907
921
  pattern: patternDigest(d.query),
908
922
  reason: 'window-boundary',
909
923
  requiredSkewMs: d.requiredSkewMs,
910
924
  objects: d.uncoveredTables,
911
- ...(max != null ? { multiplicity: boundaryMultiplicity(d, naming, max) } : {}),
925
+ ...(multiplicity ? { multiplicity } : {}),
912
926
  })
913
927
  }
914
928
 
@@ -1186,7 +1200,8 @@ async function main(argv = process.argv.slice(2)) {
1186
1200
  const m = boundaryMultiplicity(d, result.namingReceipts, max)
1187
1201
  return m.exceededIfAdmitted
1188
1202
  ? `\n ${d.delta} statements exceed the declared multiplicity bound of ${max} even if all ` +
1189
- `${m.receipts} receipt(s) naming ${m.object} are admitted`
1203
+ `${m.receipts} receipt(s) naming ${m.object} are admitted, so the clock does not decide it: ` +
1204
+ '/2 reports it as observed-without-receipt'
1190
1205
  : ''
1191
1206
  }
1192
1207
  const line = (d) =>
@@ -9,9 +9,9 @@
9
9
  "receipts": "conformance/fixtures/reconciliation/receipts-customers-early.jsonl",
10
10
  "mappingProfile": "conformance/fixtures/reconciliation/profile-multiplicity-1.json",
11
11
  "expectOutcome": "exceptions",
12
- "expectItemOutcomes": ["indeterminate"],
13
- "forbidItemOutcomes": ["matched", "observed-without-receipt"],
14
- "expectItemFields": { "reason": "window-boundary", "multiplicity": { "bound": 1, "object": "customers", "receipts": 1, "statements": 5, "exceededIfAdmitted": true } },
15
- "rationale": "An item uncovered only by the window boundary stays indeterminate under the temporal rule of the draft, and it reports that its statement count exceeds the declared bound even if every Receipt naming its objects were admitted. The outcome alone would present 5 statements and 10,000 statements as the same finding.",
12
+ "expectItemOutcomes": ["observed-without-receipt"],
13
+ "forbidItemOutcomes": ["matched", "indeterminate"],
14
+ "expectItemFields": { "reason": "multiplicity-exceeded", "requiredSkewMs": 3000, "multiplicity": { "bound": 1, "object": "customers", "receipts": 1, "statements": 5, "exceededIfAdmitted": true } },
15
+ "rationale": "The only Receipt naming the object falls outside the Window, and the statement count exceeds the declared bound even with that Receipt admitted. Under either reading of the clock the item is observed-without-receipt, so the clock does not decide it and the temporal rule does not keep it indeterminate. The item carries the offset and the bound.",
16
16
  "doesNotTest": "Whether the Receipt belongs to the recorded access."
17
17
  }
@@ -634,8 +634,13 @@ carries `multiplicity: { bound, object, receipts, statements, exceededIfAdmitted
634
634
  Receipts with a readable timestamp that name `object`, inside the Window or out,
635
635
  and `object` the one of the pattern's objects with the fewest such Receipts.
636
636
  `exceededIfAdmitted` is `statements > receipts × bound`: the count exceeds the
637
- bound even with every Receipt naming the object admitted. The item stays
638
- `indeterminate` either way, and `false` is not a pass.
637
+ bound even with every Receipt naming the object admitted. When it is `true`,
638
+ both readings of the clock give the same answer, and the item is
639
+ `observed-without-receipt` with reason `multiplicity-exceeded` instead of
640
+ `window-boundary`, carrying the same `requiredSkewMs`, `objects` and
641
+ `multiplicity` (draft-08). When it is `false`, the item stays `indeterminate`,
642
+ and `false` is not a pass. Without a declared bound no item leaves
643
+ `indeterminate` this way.
639
644
 
640
645
  ### Mapping Profile (`conarium-mapping-profile/0.1`)
641
646
 
@@ -0,0 +1,92 @@
1
+ # Claims review — 0.3.9
2
+
3
+ - base: v0.3.8
4
+ - head: 22a48b2
5
+ - surface: sha256:685117adaebe702f949bcbe187d7f0e2067d70704dd5b31ac14bc13cff53c55f
6
+ - verdict: pass
7
+ - reviewer: Claude. Three claim surfaces changed between v0.3.8 and HEAD:
8
+ `LIMITATIONS.md`, `LIMITATIONS.tr.md` and `docs/RECEIPT-SPEC.md`
9
+ (`node test/denetci.mjs input v0.3.8 HEAD`).
10
+
11
+ The release changes `projectResultV2` in `bin/conarium-reconcile.mjs`: a
12
+ boundary item whose `multiplicity.exceededIfAdmitted` is `true` is reported as
13
+ `observed-without-receipt` with reason `multiplicity-exceeded` instead of
14
+ `indeterminate` with reason `window-boundary`, and the text report says so. It
15
+ changes one conformance case and two tests in `test/reconcile_cli.test.mjs`,
16
+ adds two there, and moves the version test in `src/demo-mode.test.ts`.
17
+
18
+ Each new sentence was set against what establishes it. "Seen failing" means
19
+ the test went red when the code it names was changed, and green again when it
20
+ was restored.
21
+
22
+ - "When it does, both readings of the clock give the same answer, so the clock
23
+ does not decide the item": `exceededIfAdmitted` counts every Receipt with a
24
+ readable timestamp that names the object, inside the Window or out, so an
25
+ item over the bound with all of them admitted is over it with any subset
26
+ admitted. `10,000 statements against one bound of 1 are
27
+ observed-without-receipt with the offset and the bound` (offset 3 s) and `a
28
+ beyond-window offset over the bound is observed-without-receipt too` (offset
29
+ 25 h) read the outcome. Both seen failing with the new branch in
30
+ `projectResultV2` disabled, and so does
31
+ `conformance/cases/reconciliation/v2-window-boundary-bound-exceeded.json`
32
+ (PASS before, FAIL with the branch disabled).
33
+ - "`/2` reports it as `observed-without-receipt` with reason
34
+ `multiplicity-exceeded`, the offset and the bound (draft-08)": the first test
35
+ above reads `outcome`, `reason`, `requiredSkewMs: 3000`, `objects` and
36
+ `multiplicity: { bound: 1, object, receipts: 1, statements: 10000,
37
+ exceededIfAdmitted: true }`; the conformance case requires `reason`,
38
+ `requiredSkewMs` and `multiplicity`, not `objects`.
39
+ draft-dogru-scitt-disclosure-evidence-08, Section 4.3, as published on the
40
+ Datatracker: boundary items are indeterminate "unless they exceed a declared
41
+ multiplicity bound under either reading of the clock", and a reconciler
42
+ "MUST report which bound it applied". See finding 1.
43
+ - "The `/1` result and exit 41 do not change": the first test reads exit 41.
44
+ No test reads the `/1` body for this case; see finding 2.
45
+ - "When it does not, the item stays `indeterminate`, and `false` is not a
46
+ pass": `a single statement against the same bound is a different item` and
47
+ `every receipt naming the object counts when the item asks what admitting
48
+ them would settle` read `indeterminate` with `exceededIfAdmitted: false`;
49
+ `the text report still does not call a bound that holds unreceipted` reads
50
+ the text.
51
+ - `docs/RECEIPT-SPEC.md` "carrying the same `requiredSkewMs`, `objects` and
52
+ `multiplicity`": the first test above reads all three on the
53
+ `observed-without-receipt` item.
54
+ - `docs/RECEIPT-SPEC.md` "Without a declared bound no item leaves
55
+ `indeterminate` this way": `without a declared bound the item states no
56
+ multiplicity comparison` reads reason `window-boundary` and no
57
+ `multiplicity` with 10,000 statements; the branch is guarded by `max != null`.
58
+ - Text report: `the text report names the exceeded bound and says what /2
59
+ reports`. Seen failing with the added clause removed from the message.
60
+ - `LIMITATIONS.tr.md` says the same as `LIMITATIONS.md`, sentence for
61
+ sentence.
62
+
63
+ ## Findings
64
+
65
+ ### 1. LIMITATIONS.md, docs/RECEIPT-SPEC.md — "(draft-08)" while the repository carries -07
66
+
67
+ - Claim: "`/2` reports it as `observed-without-receipt` with reason
68
+ `multiplicity-exceeded`, the offset and the bound (draft-08)" (also in
69
+ `LIMITATIONS.tr.md` and `docs/RECEIPT-SPEC.md`).
70
+ - Mechanism: the published -08 text, Section 4.3.
71
+ - Why it falls short: `standards/` in this tree holds
72
+ `draft-dogru-scitt-disclosure-evidence-07.md`, which requires `indeterminate`
73
+ for this item. A reader who follows the citation inside the repository finds
74
+ the opposite rule until the -08 text is added. The -08 citation itself is
75
+ correct: the Datatracker copy states the rule, and its Implementation Status
76
+ names 0.3.7 as not implementing it.
77
+ - Disposition: accepted; the -08 text goes into `standards/` in its own pull
78
+ request.
79
+
80
+ ### 2. LIMITATIONS.md — "The `/1` result and exit 41 do not change"
81
+
82
+ - Claim: "The `/1` result and exit 41 do not change."
83
+ - Mechanism: the change is confined to `projectResultV2`, which builds the
84
+ `/2` body, and one line of the text report.
85
+ - Why it falls short: no test reads the `/1` body of this case, only its exit
86
+ code. Measured instead: the case's fixtures (`before-customers-10.json`,
87
+ `after-customers-15.json`, `receipts-customers-early.jsonl`,
88
+ `profile-multiplicity-1.json`) through the published 0.3.8 package and
89
+ through HEAD give byte-identical `--json` output, exit 41 for both, while
90
+ `--json-v2` moves the item from `indeterminate`/`window-boundary` to
91
+ `observed-without-receipt`/`multiplicity-exceeded`.
92
+ - Disposition: accepted, with the measurement stated here.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@conarium-ai/core",
3
- "version": "0.3.8",
3
+ "version": "0.3.9",
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.",