SOLO does not ask participants to trust unattributed data. It preserves the lineage of every reusable verification.
The lineage every certificate carries
When a product query consolidates verifications into a certificate, each populated sub-product is self-describing:
Each query result also records, in
meta, the network and the
querying policy that shaped it, and
product query responses carry an X-Ref-Id header identifying the query event.
The coverage check goes a step further
and returns a human-readable furnishing_entity_name alongside the
furnishing_entity_id, so you can see which participants could satisfy a
product for a subject before you query.
One subject, many furnishers
An entity profile is a shared subject, not a record any one participant owns. Several participants can furnish about the same consumer or business — one contributes identity verification, another fraud signals, a third business registration. All of it attaches to the same profile, and each contribution keeps its own attribution. Two consequences follow:- You don’t own the whole profile. Your furnished records sit alongside others’. Furnishing never overwrites another participant’s records.
- What you can read is governed, not automatic. Sharing a subject with another furnisher does not mean you see their data — see Entitlement.
How the network picks which verification to use
When several furnished records could answer for the same model, the query does not guess:- The querying policy filters which furnished records qualify, field by field.
- Of the qualifying records you’re entitled to read, SOLO uses the oldest one found in any of the networks you queried.
furnishing_entity_ids on a query to use only those participants’ records.
Why provenance is exposed on purpose
For most software, exposing internals is a mistake. For SOLO it is the product: participants build on each other’s work because they can see who did it, how, and when. Provenance turns “trust SOLO” into “trust the network, transparently.”Provenance here means the lineage that exists today —
furnishing_entity_id,
attestation_event_id, assertion timestamps, source, method, and evidence
fields, and the network and policy recorded in each result’s meta.
It does not include reuse counters, dispute counts, or contributor reputation
scores, which are not part of the current platform.Related
Trust assets
The reusable unit provenance describes.
Entitlement
Why you can read a given record about a subject.
Querying policies
The rules that decide which verifications qualify.
Coverage check
See which furnishers can satisfy a product before you query.