Attested Execution Framework

Where the series stands

Every number on this page is derived at build time from the repository's artifacts: the coverage declaration, the challenge record, the threat model source, and the version registry. Nothing here is hand-edited. Where this page and an artifact disagree, the artifact is authoritative and this page is a build defect.

Documents

10 published documents. Superseded versions stay live at permanent paths for citation.

Published AEF documents with current version and date
No.TitleVersionDateSuperseded
1000Charterv0.311 August 20262 kept
1001Terminologyv0.111 August 2026–
1100Threat modelv0.211 August 20261 kept
1101The trust basev0.214 August 20261 kept
1200Verifier requirementsv0.214 August 20261 kept
1201Conformance and self-testv0.114 August 2026–
1300Record structure and scope declarationv0.214 August 20261 kept
1301Approval and signature semanticsv0.114 August 2026–
1400Sealing, time, and re-verificationv0.114 August 2026–
1900Provenance findingsv0.114 August 2026–

Verifier and suite

The reference verifier is aef-reference-verifier 0.5.0, written against 1200/0.2 with 1300/0.2, 1300/0.1, 1201/0.1, 1301/0.1, 1400/0.1 also applied. The suite version under AEF 1201 C10 is the digest of the coverage declaration as served:

sha-256:18d0d14f4a34e724b1d84b92027cbf0b823cf0a587b31ec3cf49b8f3ec25768c

Suite composition
Entries9443 pinned fixtures, 51 generated tests; under C5 only the pinned entries are fixtures
Required to fail46entries whose expected outcome is a failure
Checks2219 have a failing fixture counting all entries
Fatal-capable1515 have an isolating entry
Retired5expectations superseded by later rulings, each retired with its reason under C12

Coverage of AEF 1200 v0.2's 54 requirements, entry by entry, is in the browsable coverage declaration.

Threat dispositions

AEF 1100 v0.2 enumerates 23 threats. The dispositions below are parsed from the document's own text, concessions first, because the concessions are the content:

Threat counts by disposition
Conceded11no defense exists or is claimed
Conditional9defended only if a named mechanism exists
Out of scope2delegated to parties better placed
In scope1defended by the record as specified

AEF 1400 section 16 records 5 disposition changes as candidates for AEF 1100 v0.3. They are recorded, not applied, and this page reports them the same way:

Candidate disposition changes, recorded and not applied
ThreatNowCandidate
10.3 operator clockCONDITIONAL, unrealizableCONDITIONAL, realizable in part
10.4 seal-time delayCONCEDEDCONDITIONAL
7.3 scope amendmentCONDITIONAL, unrealizableCONDITIONAL, realizable
10.1 backward reachCONDITIONAL, half-unrealizableCONDITIONAL, realizable
R14 ordering (1300 §12)No observerCandidate observer

Open failures against AEF 1201

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

Challenge record

4 challenges filed, 4 resolved, none unresolved. Rulings: challenge-0001 adopted in part; challenge-0002 adopted; challenge-0003 adopted; challenge-0004 adopted. The full record, with each challenge's claim, observation, and ruling, is browsable here and served raw at challenge-record.json.

The conformance claim

The coverage declaration states the 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.

The blocking list this section used to carry is empty: what remained was implementation, and the implementation caught up. The claim is at /aef/conformance, partial and saying so, with per-fixture results and the shared-authorship sentence AEF 1201 section 9 requires until a second independent implementation exists.