OpenChainGraph Suite · CONTRACT A3 · arch #5

FIDO2 / WebAuthn PQC Conformance

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

FIDO2/WebAuthn/COSE ML-DSA conformance vs IANA identifiers + CTAP2.3 (ART-88) -> audit receipt (cry-05). Credential crypto-suite migration; credential FORMAT/protocol conformance belongs to any future EUDI wave.

OpenChainGraph · 2 Steps cryptographic mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII
Chain Topology — FIDO2 / WebAuthn PQC Conformance Checker → Agent-Action Audit-Trail Aggregator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 2 Steps
1 ROOT · D0 node
FIDO2 / WebAuthn PQC Conformance Checker art-88-fido-pqc-conformance-checker
conformance verdict (H1) feeds the aggregator
MCP Call · check_fido_pqc_conformance
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_fido_pqc_conformance",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 TERMINAL · D2 node
Agent-Action Audit-Trail Aggregator cry-05-agent-action-audit-trail-aggregator
Exports composite FIDO PQC conformance artifact with execution_hash (H2), final stage
MCP Call · aggregate_execution_receipts
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "aggregate_execution_receipts",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition — no new hash is minted. Available after hash computation.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: The vendor calls this authenticator quantum-ready. Does it meet the ML-DSA-65 conformance target as shipped?
Run the AINumbers MCP tool `run_chain` with {"chain":"pqc-fido-webauthn"} and read `art-88-fido-pqc-conformance-checker.conformant`.
Re-run with `inputs` for `art-88-fido-pqc-conformance-checker`, reusing the values that result echoed, with `authenticator` changed so cose_algorithms is [-49] and ctap_version is 2.3. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/pqc-fido-webauthn.html