6 documents
Diagrams
Architecture, lifecycle, pipeline, lineage and trust-boundary diagrams of A-REX Core.
The diagrams of A-REX Core in one place, each with the table or rule it illustrates: tiers and layers, the life of a batch, the transfer pipeline, lineage, roles and trust boundaries, and where A-REX sits among existing standards.
Documents
Architecture: tiers and layers
The two tiers of the repository, the four layers of the standard and the direction of every dependency.
Batch lifecycle
How a batch comes into existence, moves, changes status, becomes other batches and leaves the ledger. The only fixed statuses are 0 (ACTIVE) and 255 (RETIRED, terminal); everything in between is defined by the issuer.
Transfer pipeline
Every balance change in the reference token passes through one function. The order below is fixed; transferCheck and canTransfer replay it as views.
Lineage through transform
transform is the only way to make a batch from a batch. It burns inputs, mints outputs and records the parents; BatchTransformed maps one-to-one to an EPCIS 2.0 TransformationEvent.
Roles and trust boundaries
Who can do what to the reference token, where the trust boundary with hooks lies, and the recommended custody of each key. Authority never derives from balances.
Standards landscape
Where A-REX Core sits among token, enforcement and traceability standards, and what it takes from each.