Air-gapped and classified

Sovereign and classified estates cannot depend on a SaaS control plane for minting or revocation. Foundry mints offline, Model A validates locally at Gate, and self-hosted Control keeps identity lifecycle inside the boundary.

Air-gapped Foundry+Control

Classified air-gapped Foundry plus Control island topology

Foundry minting

Air-gapped minting appliance producing cohort binaries and twin circuits

Classified and sovereign estates cannot depend on a vendor cloud for minting or revocation. ENI6MA's Sovereign packaging licenses Foundry (the minting appliance that manufactures per-identity circuit binaries) for air-gapped manufacturing, ships Control for a self-hosted registry and durable nonce ledger, and supports Model A local validate-proof at Gate so enforcement does not require a path to ENI6MA cloud.

Artifacts move via your approved media process. Revocation remains a handle state change inside your Control instance. The envelope contract (one-time cryptographic authorization for a single request) is identical to connected deployments; only the ops topology changes. That is the point for investors and auditors: same mechanism, different deployment shape, no invented compliance badges.

What this solution claims

Foundry minting and Model A local verification can run without a network path to ENI6MA cloud services.ValidatedAir-gappable Foundry license path and local validate-proof acquisition.

Model A (local validate-proof) and Model B (registry validate-proof) are security-equivalent at the envelope layer.ValidatedThe client assembles the same envelope either way; only verifier acquisition differs.