Skip to main contentA-REX Core

Diseño de sistema · AREX-ARCH

A-REX Architecture — one-page summary

The full design — context, requirements, component model, data model, sequence diagrams, operational model, security controls, measured performance, decision records and the traceability matrix — is in SYSTEM DESIGN.md.

ID del documento
AREX-ARCH
Versión
2.0 (summary of AREX-SDD-001)
Fecha
2026-09-21
Disponible solo en inglés
Este documento se publica en inglés. Los capítulos del whitepaper y los diagramas están traducidos; el estándar normativo, las guías de diseño de sistema y los registros de decisiones permanecen en inglés para que exista un único texto vinculante.
FieldValue
Document IDAREX-ARCH
Version2.0 (summary of AREX-SDD-001)
Date2026-09-21

The full design — context, requirements, component model, data model, sequence diagrams, operational model, security controls, measured performance, decision records and the traceability matrix — is in SYSTEM-DESIGN.md. This page is the summary.

Two tiers, one direction of dependency

flowchart TB
    S["<b>The standard</b><br/>standard/ + contracts/standard/<br/>interfaces · CC0"]
    R["<b>Reference implementation</b><br/>contracts/reference/core<br/>ARexToken · ARexAttestations · MIT"]
    D["<b>Demonstrations</b><br/>contracts/reference/hooks · extensions<br/>not normative · MIT"]
    S -->|implemented by| R
    R -->|demonstrated by| D
    D -.->|depend only on the interfaces| S
TierLocationDepends onMay change without a standard change
Standardstandard/, contracts/standard/nothingno (major version, two implementers)
Referencecontracts/reference/core/the standard, OpenZeppelinyes
Demonstrationscontracts/reference/hooks/, contracts/reference/extensions/, contracts/examples/the standard interfaces onlyyes

Layers

LayerInterfaceContent
0ERC-1155, ERC-165, IERC7943MultiTokenbalances; freeze; forced transfer; eligibility; canTransfer
1IARexBatchbatch record (open codes, pre-harvest, origin reference, metadata hash), role-only status, transform lineage
2IARexHook, IARexHookManagerordered rule pipeline; bytes32 codes; ARexHookRejected(hook, code)
3IARexAttestattestations per (batch, topic); trusted issuers per topic

The choke point

Every balance change passes through _update: lock → pause → eligibility → per-id (exists, not retired, frozen) → hooks check in order → balances → hooks onExecuted → unlock. canTransfer and transferCheck replay it as views.

Reference components

ComponentRole
ARexTokenlayers 0–2; UUPS; ERC-7201; 24,136 bytes
ARexAttestationslayer 3 companion
EligibilityHook, ExpiryHook, AttestationHookminimal demonstration hooks
PerishabilityHook, SeasonalHook, DeliveryHook, TraceabilityHookdomain hooks (decay, windows, custody, EPCIS events)
CommodityPriceOracle, CarbonImmobilizationWrapper, ParametricInsurancecompanion extensions

Roles (reference token)

ISSUER, TRANSFORMER, STATUS, ENFORCER, HOOK_ADMIN, PAUSER, UPGRADER, DEFAULT_ADMIN; ATTEST_ADMIN on the attestation registry. Authority never derives from balances.

Design rules in one line each

Open codes, never enums; one cached hook interface, never capability probes per transfer; bytes32 codes, never strings; status by role, never by balance, with a terminal retire; pre-harvest is first-class; lineage through transform; enforcement from ERC-7943; an origin reference, never coordinates; nothing required beyond the token; ERC-7201 storage. Rationale: ADR-001…016.