Home

AMA Cryptography Wiki

Post-Quantum Security System — built for people, data, and networks

A hybrid classical and post-quantum cryptographic framework combining NIST-standardized algorithms with defense-in-depth architecture and runtime observability.

---

How to use this wiki

• Build & integrate: Installation → Quick Start → API Reference
• Assure correctness: Security Model → Key Management → Adaptive Posture
• Operate & observe: Secure Memory → Hybrid Cryptography → Performance Benchmarks
• Need a map? Start with the system flow below; every node links to deeper pages.

---

System Blueprint — cryptographic package lifecycle

flowchart LR
    raw["Input: data / firmware / tx"]:::gray --> prep["Canonicalize + length-prefix"]:::gray
    prep --> sha3[SHA3-256 digest]:::gold
    sha3 --> hmac[HMAC-SHA3-256 auth]:::blue
    hmac --> ed[Ed25519 signature]:::black
    ed --> pqc[ML-DSA-65 signature]:::gold
    pqc --> ts[RFC 3161 timestamp]:::blue
    ts --> pkg[Cryptographic package]:::black
    pkg --> verify["Verify: HKDF keys + integrity + signatures"]:::blue
    verify --> monitor[3R observability loop]:::gold
    monitor --> action["Adaptive posture (lockdown / rotate / switch algos)"]:::black

classDef gold fill:#B4B124,stroke:#000000,color:#000000;
classDef blue fill:#11AEED,stroke:#000000,color:#000000;
classDef black fill:#000000,stroke:#B4B124,color:#f6f6f6;
classDef gray fill:#1a1a1a,stroke:#11AEED,color:#f6f6f6;

Loading

Why it matters: Each stage is independently checkable. An attacker must subvert the assurance, cryptographic, and execution layers in sequence — a defense-in-depth chain instead of a single gate.

---

Runtime Safety Loop — observability without guessing

flowchart TD
    event[Runtime crypto event]:::black --> resonance[Resonance FFT scan]:::blue
    resonance --> recursion[Recursion multi-scale patterning]:::gold
    recursion --> refactoring[Refactoring complexity score]:::blue
    refactoring --> verdict["Permit / flag / escalate"]:::black
    verdict --> posture[Adaptive posture switch]:::gold
    posture --> log["Telemetry + audit trail"]:::gray
    log --> learn[Feedback to threat model]:::blue

classDef gold fill:#B4B124,stroke:#000000,color:#000000;
classDef blue fill:#11AEED,stroke:#000000,color:#000000;
classDef black fill:#000000,stroke:#B4B124,color:#f6f6f6;
classDef gray fill:#1f1f1f,stroke:#11AEED,color:#f6f6f6;

Loading

---

Navigation by intent

• Build & Integrate:
  • Installation — requirements, toolchains, wheels
  • Quick Start — minimal create/verify package in 5 minutes
  • API Reference + C API — production calls, return codes
• Assurance & Lifecycle:
  • Security Model — threat coverage, residual risks, disclosure path
  • Key Management — hardened HD derivation, rotation, custody
  • Adaptive Posture — runtime policy toggles and allowed fallbacks
• Operations & Performance:
  • Secure Memory — zeroization, constant-time expectations
  • Hybrid Cryptography — binding combiners and KEM flow
  • Performance Benchmarks — throughput, latency, scaling curves

---

Build-with-confidence checklist

1. Define the trust surface: choose HSM/HKDF parameters; align with Security Model.
2. Assemble the pipeline: wire the API call sequence from Quick Start or API Reference.
3. Harden execution: enable zeroization + monitoring from Secure Memory and Adaptive Posture.
4. Measure and observe: run the 3R loop and record telemetry per Performance Benchmarks.

---

Status snapshot

Property	Value
Version	3.2.0
Algorithms	ML-DSA-65, ML-KEM-1024, SLH-DSA, Ed25519, AES-256-GCM, Argon2id
Platforms	Linux, macOS, Windows
Python	3.9 – 3.13
Audit	Community-tested · Not externally audited
License	Apache 2.0

Production guardrails: Use a FIPS 140-2 Level 3+ HSM for master secrets, enforce constant-time verification, and perform independent cryptographic review before deployment. See Security-Model for requirements.

---

Contact: steel.sa.llc@gmail.com — Report a vulnerability — Contribute
Built by Steel Security Advisors LLC. Last updated: 2026-05-18.