Diagrams · 06

Standards landscape

Where A-REX Core sits among token, enforcement and traceability standards, and what it takes from each.

flowchart TB
    subgraph TOKEN["Token standards"]
        E1155[ERC-1155 multi-token]
        E165[ERC-165 interface detection]
        E7201[ERC-7201 namespaced storage]
    end
    subgraph ENFORCE["Enforcement"]
        E7943[ERC-7943 uRWA · Final]
        E3643[ERC-3643 T-REX · ERC-20 securities]
    end
    subgraph TRACE["Traceability and regulation"]
        EPCIS[GS1 EPCIS 2.0 · CBV]
        FSMA[FSMA 204 · KDE / CTE]
        EUDR[EUDR · due diligence statements]
    end
    subgraph AREX["A-REX Core"]
        BATCH[IARexBatch · lineage]
        HOOK[IARexHook · pipeline]
        ATT[IARexAttest]
    end
    E1155 --> AREX
    E165 --> AREX
    E7201 -.->|reference token| AREX
    E7943 -->|verbatim| AREX
    E3643 -.->|ICompliance wrapped as a hook| HOOK
    EPCIS -->|TransformationEvent ↔ BatchTransformed<br/>metadata schema| BATCH
    FSMA -->|traceability lot code, KDEs in metadata| BATCH
    EUDR -->|DDS reference in originRef, attestation topic| ATT

Standard	Relationship
ERC-1155	base token; every A-REX token is a full ERC-1155
ERC-7943 (multi-token)	adopted verbatim; interface id `0x41c4fbad`
ERC-3643	not required; a compliance module can be wrapped as an `IARexHook`
ERC-7201	storage layout of the reference token, not a requirement of the standard
GS1 EPCIS 2.0	vocabulary of `TraceabilityHook`; `transform` ↔ `TransformationEvent`
FSMA 204, EUDR	represented as references, hashes and attestation topics; never as on-chain logic