Verification — Eclipse Ballotbox

No on-chain commitment exists for this verdict yet. The scorecard is the published record, and its digest below lets any copy be checked byte-for-byte against the file served here — a same-host check until per-verdict anchoring ships with Phase-1 D2.

What this proves — and what it doesn't. Byte-integrity proves this record is unaltered since publication. It does not by itself prove the tool is safe: safety rests on the test verdict's scope, what was not tested, and the tool's current operational status — the other dimensions shown on this page.

Issued by Verity (Cyan Eclipse Technologies) — a role-separated internal desk of the same company that publishes this catalog. Issuer relationship: first-party. The bench is not an external third-party evaluator.
No signing key is published for bench scorecards: verdicts are unsigned hosted records today. The only published key identity in the chain is the Eclipse Anchor attestation key, at batch level.

Availability

Catalog status: in-development

Distribution: MCP over stdio

Live-state note (from the catalog record): Bench evidence: argus101-program-20261027/wave4/bench-ballotbox.md (Verity bench of v0.1.0, PASS-CONDITIONAL (local/simulator), defects D1–D6, conditions C1–C6) + argus101-program-20261027/wave4/rebench-ballotbox.md (Verity delta re-bench of v0.1.1 fix commit 3475d7f: D1–D6 all CLOSED, C2 + C3 SATISFIED, builder suite 34/34 reproduced). No test-bench scorecard was issued for this verdict and none is claimed (scorecard_ref/card_url null).

Test verdict

Bench verdict: PASS-CONDITIONAL (local/simulator)

Certified scope: Eclipse Ballotbox — PASS-CONDITIONAL (local/simulator) — Verity bench of v0.1.0 (2026-10-27, argus101-program-20261027/wave4/bench-ballotbox.md) + delta re-bench of v0.1.1 (argus101-program-20261027/wave4/rebench-ballotbox.md: D1–D6 all CLOSED on independent evidence, conditions C2 and C3 SATISFIED, builder suite 34/34 reproduced). PASS-CONDITIONAL (local/simulator) is not CERTIFIED — certified is false, and nothing beyond that verdict at its exact scope is claimed. Scope is exactly: local stdio, fixture electorate + fixture governance mandates only, value_class "test"; no real person, company, union, public body, or live agent fleet votes in v0.1.1, no result binds anyone, and no real decision is taken here. The legitimacy limit binds verbatim: recompute proves tally-vs-sealed-ballots — that the published totals are exactly the function of the sealed ballots and their vote-time eligibility proofs; it does not prove electorate legitimacy (who chose the electorate, whether the mandate issuer was itself authorised, whether voters were coerced, or whether the question was fair), and Ballotbox claims none of them. Standing conditions: C1 (HMAC cap — no public/RS256/JWS claim until real Herald signing), C4 (§10 counsel gate, named and unbuilt — any real binding election), C5 (metering-only pricing), C6 (rollback fence) still bind.

Lifecycle status of this verdict record: current

Publication integrity

No scorecard is published for this listing, so no digest exists.

Anchor state: NOT_ANCHORED

No receipt hash is linked to this record in the published records; verdict anchoring ships with Phase-1 D2 of the Eclipse Anchor program.

Network context — the one confirmed anchor batch does not cover this verdict: batch b18e97a2efad… attests sealed Herald receipts (hash-chain seq 1-4) · Base tx 0x6a69e35cbe70428f1fa97251759e2b5fa974bd422f68a076ac5de72c7b2459d4 · block 53163637 · attestation key 1adf4657a0c5684cebf52df1c8eea1b47d7778100b0a78862c7e84c6ddda19b7

A chain commitment, where present, commits to the digest of the record — it proves the record's bytes are unaltered since commitment. It does not commit to, or prove, the tool's behaviour or safety.

Operational status

Trust state: UNVERIFIED · Drift: UNKNOWN

Benched version: — · Latest seen: 0.1.1

Verify recipe

Cross-check the verdict and scope against this product's record in the append-only verdict feed (/verdicts.json) — corrections arrive only as superseding records.
On-chain: not yet available for this verdict — no receipt is linked to it in the published records (per-verdict anchoring arrives with Phase-1 D2). The scorecard and the verdict feed are the complete published record until then.

Downloads: verification.json · verdicts.json · trust-feed.json