Whitepaper · 05
Technical Specification
What A-REX Core covers, and what this chapter withholds.
Purpose of this chapter
This chapter states the scope of the standard. The normative clauses stay in the standard repository, together with signatures, constants, error names, storage layouts, and the metadata schema.
Audience
A public reader can learn which problem the standard addresses and which kinds of rule it leaves open. A company that wants to implement A-REX, issue batches with it, or audit it requests the normative text on Request early access.
Layers
| Layer | What it is for |
|---|---|
| Enforcement | Freeze, forced transfer, and account eligibility, so a lot can sit under a lien, a recall, or a court order. |
| Batch identity | Commodity, unit, time, an origin reference, a commitment to an off-chain document, and a lifecycle status. |
| Lineage | A lot can be split, merged, or processed, and the parent lots remain linked. |
| Rules | One ordered pipeline of external contracts. A rule reports a result. The rule does not define a new token. |
| Attestations | Statements about a batch and a topic, from issuers trusted for that topic. |
Outside the standard
Crop lists, grade names, prices, decay curves, identity systems, and carbon issuance sit outside the core. They can be demonstrated beside it. Conformance does not require them.
Withheld on purpose
The normative specification, the interface sources, and the batch metadata schema are available under the early-access process. Access is for evaluation, implementation, and feedback. Each request is reviewed by hand. Approved readers receive read-only access to the standard repository and the reference implementation. The material stays confidential until it is published. The written terms say the standard will be published under CC0 and that early access grants no exclusivity.
Boundary of this chapter
This chapter names purposes. The early-access page is Request early access.