Module 004 — Attestation boundary
What can enclave attestation prove about a file's life before the enclave first touched it?
The standing conjecture: nothing, by itself. Attestation can bind what happens from the first attested operation onward; everything earlier lies outside the provenance claim unless independently established. The boundary — not the pipeline — is the research object.
Status — plannedPublic evidence — none yetQuestion — statedResult — not yet populated
07Claim envelope
AS-001
Publicly untested · Owner-attested
Assay is an early-stage experiment in enclave-attested media processing on AWS Nitro Enclaves, investigating which provenance claims a verifier can and cannot derive from attestation.
- Scope
- Owner statement only; the artifact is private.
- Support
- No public artifact yet, by declaration.
- Dimensions
- visibilityPrivateprovenanceOwner-attestedsupport roleNone publicmaturityExperimental
- Reviewed
- 2026-08-20 · window 120 days
- Triggers
- manual public artifact released
- Non-claims
- no public evidence is offered; nothing about completeness, security, or provenance-chain origin is established
- attestation cannot establish a file's history prior to the first attested operation
Rendered from the same registry as the ledger — one source, two views.
08Evidence
AS-001 — Owner-attested · no public binding, by declaration · reviewed 2026-08-20
10Non-claims
- no public evidence is offered; nothing about completeness, security, or provenance-chain origin is established
- attestation cannot establish a file's history prior to the first attested operation
- No public evidence exists yet, by declaration; this page will not pretend otherwise.
12Next unknown
A public artifact whose provenance claims are stated together with the attestation horizon that limits them — released only when it can stand behind itself.