Eclipse Bazaar · Eclipse Insurepack

Verification — Eclipse Insurepack

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-insurepack.md (Verity bench of v0.1.0, PASS-CONDITIONAL (local/simulator), DEFECT-1..3) + argus101-program-20261027/wave4/rebench-insurepack.md (Verity delta re-bench of v0.1.1 fix commit 440c3cc: DEFECT-1..3 all CLOSED, Condition 1 amended to Condition 1′, builder suite 28/28 reproduced, no new defect). 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 Insurepack — PASS-CONDITIONAL (local/simulator) — Verity bench of v0.1.0 (2026-10-27, argus101-program-20261027/wave4/bench-insurepack.md) + delta re-bench of v0.1.1 (argus101-program-20261027/wave4/rebench-insurepack.md: DEFECT-1..3 all CLOSED, Condition 1 amended to Condition 1′ by the bench, builder suite 28/28 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, evidence assembly over fixture verdict/incident/control records only, value_class "test"; no live API is built, no underwriter is served, no insurer system is touched, and no real insured, real incident, or real policy enters a pack. Load-bearing disclosure (SPEC §11.1): the evidence pack is insured-side disclosure tooling; underwriting reliance is the insurer's process, not Insurepack's claim. Amended Condition 1′ binds verbatim: a single-pack VERIFY_PASS attests the pack, its own transition, and the internal integrity of the presented stream; it must NOT be relied on as proof of completeness of transitions earlier than the pack's immediate predecessor (a fully re-signed, re-linked rewritten stream is indistinguishable there); full-history reliance requires per-pack chain verification (which the export transcript now performs) or an external anchor. Rollback fence and the SPEC §10 counsel gate (named, unbuilt) also 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

  1. 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.
  2. 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