MassTrail Verify
Observe what matters.
Mix accessible ProofLink capture with registered ProofNode, ProofLens and ProofMove evidence at material-risk points.
- Durable tag and seal lifecycle
- Direct scale and device health
- Blind two-ended ProofPair
Waste attestation · evidence control · reporting close
Every reported tonne,
backed by evidence.
MassTrail connects critical field observations, independent counterparties and the systems you already use—then closes the chain into a reproducible management evidence pack.
Technical verification, precisely bounded. Evidence level and limitations stay visible. MassTrail does not certify tonnes or issue an assurance conclusion.
Corridor MT-1042Synthetic live view
Origin · ProofNode12 420 kgTP-E2 · stable
Difference550 kgAbove 100 kg policy
Receiver · blind commit11 870 kgTP-E2 · revealed
EX-1042 · mass exceptionIndependent receiving observation differs from origin.
2 hStart with the phones, scales and systems you have.Add direct device evidence where the risk justifies it.Keep every correction and limitation visible.
The complete evidence chain
Twelve events. One controlled trail.
Follow the material once, then inspect where the story can break, which controls expose it, and what survives the reporting close.
A continuous trail from programme setup through field observations, blind receiving, controls, exception decisions and period close.
01 / 12
Set the rules · verify
Register the corridor
Programme, material, parties and reporting criteria are versioned before the first load.
Evidence receiptPolicy v3 · parties separated
Read the complete twelve-event sequence
- Register the corridor. Programme, material, parties and reporting criteria are versioned before the first load. Effective dates and approval history.
- Declare the load. The source creates a planned load without deciding what later observations must say. Declaration retained beside later evidence.
- Tag and seal. Durable identities bind the asset, vehicle and custody unit to the event. Assignment, mounting and seal lifecycle.
- Record at origin. ProofLink stays accessible; ProofNode adds a direct registered instrument reading where justified. Authority remains visible; nothing is overwritten.
- Add a lens. An event frame can compare display, plate and seal without becoming the scale reading. Challenge, hash, time and source comparison.
- Hand over custody. Vehicle, seal and departure are linked; location corroborates movement, not contents. Vehicle/load/seal continuity.
- Receive blind. The receiver commits its own weight before the origin figure can be revealed. Server-enforced commit and reveal.
- Reveal the pair. ProofPair exposes the 550 kg difference and the independence of both endpoints. Independence and tolerance assessment.
- Join the records. Operating, ERP, payment and partner data meet the same evidence trail. Stable keys, mapping versions and lineage.
- Run controls. Mass, duplicate, cut-off, authority, health and custody rules cite every affected row. Deterministic rules with plain explanations.
- Resolve or disclose. Accountable people correct, exclude or accept a limitation under maker-checker control. Append-only disposition and second approval.
- Close the period. The locked manifest, evidence pack and workroom preserve the trail and its limitations. Versioned snapshot; reopen creates v2.
One product system
From physical event
to controlled close.
A load does not become reportable because it appears in a dashboard. Its identity, observations, source records, controls and decisions must survive the route.
MassTrail Control
Make conflict visible.
Join operating, ERP, payment and partner records without hiding their source authority or overwriting the raw evidence.
- Mass, duplicate and cut-off rules
- Row-level lineage and ProofGraph
- Neutral exception workbench
MassTrail Close
Lock what management decided.
Resolve or disclose exceptions, apply maker-checker approvals and freeze a reproducible snapshot without issuing assurance.
- Append-only adjustments
- Signed manifest and evidence pack
- Read-only practitioner workroom
An honest evidence ladder
No unexplained
“verified” badge.
Each reported quantity exposes what observed it, who corroborated it, the device state and the remaining limitation.
TP-E0
Declared
An authenticated person entered the event.
TP-E1
Source-backed
A durable ID, operating record or event media supports it.
TP-E2
Instrument-attested
A registered, healthy device supplied the observation.
TP-E3
Counterparty-corroborated
Independent endpoints agree within stated policy.
TP-E4
Independently sampled
An external practitioner sampled under their criteria.
Control the reporting bridge
1246.3 t reported.
1198.7 t supported.
This synthetic Q3 close keeps the unresolved 47.6 t visible and lets a reviewer trace every aggregate to source row, mapping and rule version.
Open Control CentreSource-to-report bridgeQ3 2026 · Africa/Johannesburg
− 5.2Excluded
− 47.6Unresolved
Source completeness5 of 5 expected feeds received
Unit and material mapping2 000 rows on approved mapping v3.1
Duplicate and overlap1 cluster awaits reviewer
Dispatch / receipt1 corridor above tolerance
Device health at event1 missing route signal
Cut-off and late events8 rows excluded with lineage
Synthetic demonstration · 2 000 rows · mapping materials@3.1.0
Works with what you have
Instrument the gap.
Do not replace the operation.
RS-232 · Modbus · API
Scale
ProofNode preserves raw stable-weight payloads.
WhatsApp · signed web · PWA
Phone
ProofLink keeps the evidence ceiling visible.
Plate · tracker · geofence
Vehicle
ProofMove corroborates movement, never contents.
CSV · API · SFTP · email
Systems
Adapters preserve source key, payload and parser version.
Blind commit · dispute
Counterparty
ProofPair separates what each endpoint observed.
Sample · request · export
Practitioner
The workroom supplies evidence, not a conclusion.
Evidence and device health together
See when the chain
is running degraded.
A fallback is a recorded condition, not a quiet downgrade.
Management evidence pack
Mzanzi Packaging
Recovery Programme
Q3 2026 · Close version 1
SHA-256 manifest8f2a…7c11
04
Reported-total bridge
Every line links to included rows, mapping version and evidence objects.
07
Exception register
EX-1042Receiving mass differs by 550 kg
EX-0981Possible duplicate across two source feeds
EX-0774ProofMove signal absent at receiving geofence
Close without erasing the trail
One pack for management.
One workroom for review.
Original files, device observations, transformations, controls, decisions and limitations remain together. A late event reopens to version 2; version 1 still exists.
- Maker-checker adjustments and approval log
- Machine-readable manifest with file hashes
- Evidence-level and device-health coverage
- Explicit management responsibility and non-assurance boundary
Built for evidence that must survive review
Append-only by design.
Corrections become events. Locked snapshots do not mutate.
Tenant-bound twice.
Database RLS and object-key isolation carry negative tests.
Explainable controls.
Rules cite inputs, version, affected mass and plain-language reason.
Bring one corridor and one reporting period
Find out what your next close
can actually reproduce.
The paid review profiles up to three supplied sources. The corridor pilot compares the accessible ProofLink path with direct two-ended evidence.