For Partners
A figure could arrive with the record of its check, before anyone has to ask.
Every counterparty that receives one of your asset figures comes back for the evidence behind it, and you answer that request one counterparty at a time. A verification receipt records which policy was applied, the outcome and its reason codes, and a signed registry entry commits to it. An integration would touch two points: producing that record where a figure is issued, and checking it where the figure is received. The offline check calls no service, so your counterparty would run it on its own machine.
What an integration adds
Your counterparties could check your records without reaching your systems.
Opening a system to a counterparty means an access review, an export or a call that has to stay up. A receipt and its registry entry would go out with the figure. The entry commits to the bundle by digest, so a document changed afterwards would fail the counterparty's own check, and nothing would be asked of you.
The policy behind each figure
Customers, investors and your own teams would see which policy each figure was checked against and the reason codes behind its status. A question about an outcome would start from one named reason.
Issuer keys with a scope
A key authorized only for property valuations would fail the authorization check (L3) on a NAV entry.
One side or both
You could take on either side of the exchange on its own.
Producing receipts and running the verifier are separate jobs. Run only the verifier and you could check bundles from another platform; produce only receipts and your counterparties would have something to check on their own.
A single workflow
One asset type and one review process, traced from where the figure is issued to where it is checked.
Producing receipts
You would write, version and run your own policy in your own code; the project ships no policy engine. What the protocol defines is the record: which policy ran and what it returned. You would also need a signing key listed in the trust registry.
Running the verifier
You would choose the level you require, up to issuer authorization (L3).
Integration