Stock Risk Receipt standalone install · one product

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

Both are SIGNED before they can compose. An unsigned regulation is somebody's assertion about the law, and this estate will not let one decide anything.
AuthorityInstrumentIn force fromWhat it asks for
European UnionRegulation (EU) 2023/1115 (EUDR)2025-12-30MAX_AGE geolocation = 365 (Art. 9)
MIN_PROVENANCE geolocation = SELLER-ASSERTED (Art. 9(1)(d))
REQUIRE_CLAIM geolocation (Art. 9(1)(d))
United States FDA21 CFR 1.1300 et seq. (FSMA 204)2026-01-20MAX_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.

The weaker ask is not discarded — it is carried, with its authority and its citation, so a receipt can show WHY the stricter number governed and who else was asking.
RequirementWhat bindsWhich authorityCitationThe weaker ask, recorded
maximum age90 daysUnited States FDA1.1345(c)365 days (European Union)
minimum provenanceVERIFIEDUnited States FDA1.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.

Read from the shipped crosswalk while this page was built. A packhouse bench does not satisfy "accredited laboratory" because the codes say it does not — not because somebody remembered to check.
QuestionAnswer
SIC 8734 (Testing Laboratories) maps to NAICS541380
NAICS 541380 (Testing Laboratories) maps to SIC8734
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.

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.

Stock Risk Receipt · 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.