Eclipse Duet

Bench verdict: PASS-CONDITIONAL(local, attested model-family declarations)

Certified scope: PASS-CONDITIONAL(local, attested model-family declarations) — Verity bench of v0.1.0 (2026-10-27, argus101-program-20261027/wave3/bench-duet.md) + D1 spot re-bench (wave3/rebench-duet.md, D1 CLOSED): builder suite 31/31 re-run clean by bencher at bench, 32/32 after the D1 fix (the +1 is the D1 regression test); decisive fixture F-D9 independently re-derived (bencher corpus, bencher keys, black-box stdio) — seal via stdio → SEALED with face families [orion, vega], fresh process with empty data dir from export + pinned keys alone → verified: true / SEALED, and the same-family control (signer B's identity record family edited to orion, attestation hash recomputed, record re-sealed under the bencher issuer key, refs re-derived) fails at DUET_VERIFY_FAIL:step2_check4_distinctness, UNVERIFIED_EXPORT, attestation_claim: null — the diversity leg is load-bearing; bencher battery 72 checks, 71 PASS at bench (sole failure = D1, closed on re-bench). PASS-CONDITIONAL is not CERTIFIED — certified is false. Scope is exactly: local stdio, fixture proposals, fixture agents and fixture identity records only, value_class 'test'; attestations only — Duet executes, authorizes, and approves nothing. Sole condition (verbatim): cross-artifact cross-commitment is fenced — external anchor required before live/multi-party use. Duet's diversity/independence proofs establish attested model families/providers and bound signatures — NOT actual running models, NOT non-collusion. Advisory O1/O2 (non-blocking): pairs carrying different family taxonomies seal (face surfaces each ref's own taxonomy; §2.4 includes no taxonomy-equality check — recorded for the live-identity phase), and signing is an HMAC fixture stand-in for Herald RS256 (disclosed).

Not tested:

• Actual running models / non-collusion — proofs cover attested declarations + bound signatures only: Duet's diversity/independence proofs establish attested model families/providers and bound signatures — NOT actual running models, NOT non-collusion. Duet never probes, fingerprints, or infers a signer's actual model; it does not establish that either agent actually runs the attested model, that the two agents share no operator, owner, prompt, tooling, training data, or incentive, that a diverse pair cannot collude through channels outside the signing act, or that the attested action is correct, safe, or compliant (SPEC §11.3). Never claimed for v0.1.0 are 'collusion-proof', 'fraud-proof', 'guaranteed independence', 'dual control compliant' (unqualified), or 'verified different models' (SPEC §11.4 strings named here only as never claimed)
• Sole condition (verbatim): cross-artifact cross-commitment is fenced — external anchor required before live/multi-party use. The export's anchor is the self-contained signed chain head; a superseded export still verifies offline after the store has advanced, so freshness / coordinated full rollback is undetectable without an external anchor — no live or multi-party use is licensed until that anchor exists and the build is re-benched
• Q-D3 ruling (bench, adopted, gates scope): a sealed attestation does NOT lapse when a signer's family attestation later lapses — currency (§2.4 check 2) is judged at signing time, so a sealed attestation proves the pair/diversity as at signing, within the proposal's face expiry, not continuing family attestation; later compromise is handled by revocation marking (F-D3), the only post-seal marking path — a sealed attestation's face changes to REVOCATION_MARKED while its sealed record_hash is unchanged, and a forged revocation is refused (REVOCATION_UNVERIFIED) and fails verify at step5_revocation
• Live reliance — SPEC §10 reliance gate (named, unbuilt): any use of a Duet attestation as a reliance/authorization control for regulated payments, fund movement, or other high-value/regulated actions sits behind the existing gates of the system that would rely on it (for payments, Till's existing FinTech Law counsel gate); no execution, authorization, approval, or reliance code exists, no dormant live path exists, and any live-identity or regulated-reliance phase is a separate, counsel-cleared, re-benched build — not a configuration change to v0.1
• Live identity — real Genesis/Continuity records, real agents, and real model families are not tested or claimed: fixture agents and fixture identity records only; Genesis/Continuity-style records are consumed by reference only, Duet issues, alters, and classifies nothing about them and defines no family taxonomy or equivalence mapping; startup fence refuses live keys, non-local endpoints, value_class other than 'test', and any model-probing or action-execution module (CONFIG_FENCE_REFUSED:<class>)
• Production signing — v0.1.0 signing is an HMAC fixture stand-in for Herald RS256 (HMAC Herald stand-in disclosure), disclosed on the product's face; verification uses keys pinned out-of-band in a local chmod-600 gitignored key file, never key material from the record under verification; a live phase requires real Herald signing and a re-bench
• Production key custody — fixture keys live in keys/fixture-keys.json (chmod 600, gitignored, never committed; GitHub contents/keys verified 404); a fresh clone generates its own fixture key file to run the full suite
• Hosted or live operation / charge path — local stdio only; metering points only per SPEC §9 (exactly 1 point per distinct signer pair per fixture month window with at least one sealed attestation, event duet_active_pair_month at the $99/mo price shape; 0 for all refusals and for verifies; idempotent second-signature re-presentation meters no second point); no charge, checkout, invoice, subscription, or payment-collection path is built and no live Meter ingest is claimed

Live state note: Bench evidence: argus101-program-20261027/wave3/bench-duet.md + wave3/rebench-duet.md (Verity bench + D1 spot re-bench of v0.1.0, 2026-10-27; builder suite re-run clean 31/31 at bench and 32/32 after the D1 fix, decisive F-D9 reproduced independently incl. fresh-process empty-data-dir verify and the same-family control, bencher battery 72 checks with sole failure D1 — closed on re-bench with the verbatim §11.3 sentence byte-exact on the attestation face and the verify-success result; sole condition C1 as stated, O1/O2 advisory only). No test-bench scorecard was issued for this verdict and none is claimed (scorecard_ref/card_url null).