Skip to content

Warehouse Receipts Architecture

The Warehouse Receipts workspace is a domain adapter over the general OpenETR protocol model.

Layer Model

flowchart TB
  A["Warehouse receipt users"] --> B["Warehouse Receipts workspace"]
  B --> C["OpenETR service layer"]
  C --> D["OpenETR Nostr wire format"]
  D --> E["Relay pool / local event store"]
  C --> F["Verifier policy"]
  F --> G["Recognition sources"]
  G --> H["TRQP / Web of Trust / registry / KYC / rule book"]

Domain Adapter

The workspace speaks warehouse receipt language:

  • create receipt evidence record;
  • current holder/controller;
  • pledge or lien;
  • release;
  • presentation for delivery;
  • completed lifecycle.

It translates those concepts into generic OpenETR service calls.

OpenETR Core

The OpenETR component remains general.

It works with:

  • digests;
  • Anchor Events;
  • evidence events;
  • linked-evidence events;
  • Nostr pubkeys;
  • action tags;
  • relay-backed publication and query;
  • defined state-transition rules;
  • Consequential State derivation;
  • verifier warnings.

This lets other domains, including Product Passports, reuse the same DCR evidence and state-derivation model without inheriting MLWR-specific terminology.

Wire Format

The Nostr wire format is the interoperability boundary.

Integrators can use:

  • the webapp;
  • the REST endpoints demonstrated by the app;
  • the CLI;
  • the installable Python component;
  • direct protocol-level event integration.

Deployment Philosophy

OpenETR does not require relying on someone else's running code at time of performance.

Everything important is represented as cryptographically signed events. Those events can be served from public relay pools, private relays, third-party services, or local event stores.

Source Notes