Regulators
A regulation is not a checklist here. It is a signed object — an authority, the instrument, the article you are relying on, the edition, a digest of the published document, the dates it is in force, and the rules it actually imposes.
Several apply at once, and they disagree. This page shows what happens when they do. Everything below was computed by composing two real regulations while this page was built.
Two regulators, one shipment
| Authority | Instrument | In force from | What it asks for |
|---|---|---|---|
| European Union | Regulation (EU) 2023/1115 (EUDR) | 2025-12-30 | MAX_AGE geolocation = 365 (Art. 9)MIN_PROVENANCE geolocation = SELLER-ASSERTED (Art. 9(1)(d))REQUIRE_CLAIM geolocation (Art. 9(1)(d)) |
| United States FDA | 21 CFR 1.1300 et seq. (FSMA 204) | 2026-01-20 | MAX_AGE geolocation = 90 (1.1345(c))MIN_PROVENANCE geolocation = VERIFIED (1.1345(b))NEVER_WAIVABLE traceability_lot_code (1.1345)REQUIRE_CLAIM traceability_lot_code (1.1345) |
They disagree, and the stricter one binds
Both regulators care about geolocation. The EU accepts a supplier's own word and a year-old reading. The FDA wants an independently verified one no older than ninety days. Nothing averages.
| Requirement | What binds | Which authority | Citation | The weaker ask, recorded |
|---|---|---|---|---|
| maximum age | 90 days | United States FDA | 1.1345(c) | 365 days (European Union) |
| minimum provenance | VERIFIED | United States FDA | 1.1345(b) | SELLER-ASSERTED (European Union) |
And it compiles into the decision itself
This is what the engine is handed. Not a report about the regulations — the requirements themselves, in the engine's own terms:
{
"critical": [
{
"key": "lot:COCOA-77|geolocation",
"min_class": "VERIFIED",
"ai_position": "ADMIT",
"max_age_days": 90
},
{
"key": "lot:COCOA-77|traceability_lot_code",
"ai_position": "ADMIT"
}
],
"neverWaivable": [
"lot:COCOA-77|traceability_lot_code"
]
}The 90-day limit that reached this task came from the FDA, and the claim marked never-waivable stays never-waivable: no acceptor at any level, including one who could accept a fifty-million-dollar exposure, may price that gap.
And where two authorities genuinely conflict, nothing compiles
A stricter number is not a conflict — it is an answer. A conflict is two authorities asking for things that cannot both be satisfied, and the engine refuses to compile a composition that did not resolve, in its own words: "Conflicts must be settled by a person, not compiled around."
That is the same rule the rest of the suite runs on. Averaging two regulators would produce a number neither of them asked for, and a decision defended by nobody.
Who is competent to attest what
An authority can require that a claim come from an accredited source, and "accredited" is not a word — it is a set of industry codes. The engine carries the US SIC and NAICS tables with a crosswalk between them, so a rule written against one answers a record classified under the other.
| Question | Answer |
|---|---|
| SIC 8734 (Testing Laboratories) maps to NAICS | 541380 |
| NAICS 541380 (Testing Laboratories) maps to SIC | 8734 |
| Where the table comes from | {"status":"HAND-CURATED WORKING SUBSET — NOT the authoritative federal tables","curated_at":"2026-08-01","naics_edition":"NAICS 2022 (the 2022 revision of the North American Industry Classification Sy |
What is not here
The mechanism is general. The library of instruments is not, and this page would be worth nothing if it implied otherwise.
- Shipped as demonstrations: the two above, plus the deforestation and forced-labour instruments the other pages use. They are shaped correctly and their article numbers are illustrative.
- NOT shipped: clinical and laboratory research obligations — 45 CFR 46, ICH GCP, OECD GLP — and the reporting schemas of federal and international research funders. Nothing here has been drafted against them and no page should be read as claiming otherwise.
- Every instrument needs a practitioner. Turning a regulation into rules is a legal act, and the engine's job is to enforce exactly what somebody signed — never to interpret a statute.
This estate holds no private keys. The signatures on this page were made with demonstration keys derived from published labels; in a real deployment a compliance officer signs an instrument with their own key and the engine only ever verifies.
AttestedAssets · standalone install · one product · built by 27-console/build-console.js from the register, not typed.
This page loads nothing from another origin, makes no request at run time, and touches no browser storage. It works from a file on disk with no server.
Nothing in this console is legal advice.