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:f851528b8d6e7e3acbaf8a711b9e20450ae38c0534136bd4f786265797ac07b9

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

Produced with AEF 1201 v0.1 and extended in each session since. Under AEF 1201 C5, only entries whose inputs are retained byte-identical are fixtures; entries that regenerate their inputs each time the suite executes are generated tests and discharge no C-requirement. This is the suite's fourth version and the first to carry retirements: five expectations pinned under earlier documents were superseded by the AEF 1300 v0.2 and AEF 1200 v0.2 rulings, each retired with its reason below and re-pinned under the ruled expectation, per AEF 1201 C12. 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 (28)

V2, V5, V6, V7, V8, V9, V10, V14, V15, V19, V21, V24, V26, V27, V29, V35, V36, V42, V43, V44, V45, V46, V47, V48, V49, V51, V52, V53

Asserted in part (9)

Occurs unasserted (8)

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, V30, V31, V37

Never arises (4)

No fixture or generated test produces the condition at all. V32, V33, and V34 await an earlier verification result to compare against; V16's declared-present-and-absent case has a failing branch in declared-elements and no fixture.

V16, 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, and it sits in its own bucket so the reason travels with the fact and the partition stays complete.

V22

Required to fail, and isolation

key-binding has no failing state in the implementation, because V13's stapled branches are expressible after AEF 1200 v0.2 and remain unimplemented, which the running failure list carries. anchor-ordering and algorithm-standing have no failing state by design: they report and decide nothing. record-form fails on a member-set violation and reports not-run on an unknown form. seal-latency's failing fixture fails it non-fatally, a finding inside a declared boundary. Of 22 checks, 5 have no failing entry counting generated tests, two of those by design; under C5, 12 of 22 have no failing fixture.

Checks with no failing fixture under C5: key-binding, declared-elements, role-disclosure, trust-base-reference, anchor-ordering, algorithm-standing.

Fifteen fatal-capable checks: record-form joined when R1's member-set test gave it a failing state. The withIsolatingFixture list counts generated tests for the seven pre-1301 checks; under C5, the approval, anchor, and form checks are the ones with pinned isolating fixtures.

Five entries pin complete qualification sets by class: the approval-0001 worked example, the self-approved record, run-0001, anchor-0001, and the form-0002 worked example. Eleven more assert one or more classes without pinning the full set. Every other entry still fails AEF 1201 C6 in part.

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 8 failures against AEF 1201's requirements, listed with the rest of the series' state on the status page, and states the conformance claim's standing:

None exists and none can honestly be made. AEF 1201 C1 requires a suite version, and this suite does not yet satisfy the requirements that make its version meaningful. AEF 1201 section 12 states this.