Local authority point
The master node acts as the local operational anchor for field devices, hosted receipts, queues, sync status and proof review.
System architecture
Master nodes, field devices, receipt hosting and manual sync.
The VERIMESH architecture is designed around local operational authority: a master node anchors field devices, receives proof records, displays safe review surfaces and supports deliberate operator-authorised synchronization.
Offline-firstReceipt-backedManual syncMaster nodeRead-only review
Core points
Key VERIMESH concepts on this page.
Controlled edge workflows
Tablets or appliance devices record approved actions locally and bind those actions to device-level evidence.
Review without write exposure
Operational status and latest receipts can be shown through safe read-only views while restricted controls stay protected.
Operator action by design
Synchronization is treated as a deliberate operator-authorised action that can create its own receipt evidence.
Controlled software changes
Updates and capability changes can be controlled through signed release bundles rather than uncontrolled automatic updates.
Same proof standard, different workflows
Government, finance, cannabis and other sectors can define specific event types while using the same receipt structure.
Structured summary
How the VERIMESH model is described.
| Area | VERIMESH approach | Reason it matters |
|---|---|---|
| Node model | All devices anchor to a master node. | Creates one local source of operational truth and avoids scattered proof records. |
| Sync model | Manual operator-authorised sync only. | Keeps accountability visible when receipts, reports or settlement evidence move. |
| Review model | Read-only views for ordinary users; restricted controls for supervisors. | Lets departments inspect proof without exposing master-node authority. |
| Deployment model | Offline-first local network with optional later publication or export. | Supports field operations during outages or restricted connectivity. |
FAQ
Quick answers.
What is a VERIMESH master node?
A VERIMESH master node is the local operational anchor that hosts receipt status, device state, queues, proof review and manual sync controls.
Does VERIMESH need the cloud to run?
No. The architecture is designed around local-first operation with optional later sync, export or publication.
Why is synchronization manual?
Manual sync makes the operator action explicit and auditable, especially where sync can trigger reporting, reconciliation or settlement processes.
Continue
Return to the VERIMESH knowledge base.
Use the connected pages to understand the architecture, proof layer, sector workflows and official brand scope.