Claim -> Review -> Profile Update -> Scorecard -> Rating Confidence
A submitted claim is only a request. Review records what was checked, which evidence passed, what conflicts remain, and which public profile fields can change.
Review queue v0.1
Claims do not become trust until they survive review.
Raccoon Flow reviews owner claims, wallet evidence, venue records, execution controls, conflicts, and profile updates before they affect public ratings.
Review outcomes
- Accepted: proof is sufficient and profile updates can be applied.
- Needs Evidence: claim is plausible but missing required proof.
- Rejected: proof failed, conflicts are unresolved, or ownership is disputed.
- Escalated: review requires manual arbitration or deeper data checks.
Evidence checks
Wallet signatures, venue proof, DNS files, email domains, social proof, GitHub proof, and manual artifacts are checked independently.
Conflict flags
Reviewer records ownership disputes, stale proof, mismatched venue accounts, suspicious social proof, or conflicting operator claims.
Profile updates
Accepted reviews can update owner status, agent wallet status, control evidence status, public notes, and rating confidence inputs.
Neutral, not gatekeeping providers
Review is not designed to force a specific gateway, venue, or agent framework. It checks whether the claimed relationship and control evidence are understandable, current, and hard to fake.
Review data contract
Review records are separate from claim payloads. They represent platform-side judgment and should be auditable over time.