Verification — Eclipse Fairlend

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-fairlend.md (Verity bench of v0.1.0, PASS-CONDITIONAL (local/fixture), defects D-1..D-10) + argus101-program-20261027/wave4/rebench-fairlend.md (Verity delta re-bench of v0.1.1 fix commit 01cceda: D-1..D-6, D-8, D-9, D-10 CLOSED, D-7 partially closed with residual D-11 named, builder suite 36/36 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/fixture)

Certified scope: Eclipse Fairlend — PASS-CONDITIONAL (local/fixture) — Verity bench of v0.1.0 (2026-10-27, argus101-program-20261027/wave4/bench-fairlend.md) + delta re-bench of v0.1.1 (argus101-program-20261027/wave4/rebench-fairlend.md: D-1..D-6, D-8, D-9, D-10 CLOSED; D-7 closed for its probed class with residual Low defect D-11 NAMED; builder suite 36/36 reproduced). 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 decisions only, synthetic cohorts; no real applicant, no real credit data, no real model, and no lender system is touched, and Fairlend makes no credit decision and influences none. A Fairlend seal proves what was recorded at decision time — the presented feature set, model version, and reason codes, counter-signed then; it does not prove the decision was fair, lawful, unbiased, or correct. Standing condition D-11 (NAMED): the SPEC §7.3 identifier fence is still evadable by token-split spellings (tax_id, ein, gov_id, surname, home_street etc. seal today when they should refuse); D-11 must close before any non-fixture scope. Rollback fence and the SPEC §10 fair-lending 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

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