TRACE is five cooperating layers: an on-chain token, multi-party custody endorsement, checkpoint and EMCON event recording, an offline-resilient IoT pipeline, and a set of integrations that push verified events out to FORGE, AFRL, and the four DoD enterprise systems.
Every asset is a Hyperledger Fabric token anchored to the government UII parsed from the MIL-STD-130N Data Matrix barcode. The UII is immutable from mint onward — TRACE does not maintain a parallel numbering system.
A transfer cannot complete with one signature. The initiator submits a PENDING proposal; the receiving party authenticates independently and confirms or rejects. Both signatures land on-chain.
Custody-significant location events are written on-chain. EMCON state transitions — including hardware dark mode and tamper events — are recorded with timestamps from the tag’s non-volatile memory, not the moment of network reconnect.
Tag publishes flow through AWS IoT Core → SQS FIFO (preserving per-token order) → tag-event-processor Lambda. EMCON events are highest-priority and are never dropped — partial-batch failures requeue the message until Fabric submission succeeds.
Verified asset state is pushed to FORGE via a cross-account API the moment chaincode confirms a checkpoint. A dedicated bridge channel mirrors the same events into the AFRL Hyperledger network via a bidirectional translation table.
A 30-minute walkthrough covers a real team dispatch, a missing item recovered through last-known GPS, an EMCON dark period with NVM-restored truth, and the resulting CDRL property accountability report.