Verification — Eclipse Exportcheck

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-exportcheck.md (Verity bench of v0.1.0, PASS-CONDITIONAL (local/fixture), defects D1/D2, conditions C1-C3) + fix records wave4/fix-exportcheck-011..021 + spot re-benches wave4/spot-exportcheck-012..022 closing at spot-exportcheck-022.md (Verity spot re-bench round 6 of v0.1.7 @5b0ab96: D3 CLOSED, survivors-in-claim 0, determinism 55/55, C4 discharged, final product verdict PASS-CONDITIONAL (local/fixture) (spot-022 verdict: PASS, scoped to the D3/C4 condition only; the C3 rollback fence is undischarged and caps the product verdict at PASS-CONDITIONAL (local/fixture) until an external anchor exists)). 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/fixture)

Certified scope: Eclipse Exportcheck — PASS-CONDITIONAL (local/fixture) — Verity bench of v0.1.0 (2026-10-27, argus101-program-20261027/wave4/bench-exportcheck.md: PASS-CONDITIONAL (local/fixture), defects D1/D2, conditions C1-C3) + collision-screen fix rounds and spot re-benches rounds 1-6 closing at wave4/spot-exportcheck-022.md (v0.1.7 @5b0ab96: D3 CLOSED, survivors-in-claim 0 forms / 0 glyphs over an exhaustive 2,749-glyph / 9,836-form sweep, determinism 55/55 processes one digest, invariance byte-identical vs v0.1.2, C4 DISCHARGED) — final product verdict PASS-CONDITIONAL (local/fixture) (spot-022 verdict: PASS, scoped to the D3/C4 condition only; the C3 rollback fence is undischarged and caps the product verdict at PASS-CONDITIONAL (local/fixture) until an external anchor exists). PASS-CONDITIONAL (local/fixture) is not CERTIFIED — certified is false, and nothing beyond that verdict at its exact scope is claimed. Scope is exactly: local stdio, fixture parties against invented fixture snapshots only, value_class "test"; no real list is loaded, fetched, or reproduced, no real party is screened, and no verdict is relied on for anything. Collision screening (local/fixture scope): fixture sets loaded into Eclipse Exportcheck are collision-screened against symbol-, format- and homoglyph-decorated forms of listed names under SPEC Q-E3 as amended at v0.1.7 — assignment, identity and transmitted readings as there defined (bench: spot-exportcheck-022, survivors-in-claim 0). Standing disclosure: fixture sets are invented test data; a fixture CLEAR states only that this invented party record did not match this invented snapshot under this sealed rule-set version, as recomputed by spec 6.3 — it authorises no shipment, transaction, or filing. No live claim is made; no certification is claimed beyond the stated local/fixture bench scope. Standing conditions: C2 (from bench deviation 2): party_screen never links (prior_verdict_id: null) — a repeat party_screen under a newer snapshot produces an unlinked but immutable, vintage-sealed verdict; chain claims rest on verdict_rescreen + pack chain receipts only, and no listing or doc may imply party_screen chains. C3 (rollback fence, builder-stated, bencher-confirmed): verdict caps at PASS-CONDITIONAL(local/fixture) until an external anchor exists; pure local file store + signed head/SET anchors only. No test-bench scorecard was issued for this verdict and none is claimed (card_url null).

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

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