Candidate -> Evidence Request -> Evidence -> Review -> Scorecard -> Rating
The request queue is the action layer between candidate transparency and accepted evidence. It makes trust gaps specific enough to resolve.
Evidence request queue v0.1
Missing evidence should become an actionable request.
Evidence requests tell owners, providers, venues, adapters, and reviewers what proof is missing, which proof types are accepted, what the gap blocks, and which trust fields can change after resolution.
What each request records
- Who should respond: owner, provider, venue, adapter, or reviewer.
- Accepted proof types and the candidate/submission/profile it supports.
- What the missing proof blocks: verification, confidence, listing, or capital routing.
- Which trust fields change after resolution.
Owner claim proof
Frontier Volatility needs owner-controlled proof before owner verification or stronger trust scoring can move.
Open
High priority
Agent wallet signature
A wallet signature can connect the agent identity to a vault or operating wallet and later map to ERC-8004 identity evidence.
Open
Identity
Execution-control proof
Gateway, venue-native permissions, scoped keys, or smart-contract policies can satisfy control evidence requests.
Open
Gateway optional
Request endpoint
- /evidence-requests.json - public request queue v0.1.
- /evidence-resolution.example.json - evidence resolution example v0.1.
- /evidence-resolution.schema.json - evidence resolution schema v0.1.
- /candidates.json - candidate queue with request ids.
- /evidence.example.json - reusable evidence object examples.
- /review.example.json - review example that can consume resolved evidence.
The platform tells you how to become more trustworthy.
This is the difference between a score and a trust system. A candidate can see exactly what to submit, what it unlocks, and what remains blocked.