Build patterns
9 ways to evaluate PQC integration with QNSI
Source-linked application patterns and explicitly labelled reference architectures. Deployment-specific behavior remains NOT VERIFIED unless independent production evidence is cited.
Catalog
Pick a pattern
LegalTech Contract Management
Source-linked contract-management integration pattern spanning storage, search, AI, and audit surfaces.
Source presence and snippet rendering do not prove mounted routes, encryption semantics, retention, AI isolation, audit coverage, or deployment behavior; all remain NOT VERIFIED.
Healthcare PHI / Patient Records
Source-linked PHI integration pattern spanning storage, search, tenant isolation, and audit contracts.
The pattern is not a compliance attestation or deployment proof. PHI protection, policy enforcement, isolation, audit completeness, and runtime behavior remain NOT VERIFIED.
Investment & Broker-Dealer Archives
Source-linked archive pattern for evaluating retention, audit, and searchable-encryption contracts.
The pattern is not evidence of WORM enforcement, regulatory compliance, immutable audit coverage, searchable encryption, or deployment behavior; all remain NOT VERIFIED.
Multi-Tenant B2B Platform
Source-linked multi-tenant integration pattern for onboarding, policy, storage, and metering contracts.
SDK source presence does not prove route reachability, tenant isolation, policy enforcement, quota accounting, billing, or deployment behavior; all remain NOT VERIFIED.
EdTech Secure LMS
Source-linked education-record integration pattern for storage, search, isolation, and retention contracts.
The pattern is not a compliance attestation or deployment proof. Record protection, selective indexing, retention, isolation, and runtime behavior remain NOT VERIFIED.
GovTech Public Records
Source-linked public-records pattern for evaluating access, audit, and retention contracts.
The pattern is not evidence of FOIA compliance, authorization enforcement, audit completeness, immutable retention, isolation, or deployment behavior; all remain NOT VERIFIED.
AI Agent / MCP Integration
Source-linked MCP integration pattern for evaluating QNSI tool, signing, and audit contracts.
Package and snippet presence do not prove MCP route reachability, PQC signing, audit effects, secret handling, or deployment behavior; all remain NOT VERIFIED.
Browser-to-Vault PQC Reference Architecture
Reference architecture for browser-side ML-KEM-768 and a PQC-native vault handoff. Deployed browser-to-vault behavior is NOT VERIFIED.
No executable handoff contract or independent deployment evidence exists for this architecture. Browser-to-vault confidentiality, PQC continuity, edge negotiation, and plaintext handling remain NOT VERIFIED.
Service-to-Service PQC Reference Architecture
Reference architecture for PQC-native service authentication and explicit composite interoperability. Production mTLS and ML-DSA SVID behavior is NOT VERIFIED.
No independently verified service-mesh execution path exists for this architecture. PQC mTLS, SVID issuance, certificate rotation, audit coverage, and deployment behavior remain NOT VERIFIED.
Next