Receipts
Receipts capture event identity, actor context, device context, timestamps, status, hashes, and release state.
LUMA XIP PROTOCOL
Luma XIP defines how operational receipts are structured, linked, exchanged, reviewed, and mapped to external standards without turning evidence into a closed product format.
Receipts capture event identity, actor context, device context, timestamps, status, hashes, and release state.
Each proof object follows a predictable model so reviewers and systems can inspect the same core fields.
Sector-specific event types can extend a common base without breaking chain continuity or review workflows.
Receipts can be exchanged across appliances, hubs, regulators, and settlement workflows with explicit mappings.
The protocol is designed to align with external assurance, audit, and evidence standards rather than replace them.
Profiles can map VERIMESH receipt fields to ISO-aligned controls for audit, governance, continuity, and security review.
Reference
The canonical Luma XIP specification lives in the public protocol repository. VERIMESH uses it as the evidence structure beneath receipts, reviews, settlement preparation, and cross-system proof exchange.