// Technology

How the architecture turns into enforcement.

The architecture resolves into enforceable paths: identity, policy, communication, evidence, and controlled change.

01

Workload Identity

SPIFFE-aligned identity issued from node and workload evidence.

Open mechanism →
02

QHx Flowspecs

Service annotations that realize proxy paths without hand-configuring every workload.

Open mechanism →
03

Hardware-Rooted Trust

TPM-backed node attestation and policy-gated identity issuance.

Open mechanism →
04

Post-Quantum Readiness

ML-DSA, ML-KEM, hybrid modes, and namespace-level algorithm selection.

Open mechanism →
05

AI / Request Notary

Signed request and response receipts for provenance and offline verification.

Open mechanism →
06

MLS Policy and Isolation

Classification, compartment, and releasability labels turned into enforcement.

Open mechanism →
07

Federation

Trust domains and bundle exchange across clusters, authorities, and operating environments.

Open mechanism →
08

Signed Resources

Signed policy and deployment bundles for controlled change in remote environments.

Open mechanism →
09

Message-Level Control

CABE for policy-bound objects beyond the live transport path.

Open mechanism →
10

DDIL Patterns

What proof, policy, and evidence can preserve when connectivity is broken.

Open mechanism →
11

Field Updates

Signed, versioned, rollback-resistant change for fielded systems.

Open mechanism →
12

Network Isolation

Automatically generated NetworkPolicies based on MLS identity.

Open mechanism →