Structured-Finance Receipt Schema

Use sf-receipt to represent a structured-finance fact, its cited sources, and server-authored confirmation metadata in one observation receipt.

The canonical v0 machine artifacts are immutable URLs on cmdrvl.com:

The wire schema_version is:

obs-receipt/0.3 (profile: sf-receipt/0.3)

What It Covers

An sf-receipt has three main parts:

• subject: the observation being asserted, such as a deal, loan, field, value type, period, and canonical value.
• citations: the attributed evidence, including party, value, source class, accession reference, URL, and observation time.
• receipt metadata: confirmation, confirmation_core, stage, procedure, issued_at, and receipt_sha256.

The profile is used by the CMD+RVL Receipts MCP server for SEC CMBS conduit verification. It is not limited to one server deployment; the schema URL is the stable contract clients can use when they receive an sf-receipt payload.

Vocabulary Guard

There are two different judgments:

• claim_verdict lives outside the receipt on a tool response envelope. It adjudicates the caller's claimed value against the canonical value. DENY belongs only there.
• receipt.confirmation lives inside the receipt. It says whether the cited sources agree with each other.

Do not merge those fields. A source conflict and a denied caller claim are different events.

Hash Rule

receipt_sha256 is the lowercase hex SHA-256 of the RFC 8785 JSON Canonicalization Scheme bytes for the receipt object with the receipt_sha256 key removed.

Clients can recompute the hash to verify that a detached receipt has not changed.

Minimal Client Pattern

{
  "schema_uri": "https://cmdrvl.com/schemas/sf-receipt/v0/schema.json",
  "context_uri": "https://cmdrvl.com/contexts/obs-receipt/v0/context.json",
  "profile": "sf-receipt",
  "version": "0.3"
}

Use the JSON Schema for structural validation. Use the JSON-LD context when lifting a wire receipt into RDF terms used by the CMD+RVL shape.

Current Limitations

• v0 is the public URL for the current 0.3 wire definition.
• The schema is a JSON Schema projection of the receipt contract; SHACL parity is maintained in the receipts implementation test suite.
• The schema defines the receipt payload only. MCP tool envelopes, including claim_verdict, are intentionally outside this schema.