Community-owned campaign
- Publish declared rules
- Accept member entries
- Resolve checks
- Lock and publish outcomes
For communities
Run your own campaigns, route members into partner opportunities and understand outcomes without exposing private participant records.
Partner ask
Northstar Playtest
Reviewed
Owned
Community round
Ready
Community Alpha
Source retained
Own the campaign or attach the route.
01 · Operate
Community work has two legitimate modes. Both keep rules and outcomes attached to the public campaign record.
One workspace
Two legitimate operating modes.
02 · Attribute
The source stays attached from project request through member entry and the final selected outcome.
03 · Respect the boundary
Operators get the readiness and attribution needed to act—not a window into every participant’s private evidence.
04 · Deliver and measure
Announcements, reminders and private status checks can happen in Discord while the web campaign remains the canonical record.
Optional interaction layer
The public web campaign remains canonical.
Route outcomes
05 · Publish
Owned campaigns, partner routes and public dates live together without turning community activity into a private-data feed.
Public community record
Community workspace
Create the workspace immediately. Verification protects publishing and sensitive controls before they become public.
Open the next operating surface
Create a community