Warehouse Receipts

MLWR Control Desk

Work with warehouse receipts in domain terms while the app translates each action into the general OpenETR control layer. The receipt file is hashed into an object id, then issued, queried, and evaluated through shared OpenETR services.

Read-only mode: query receipts without logging in. Log in to issue a receipt as a warehouse operator or issuer profile.

Receipt Roles

Warehouse Operator

Issues the receipt and commonly acts as obligor for delivery.

Holder

The current controller derived from the OpenETR control chain.

Secured Party

The beneficiary of a pledge, lien, or other encumbrance.

Attestor

A registry, warehouse, auditor, or relying party that can add recognition evidence.

Query Receipt State

Upload a warehouse receipt document and inspect its origin, holder, lifecycle, and outstanding pledge or encumbrance state.

Issue Receipt

Publish a warehouse receipt origin event. Underneath, this calls the general OpenETR issue service for the uploaded receipt digest.

Domain Actions

These receipt actions are domain names for general OpenETR control events. Query or issue a receipt first, then use the receipt-state page to transfer, pledge, release, present, or complete the receipt lifecycle.

Transfer receipt: maps to openetr transfer initiate and openetr transfer accept.
Record pledge or lien: maps to openetr encumber with the secured party as beneficiary.
Release pledge or lien: maps to openetr discharge referencing the encumbrance event.
Present for delivery: maps to openetr redeem with the warehouse operator as obligor.
Complete delivery: maps to openetr terminate-etr after the receipt lifecycle is complete.

Recognition Boundary

OpenETR records signed evidence of control and control-relevant assertions. MLWR-style law, local enactment, registry rules, contract, and institutional policy decide legal validity, protected-holder status, pledge effect, priority, warehouse obligations, and final recognition.