The coverage declaration

Suite version

Under AEF 1201 C10 the suite version is the digest of the coverage declaration as served, which the file cannot contain and this page computes from the same bytes it links:

sha-256:18d0d14f4a34e724b1d84b92027cbf0b823cf0a587b31ec3cf49b8f3ec25768c

Suite sources: packages/aef/test-suite-pins.ts at sha-256:acd1a0fc3ae17e19…; packages/aef/test.ts at sha-256:728c1769a3c95bb6…. Additional documents applied: 1300/0.2, 1300/0.1, 1201/0.1, 1301/0.1, 1400/0.1. Previous suite version: sha-256:f851528b8d6e7e3a….

Self-test subset (carried by the verifier, AEF 1201 C19): sha-256:a7385e2738bec6ce…. One required-to-fail fixture per fatal-capable check, per C19. The deployed verifier runs the subset before its first result in each configuration, refuses on mismatch per C20, and records the digest and outcome on every result per C21. A pass means the verifier agrees with its own pinned history in that configuration, and nothing more.

The suite's sixth version, and the first in which every fixture is a pinned pair as AEF 1201 C5 defines one: inputs comprise the record, the declaration, any supplied acceptance, renewals, or deprecations, the trust base statement, and the options, with the verification time pinned and artifact roots pointing at snapshots rather than the live repository. The hand-written tests in packages/aef/test.ts remain as a generated layer, labeled below, exercising the same behaviors with regenerated inputs; per C5's own text they discharge no C-requirement and are retained for redundancy. The suite version under C10 is the sha-256 digest of this file as served, which this file cannot contain.

The entries

Requirement coverage: 54 requirements of 1200/0.2

Asserted (36)

V2, V4, V5, V6, V7, V8, V9, V10, V14, V15, V16, V18, V19, V21, V24, V26, V27, V29, V30, V31, V35, V36, V37, V41, V42, V43, V44, V45, V46, V47, V48, V49, V51, V52, V53, V54

Asserted in part (5)

Occurs unasserted (5)

The condition arises on every suite run and no test asserts it. A verifier that silently stopped satisfying any of these would still pass the suite.

V3, V17, V20, V23, V28

Never arises (3)

V32, V33, and V34 await re-verification comparison against an earlier result, which the verifier does not implement; no fixture can produce the condition.

V32, V33, V34

Not fixture-checkable (4)

Per AEF 1200 section 14: V12, V38, and V39 are checked by inspecting the verifier, and V40 is the document's one requirement on judgment.

V12, V38, V39, V40

Scoped unproducible (1)

V22 v0.2 scopes ORDER-UNCHAINED to record forms that do not require chaining, of which none exist, per resolution-0001; the condition is unproducible by any conformant input until such a form does.

V22

Required to fail, and isolation

Counting pinned fixtures only, per C5.

Every check that can fail has a failing fixture. Checks that cannot fail by construction: key-binding, anchor-ordering, algorithm-standing. These checks report and decide nothing: their status vocabulary contains no failed state, so C7's obligation, which binds every check that can fail, does not arise for them.

All 15 fatal-capable checks have isolating fixtures. An isolating fixture fails exactly its check and no other fatal check, asserted by exact fatal-failure-set comparison.

Every pinned fixture pins its complete expected qualification set by registry class, its exact fatal and non-fatal failure sets, its outcome, and its first failing check (C6).

Retired expectations (5)

Under AEF 1201 C12 a retirement keeps the entry's identity and records why the pinned expectation no longer binds:

The suite's own standing

The declaration records 0 failures against AEF 1201's requirements. The list is empty for the first time, and emptiness means exactly this: no requirement of AEF 1201 that binds this suite, this coverage declaration, or this verifier's self-test is known to be unmet. It is not a statement of suite adequacy, which AEF 1201 section 4 states cannot be established, and the reference-implementation gaps against AEF 1200 itself are listed inside the conformance claim, where C1 puts them. The conformance claim's standing:

Conformance claim 0001 is published at /aef/conformance-claim-0001.json, per C1 through C4: partial, with the requirements still failed or unexercised listed inside it.