ONE REBEL · MANY PLACES
A connected app may prove only a reviewed public fact from its own experience. RAAP decides whether that proof belongs in a Rebel's life. Private activity never needs to travel with it.
HOW IT WORKS
The app checks its own quest, game, world or creator milestone under a reviewed rule.
Only the approved public summary and evidence commitments leave the app.
RAAP checks the issuer, selected Rebel, proof, replay state, Controller Epoch and transfer rule.
ISSUER DIRECTORY
Each app receives a separate identity and a narrow list of allowed public facts. Planned apps have no production key, no approved badge mapping and no issuing power.
Only the reviewed First Signal quest is mapped today.
message text · Discord identity · wallet data · form answers · moderation detail · points ledger
UI and evidence work may be built in Preview, but Production admission stays off.
raw movement telemetry · chat · private party data · unreleased world content · 3D-avatar ownership assumptions
UI and evidence work may be built in Preview, but Production admission stays off.
raw session telemetry · anti-cheat evidence · unrelated scores · arbitrary client claims
UI and evidence work may be built in Preview, but Production admission stays off.
adult content · private messages · sexual activity · moderation detail · private identity · relationship data
UI and evidence work may be built in Preview, but Production admission stays off.
unpublished assets · private drafts · credentials · customer data · arbitrary local build events
ONE CLEAR JOURNEY
Approved inside an app is not the same as admitted by RAAP. The interface must show the difference.
SHARED RULES