Concord engine vocabulary
Auditability Ledger
An append-only, hash-chained, Ed25519-signed evidence chain threading every decision the engine makes.
Definition
The Auditability Ledger inside Concord by IaxaI is the spine. Every translation decision, every entity match, every drift event, every mapping repair, every retrieval against the knowledge graph writes a signed receipt. Receipts hash-chain so any tampering with a past entry breaks every entry that follows it. Each entry is signed with an Ed25519 key per tenant. The ledger is the only durable record of why the engine produced the output it did. When an examiner asks how a number on a dashboard was derived, the answer is one query against the ledger. Not a screenshot reconstruction. When a regulator asks who approved a mapping change, the receipt names the analyst, the timestamp, and the calibrated confidence at decision time. Compliance Evidence Auto-Packets are built directly on top of the ledger; they cannot fabricate evidence because every claim is anchored to a receipt that was written when the event happened.
See also
Related capabilities and terms
Hash Chain (append-only ledger)
A sequence of records where each entry contains the cryptographic hash of the previous entry. Tamper any past row, every later row breaks.
Compliance Evidence Auto-Packets
FFIEC, SOC 2, HIPAA, and PCI evidence bundles assembled directly from the audit ledger. Not screenshotted into a PDF.
Reverse Transpiler
Compiles OCSF detections back into vendor-native query languages so one rule runs across every tool in the stack.
Calibrated Identity
Entity resolution with a coverage-guaranteed prediction set. Concord tells you when it doesn't know, instead of guessing.
Stop reconciling. Start trusting one timeline.
30-minute walkthrough. Your tools. Your tenants. Your audit cycle. We will show you exactly where Concord earns its keep.