Request -> Evidence -> Review -> Scorecard -> Rating history
A missing proof request should not disappear into a private inbox. Resolution records what was submitted, who submitted it, how review judged it, and what changed publicly.
Evidence resolution v0.1
Trust gaps should close through a visible workflow.
Evidence resolution connects open requests, submitted proof, reviewer checks, scorecard impact, and rating-history updates into one inspectable trust-ops record.
Resolution states
- Open Request: missing proof is visible in the request queue.
- Evidence Submitted: owner, provider, venue, adapter, or reviewer submits proof.
- Under Review: checks are pending or partially complete.
- Verified or Rejected: submitted proof passes or fails review.
- Scorecard Updated: confidence, caps, blockers, or dimensions change.
- Rating History Appended: any material rating or review-state change gets a public changelog entry.
Proof enters the system
Accepted proof can be a wallet signature, venue account proof, execution-control proof, DNS file, website proof, adapter output, or attestation.
Evidence becomes judgment
Reviewers check authenticity, freshness, ownership, conflicts, permission scope, and whether the evidence actually resolves the request.
Trust objects change
Verified evidence can update scorecard confidence, remove caps, close requests, change profile fields, and append rating history.
Resolution endpoints
- /evidence-resolution.schema.json - resolution schema v0.1.
- /evidence-resolution.example.json - example resolution for Momentum Router control proof.
- /evidence-requests.json - open request queue.
- /scorecards/momentum-router-vault.json - scorecard affected by the example.
- /rating-history.json - changelog for material rating changes.
Owners should know exactly how to improve trust.
This is the operational heart of the platform: a provider can see what blocks investability, submit the missing proof, and watch the public trust graph update.