Checkable Sets
Registry continuity, settlement arithmetic, and batch inclusion
The problem
Batch systems are vulnerable to quiet changes in membership, order, totals, and continuity. A signed summary is weak if the signer also supplies the root, count, and outcome without independent recomputation.
These profiles reject caller supplied derived fields. Registry adds status transitions, settlement adds integer minor unit arithmetic, and voting adds manifest timing plus commitment inclusion.
Primitive map
| Receipt | Bound inputs | Derived relation | Claim boundary |
|---|---|---|---|
receipt.registry.sovereign | Unique entries, prior checkpoint, statuses, and jurisdiction metadata | Root, count, and allowed transitions recompute | Government authority or legal effect |
settlement.feed | Unique settlement entries, prior checkpoint, and minor unit amounts | Root, count, continuity, and integer totals recompute | Funds moved, finality, or obligation validity |
voting.verifiable | Manifest, timing, ballot commitments, inclusion proofs, and optional tally | Root, count, inclusion, and supplied tally consistency recompute | Eligibility, secrecy, coercion resistance, authority, or legal validity |
Verifier gates
The verifier rebuilds derived values. It does not trust a caller supplied outcome, count, root, total, or relation.
- UNIQUE_ENTRIES
- CANONICAL_ROOT
- COUNT_RECOMPUTATION
- CHECKPOINT_CONTINUITY
- STATUS_TRANSITIONS
- INTEGER_ARITHMETIC
- MANIFEST_TIMING
- BALLOT_INCLUSION
- TALLY_CONSISTENCY
Failure cases
Duplicate entry
Canonical identity checks reject repeated members.
Root substitution
The verifier rebuilds the root from canonical leaves.
Count inflation
The verifier counts accepted entries.
Checkpoint fork
The new checkpoint must reference the expected prior root.
Total inflation
Settlement totals use integer minor units derived from entries.
Claim boundary
- Jurisdiction metadata does not grant registry authority.
- A settlement receipt does not prove that funds moved or became final.
- A voting receipt does not prove voter eligibility, secrecy, or freedom from coercion.
- No profile creates legal validity by itself.
Standards context
These sources describe related transparency, authorization, or evidence patterns. They do not endorse Hive or establish that a Hive receipt was present in any third party system.