Agentic Post-Quantum Conversion

Agentic Post-Quantum Conversion (APQC) is the discipline of transforming critical infrastructure — beginning with the migration of classical cryptography to post-quantum standards — using governed AI agents that operate under delegated authority and produce independently-verifiable evidence of every change.

This suite is a vendor-neutral specification corpus. It defines the discipline — its problem, model, lifecycle, architecture, authority and evidence models, maturity, and standards composition — independently of any implementation. H33 is a conforming reference implementation (APQC-REFERENCE-010), not the definition.

Figure 1 — The APQC Architecture. Know, permit, act, prove; govern continuously.

Foundational

APQC-GLOSSARY-000

APQC Glossary

The canonical dictionary of Agentic Post-Quantum Conversion — authority, evidence, the three graphs, and 60+ terms, with verification, validation, proof and attestation kept distinct.

APQC-CORE-001

APQC Constitution

The root specification of Agentic Post-Quantum Conversion: definition, principles, the twelve-stage lifecycle, the three-graph core, threat model, and conformance.

APQC-PROBLEM-002

Why Post-Quantum Migration Fails Today

Why cryptographic migration fails structurally — manual discovery, snapshot inventories, non-scaling consultants, unprovable completion — and why authority and proof must be intrinsic.

APQC-MODEL-003

APQC Conceptual Model

The conceptual model of APQC: the Knowledge, Authority, and Evidence graphs, and the invariants that hold across every transformation.

Operational

APQC-LIFECYCLE-004

APQC Lifecycle

The twelve decision-based stages by which autonomous systems transform critical infrastructure under governed authority — Intent through Continuous Adaptation.

APQC-ARCH-005

APQC Reference Architecture

The reference architecture of APQC: the Transformation Engine at the intersection of three graphs, wrapped by Governance — five engines total.

The moat — Authority & Evidence

APQC-AUTH-006

APQC Authority Model

Authority as a first-class object — root, graph, scope, delegation, revocation, continuity, replay — and why identity, authentication, and credentials are not authority.

APQC-EVIDENCE-007

APQC Evidence Model

Portable, replayable, independently-verifiable proof for every transformation: evidence objects, the evidence graph, completeness, survivability. Evidence is not logging.

Adoption

APQC-MATURITY-008

APQC Maturity Model

APQC maturity defined objectively by which engines you operate — Level 0 Unaware to Level 5 Autonomous — with a self-assessment questionnaire.

APQC-STANDARDS-009

APQC Standards Mapping

How APQC composes existing standards — NIST PQC, Zero Trust, IAM, audit, and compliance frameworks — rather than competing with them.

Conforming implementation

APQC-REFERENCE-010

APQC Conforming Reference Implementation

A falsifiable demonstration that the H33 platform conforms to APQC-CORE-001 through APQC-STANDARDS-009, with honest Implemented / Partial / Trajectory status.

Reserved

APQC-DECISION-011

Decision Model

Reserved — the decision object, lifecycle, replay, inheritance, and revocation. Anticipated after APQC-EVIDENCE-007.

Live reference-implementation proofs

These are the live, independently-verifiable proofs on h33.ai that instantiate this specification. The specification is vendor-neutral; H33 is a conforming reference implementation (APQC-REFERENCE-010).

LIVE PROOF ↗

H33-74 on Avalanche

FHE + STARK + three PQ signatures, anchored on-chain. Nothing mocked.

LIVE PROOF ↗

Trust Card

Independently verifiable evidence you hand an auditor — offline.

LIVE PROOF ↗

Portability Verifier

Verify any bundle against three PQ signature families. No H33 contact.

LIVE PROOF ↗

What Happens If H33 Disappears?

Verification still succeeds with H33 absent — survivability, proven.