EA-HK-INFRA-01 applies EA-HK-01 to operational infrastructure.
Its portable statement is: a summary discards structure to save space; a kernel discards material to save structure. For infrastructure, this means preserving the architecture that produced a running system rather than preserving every live container, environment value, or data volume.
An infrastructure holographic kernel must:
1. contain the complete architectural specification as executable role operators; 2. carry DOI and ORCID provenance; 3. pass the Back-Projection Test at a stated threshold; 4. permit a node with a valid clone to project any declared role.
Three invariants govern the object:
The specification distinguishes stateful from stateless recovery. A web service or cache may be reconstructed from the pattern alone. A database role can be recreated and reattached to a surviving volume, but absent data cannot be regenerated by the kernel.
Self-projection is constrained by integrity verification, secret availability, resource capacity, uniqueness policies, health checks, rate limiting, and operational logging. A corrupted kernel must not propagate itself.
The work positions the kernel beside—not in place of—infrastructure-as-code, reproducible builds, software citation, backups, Kubernetes, SLSA, in-toto, Nix, and supply-chain attestations. Its claimed distinct contribution is a citable, reconstructive architecture in which role logic, recovery policy, secret shape, and provenance are held together.
The document’s implementation maturity is carefully divided:
The production gate is specified, not yet completed in the body.