Xworks™ — Verification Infrastructure

The verification spine

Eight gates.
One outcome.

Every record passes through the same deterministic sequence. Rules execute in fixed order. Outcomes are terminal. No manual override of QUARANTINE BLOCK. No inference on missing evidence. The spine is the system of record.

Gate 0

Trust

✕ BLOCK / ✓ PROCEED

Gate 0 Trust Gate

Entity KYC, AML, and sanctions check. Runs before any document or registry validation. A sanctioned entity is an absolute block — no override exists anywhere in the system.

Entity trust verification
→ diligence record (most recent row)

✗Sanctions check active → QUARANTINE BLOCK SANCTIONED_ENTITY

✗AML status flagged → QUARANTINE BLOCK AML_FLAGGED

✗KYC check failed → QUARANTINE BLOCK KYC_FAILED

○KYC not yet verified → QUARANTINE REVIEW (passes through)

✓All clear → trust record merged, proceed to Gate 0.5

✓ PROCEED

✗ BLOCK

Gate 0.5

Code

✕ HARD STOP / ● REVIEW

Gate 0.5 Code Validation

EWC code, HS code, entity role, and role confidence check. Invalid or unrecognised codes hard-stop the record before it touches registry or document paths.

Waste code reference · Classification code reference
Operator role registry · Role confidence scoring

✗EWC code not in Waste code reference → HARD STOP INVALID_EWC

✗HS code required but absent (TFS) → HARD STOP MISSING_HS

✗Operator role not in Operator role registry → HARD STOP INVALID_ROLE

○Role confidence scoring = LOW → QUARANTINE REVIEW (proceeds)

✓All codes valid → proceed to Gate 1

✓ REVIEW

✗ HARD STOP

Gate 1

Registry

✓ VERIFIED / ● DOCUMENT

Gate 1 Registry Validation

the registry authority registry fetch. Resolves verification path to either REGISTRY or DOCUMENT. Registry path is authoritative. Document path triggers additional document validation burden.

the registry authority API fetch → verification path
→ evidence_records.verification path

✓the registry authority confirms operator registration → verification path = REGISTRY

○the registry authority fetch fails or no match → verification path = DOCUMENT

○DOCUMENT path → permit, licence docs required at Gate 2

✓ VERIFIED

○ DOCUMENT

Gate 2

Pre-Insert

✕ QUARANTINE / ✓ ACCEPTED

Gate 2 Pre-Insert Validation

35 failure codes evaluated before the record is written. Red codes are supplier-fixable. Blue codes require operator action. No record enters the database without passing this gate.

Pre-insert validation
→ decision log · C01–C35

✗C02 name mismatch · C09 legibility · C12 duplicate → QUARANTINE (red)

✗C28 role not verified · C31 obligation undefined → QUARANTINE (blue)

✓All 35 checks clear → record inserted → ACCEPTED

✓ ACCEPTED

✗ QUARANTINE

Gate 3

Regulatory

✕ BREACH / ✓ COMPLIANT

Gate 3 Regulatory Enforcement

Mandatory legal obligations assessed per EWC code and jurisdiction. PPWR, CSRD, TFS notification, Duty of Care. A breach blocks issuance — it is not a soft warning.

Regulatory obligation assessment
→ obligation status

✗Missing TFS notification (cross-border) → OBLIGATION BREACH

✗PPWR compliance gap → OBLIGATION BREACH

✗Duty of Care transfer chain incomplete → OBLIGATION BREACH

✓All obligations met → COMPLIANT · proceed to Gate 4

✓ COMPLIANT

✗ BREACH

Gate 4

Load

✕ INCOMPLETE / ✓ COMPLETE

Gate 4 Load Completeness

Five sub-gates must all pass: Tier 1 entity docs, Tier 2 per-load records, Tier 3 processing receipts, mass balance reconciliation, and regulatory record completeness.

Load completeness check
→ 5 gates: T1 · T2 · T3 · massBalance · regulatory

✗Any T2 load without linked T3 receipt → INCOMPLETE

✗Mass balance variance exceeds threshold → INCOMPLETE

✗T1 entity doc outstanding → INCOMPLETE

✓All 5 sub-gates pass → COMPLETE · proceed to Terminal

✓ COMPLETE

✗ INCOMPLETE

Terminal

Verification

✓ ACCEPTED · ● QUARANTINE · ✕ REJECTED

Terminal Verification State

Deterministic terminal outcome. Computed from all gate results. Immutable once verification path = REGISTRY. Three terminal states — no further transitions from REJECTED.

Verification state view
→ verification_state · immutable

✓All gates pass → ACCEPTED · eligible for issuance

○Conditions unresolved → QUARANTINE REVIEW (resolvable)

✗Sanctions · fraud · irresolvable breach → REJECTED (terminal)

✓ ACCEPTED

✗ REJECTED

Portal access

ROLE_SUPPLIER

Recycler / Collector / Carrier

Submit evidence. Complete Tier 1 onboarding. Upload weighbridge tickets, transport notes, processing proof. Evidence enters the spine at Gate 0.

Portal A — Supplier Intake ↗

ROLE_BUYER

Brand Owner / Manufacturer / Corporate

Claim verified output directly from a verified batch. DPP, CSRD Scope 3, Recycled Content Certificate, CBAM declaration. Batch lookup validates your allocation before any upload is permitted.

Portal B — Reporting & Claims ↗

ROLE_TRADER

Trader / Broker / Intermediary

Allocate verified output across multiple buyers. Manage right-to-report allocations. Access batch-level allocation dashboard. Trader ID is system-assigned — no self-declaration.

Portal B — Allocation tab ↗

ROLE_AUDITOR

VVB · Verifier · Regulatory Observer

Read-only access to audit replay packages, LCA summary sheets, batch-level monitoring datasets. VVB independence from project participants is absolute per methodology requirements.

Verification Review Interface

Eight gates.One outcome.

Verification infrastructurefor industrial supply chains.

Eight gates.
One outcome.

Verification infrastructure
for industrial supply chains.