# Claims review — 0.2.27

- base: v0.2.26
- head: cb4d2ee
- surface: sha256:0968a0b4fdbed3966bd1d7afd4490495fc2efef68056a69e8530ff6e26bf459b
- verdict: pass
- reviewer: Claude (release review before publish)

Two claim surfaces changed: `docs/RECEIPT-SPEC.md` gained the exit-41 row and a
section describing it, and `docs/API-STABILITY.md` gained `--skew` in the
`conarium-reconcile` flag list. The flag list matches the parser. The finding is
in the new section, and it is the same shape as the defect the release fixes:
prose implying a limit the mechanism does not enforce.

## Findings

### 1. docs/RECEIPT-SPEC.md — "a receipt just outside the boundary" described a proximity the default mode does not enforce

- Claim: "A pattern whose uncovered tables **all** have a receipt just outside the boundary is reported as `indeterminate` and exits 41", followed by "Without the flag nothing decides the question, so nothing is asserted."
- Mechanism: `reconcile()` moves a pattern to `indeterminate` when every uncovered table appears in `outsideBoundaryCoverage()` and, if `--skew` was given, the largest offset is within it. When `--skew` is absent there is no bound at all, so the offset is recorded and never compared.
- Why it falls short: without a declared bound there is no "just". Measured on the CLI against the same fixture, a receipt six hours outside the window produces `21600000ms outside` and exit 41, exactly as a three-second one produces `3000ms outside` and exit 41. A reader would take the sentence to mean a distant receipt still yields 40, and it does not. The second sentence has the opposite error, claiming less than the tool does: it does classify, into a weaker class.
- Disposition: reworded in `cb4d2ee`. The section now says distance is reported and not judged until a bound is declared, that any covering receipt outside the window lands at 41 in the default mode, and that reading the number is the operator's job there.