System diagram
This is the transfer-evidence workflow. The pilot implements the originating side, a simulated counterparty and receipt mirroring, tested locally. Remote delivery to a live counterparty is not yet implemented.
The counterparty step runs against a local simulator; TRP and TRISA bridges remain prototypes. A mirrored receipt does not establish settlement or regulatory compliance.
Separate state tracks
| Track | Question |
|---|---|
| Policy | What was evaluated and which outcome was reached? |
| Counterparty exchange | Was required information delivered and accepted? |
| Proof | Does the proof verify under the approved statement and key? |
| Authorization | Are trusted state, freshness, binding and replay requirements satisfied? |
| Settlement | Was the custody/chain transfer actually completed? |
| Evidence | Can a reviewer reconstruct the scoped decision later? |
The pilot keeps these tracks separate, joins them into investigation timelines, and exports them as encrypted historical bundles for offline review. See architecture, contracts and status.
Last updated on