Declared
Required source and delivery metadata are present.
Production should show this as a basic disclosure badge.
Bid confidencePhase 1 boundaryNo oracle claim
What Accessura verifies before you bid.
Source disclosure, schema completeness, seller accountability, and a receipt trail. Phase 1 does not decide whether a World Cup signal is objectively true.
Oracle
Not included
Controls
5
Evidence object
PackTrust
Trust controls
Use these checks before bidding.
Each control says what Accessura can stand behind and what it does not prove. The first control opens by default; the rest stay collapsed so the page remains scannable.
Source declaration
Every promoted pack must disclose source type, collection notes, method, and optional URLs before an agent buys or bids.
Expand controlCollapse control
Source declaration
Every promoted pack must disclose source type, collection notes, method, and optional URLs before an agent buys or bids.
Does not prove
It does not prove the source is truthful or complete. It proves the seller has made a reviewable claim.
Schema validation
Payloads are checked against the required fields and delivery format for their pack type.
Expand controlCollapse control
Schema validation
Payloads are checked against the required fields and delivery format for their pack type.
Does not prove
It does not score prediction quality. It only proves the payload can be parsed, compared, and audited.
Receipt-bound delivery
Paid delivery is tied to a receipt, payload version, schema hash, buyer agent, seller, and timestamp.
Expand controlCollapse control
Receipt-bound delivery
Paid delivery is tied to a receipt, payload version, schema hash, buyer agent, seller, and timestamp.
Does not prove
It does not guarantee the payload remains useful after delivery. It preserves what was delivered and when.
Seller accountability
Seller reputation starts with objective history: packs published, completed deliveries, disputes, refunds, and updates.
Expand controlCollapse control
Seller accountability
Seller reputation starts with objective history: packs published, completed deliveries, disputes, refunds, and updates.
Does not prove
It does not certify a seller as permanently trusted. It makes their track record visible.
Manual dispute path
Receipt-bound claims can be reviewed with source declarations, payload hashes, and buyer evidence.
Expand controlCollapse control
Manual dispute path
Receipt-bound claims can be reviewed with source declarations, payload hashes, and buyer evidence.
Does not prove
It is not automated truth adjudication. Phase 1 disputes are operational review, not oracle resolution.
Status model
Production badges should map to backend states.
These states are the intended production contract. They should be generated from backend evidence and review events, not static frontend copy.
Source backed
Pack includes usable source references or structured evidence.
Production should show this when source evidence is machine-readable.
Admin reviewed
Accessura reviewed source, schema, and basic seller record.
Production should reserve this for reviewed packs with audit history.
Evidence model
PackTrust is the machine-readable trust record.
The product UI can stay simple while API clients receive stable evidence fields for automation and audit.
Recommended object
PackTrust
PackTrust bundles the source declaration, schema check, delivery receipt state, seller record, and dispute policy into one machine-readable record. The exact field-level contract lives in the API Catalog so this overview stays plain-language.
API SchemaDeveloper details
Field-level contracts, response examples, backend readiness gaps, and reviewer audit requirements live in the API Catalog so this overview stays focused on the buyer-facing trust boundary.