A metadata-only trade asset passport is a structured identity and evidence record for a trade-related object. It supports review preparation only; it does not create ownership, approve financing, authorize payment, or perform capital execution.
Core identity fields
The passport should identify the trade case, object type, relevant parties, goods or receivables, commercial references, currency, value, dates, and current lifecycle state. Each field should distinguish asserted data from human-confirmed data.
Evidence links
A metadata-only trade asset record should link each material claim to its source: contract, invoice, shipment record, warehouse evidence, inspection result, insurance record, confirmation, or external system reference. A copied value without provenance is weaker than a traceable claim.
Rights and relationship claims
The passport may record claimed seller, buyer, holder, obligor, beneficiary, custodian, or reviewer relationships, but these remain metadata-only claims until the relevant authority confirms them. The record is non-approval and non-execution.
Status, conflicts, and gaps
Useful states include known, claimed, confirmed, conflicting, missing, stale, and not applicable. The passport should preserve disagreement instead of silently selecting one source.
Review history
The record should show who added evidence, who confirmed a fact, what changed, and which questions remain open. This makes the package easier to review without turning history into an automated decision.
What does not belong
A metadata-only trade asset passport must not contain executable payment instructions, automatic approval, settlement commands, token movement, chain submission, or capital execution. Those are separate controlled domains, not consequences of a complete record.
The design goal is simple: make the trade object understandable and traceable while keeping decision and execution authority outside the passport.