Universal Transaction Fabric: connecting the record of what happened
The Universal Transaction Fabric is the communication and event-recording layer connecting activities across the BTG systems. In everyday terms, think of it as the system of numbered receipts and dependable delivery between different departments. Each event can identify what happened, which asset or right it concerned, which authority acted, which rules were checked and how to retrieve the relevant evidence.
When NIKI produces an experiment result, the research service records it. When a DataChip version is qualified, the capability service records that event. When an owner grants a licence, the rights system records an authorization. When a customer actually pays, the financial service references the external payment evidence. A public transparency service may disclose a safe verification summary without publishing a private customer's identity or contract.
This fabric is designed to tolerate the ordinary failures of distributed computing. A message may be delayed, delivered twice or arrive after an outage. The architecture uses stable references, signatures, version checks and duplicate handling so repeated messages do not change legal balances twice. When one service fails after another has acted, the recovery process must reconcile the authoritative records rather than simply declaring all parts of the transaction successful.
The name 'transaction' has a broad meaning here: it may refer to a confirmed technical event, a licence permission or an actual financial transaction. A technical event receipt is not money. It is also not automatically a corporate share certificate or enforceable assignment of intellectual property. Each real-world authority remains separately identified.