Trust Object
presschain-models defines TrustObject as a structured envelope that can carry information across identity, source, content, evidence, provenance and analysis domains without flattening them into a single score.
The current Rust model contains:
Why the model is broad
A Capsule is a protocol publication record. A Trust Object is a broader structured record that can describe the context around content whether or not that content has already been published to PressChain. Makingcapsule optional allows an application to normalize external or pre-publication information and later attach the canonical Capsule projection when one exists.
Interoperability does not merge systems
PressChain can produce or consume structured trust-compatible objects, but PressChain and the separate TRUST Layer remain distinct systems. Shared data shapes do not merge governance, infrastructure, branding or legal authority. If an application combines PressChain records with another analysis system, preserve source attribution for every externally produced field.Adapt at the boundary
A clean integration maps external data once at ingestion instead of teaching every UI component to understand several incompatible shapes.Keep facts and interpretation separate
An extracted claim is not automatically an on-chain fact. A risk signal is not a Capsule status. An external confidence score is not evidence. The model remains useful because those concepts remain separate and can carry their own provenance. Consumers can then decide which components they trust and why.Version the envelope
Treatversion as compatibility data. A parser should explicitly adapt or reject an incompatible future major shape instead of silently ignoring fields it does not understand.
For exchanged objects, record both model version and producer identity. That makes debugging and audits far easier than relying on the receiving application’s deployment date.