SYNTHETIC DEMOWorkspace Mode: Synthetic demo data. Not connected to a backend, database, or blockchain. (Navigate to Live Registry for connected Supabase DB).
Material TraceabilityAudit Ledger · v0.1
Demo Mode (Offline Fixtures)Switch to Live Registry →
SYNTHETIC DEMO Prototype only. Backend and blockchain are not connected. All identifiers, hashes, and mass figures below are demonstration placeholders.

Batch DEMO-003

RECEIVEDReceivedReview status: Not applicable

Monitors (demo)

Synthetic demo data. Not connected to a backend, database, or blockchain. Names, times, masses and hashes below are invented.

Recorded Intake24.5 kg (24,500 g)
Claimed OutputNo claim yet
Last Updated (UTC)
NEXT WORKFLOW STAGEResponsible: Assigned Processor (Processor B (demo))

Awaiting processing claim & mass-balance submission

The processor must complete sorting, shredding, and material separation, then lodge a Processing Claim detailing recovered mass fractions (copper, circuit boards, plastics).

Integrity Gate: Total recovered mass must not exceed intake mass (conservation of mass rule).

Batch Summary & Custody Assignments

Assigned actors are separated from verifier judgment. Environmental impact remains gated until independent verification and cited public factors exist.

Lifecycle state
RECEIVEDReceived
Review status
Not applicable (status, not a stage)
Collector
Collector A (demo)
Processor (locked at registration)
Processor B (demo)
Assigned verifier (independent)
Verifier C (demo)
Recorded intake mass
24,500 g
Claimed output mass
No processing claim yet
Environmental impact
Unavailable
Impact gate: Unavailable until independent verification (state must be VERIFIED). No impact figure is shown or estimated.

Canonical Lifecycle & Alternative Outcomes

Five canonical happy-path stages with separate non-happy-path outcomes.

Traceability Principle: Stages 01–03 record physical custody transfer. Stage 04 is a processor self-reported claim. Stage 05 is an independently audited outcome.
  1. RegisteredREGISTEREDBatch created. Nothing has been collected yet.
  2. CollectedCOLLECTEDThe collector attests it collected the batch. Collected does not mean recycled.
  3. ReceivedRECEIVEDThe processor attests it received the batch at its facility.
  4. Processing claimedPROCESSED_CLAIMEDThe processor claims processing was done. This is a claim, not proof.
  5. VerifiedVERIFIEDThe assigned independent verifier accepted the processing claim.

Alternative Lifecycle Outcomes

Non-happy-path branches separated from the five canonical progression stages.

  • ReturnedRETURNED
    The verifier asked for additional evidence; the processor must resubmit with new evidence.
  • RejectedREJECTED
    Terminal. The verifier rejected the processing claim.
  • CancelledCANCELLED
    Terminal. Withdrawn before collection.

Evidence Records

Evidence files stay off-chain. Only SHA-256 hashes would be anchored. The values shown are placeholders, not digests of real files.

2 of 3 stage records
RecordSubmitted bySubmitted atHash (placeholder)Note
Collection recordEV-DEMO-003-ACollector A (demo)sha256:8c41…77adPlaceholder hash. Evidence file stays off-chain.
Receipt recordEV-DEMO-003-BProcessor B (demo)sha256:2e90…f1c3Placeholder hash. Evidence file stays off-chain.

Verifier Review Checklist

Current batch state is RECEIVED (review status: Not applicable).

Independent Verifier Review Checklist

Interactive demonstration checklist. Ticking items here simulates the verifier audit workflow in the client tab. No on-chain state or database row is modified without an authorized verifier transaction.

Audit criteria completed:0 of 5 (0%)
Simulated Verifier Decision Controls (Read-Only)

Actions disabled: verifier decisions are cryptographically enforced on-chain (D-15). Only the assigned verifier key may record a state transition.

Verification, return, and rejection can only be performed by the batch's assigned, independent verifier through the registry contract. This page has no such control and is not connected to the contract.

Event Timeline

Chronological log distinguishing on-chain lifecycle transitions from derived review-status updates.

3 events
  1. RegisteredLifecycle transition

    Batch registered with assigned collector, processor and verifier.

    Registrar (demo) ·

  2. CollectedLifecycle transition

    Collector recorded intake mass and collection evidence.

    Collector A (demo) ·

  3. ReceivedLifecycle transition

    Processor recorded receipt evidence.

    Processor B (demo) ·