01

For communities

Turn community reach into attributable access.

Run your own campaigns, route members into partner opportunities and understand outcomes without exposing private participant records.

Attribution topologyROUTE / COMMUNITY-ALPHA

Partner ask

Northstar Playtest

Reviewed

Owned

Community round

Ready

Community Alpha

Source retained

Own the campaign or attach the route.

Member entries32
Eligible26
Selected10
Project opportunity → attributed route → member outcomePrivate evidence stays private

01 · Operate

Own the campaign or route the opportunity.

Community work has two legitimate modes. Both keep rules and outcomes attached to the public campaign record.

One workspace

Two legitimate operating modes.

Run01

Community-owned campaign

  • Publish declared rules
  • Accept member entries
  • Resolve checks
  • Lock and publish outcomes
Route02

Partner opportunity

  • Review the project ask
  • Create an attributed source
  • Share with members
  • Track readiness and outcomes

02 · Attribute

From partner ask to sourced outcome.

The source stays attached from project request through member entry and the final selected outcome.

  1. 01Project requestReviewed
  2. 02Source linknorthstar/community-alpha
  3. 03Member entries32 sourced
  4. 04Eligible26 ready
  5. 05Awaiting review4 entries
  6. 06Selected10 seats

03 · Respect the boundary

See readiness without reading private passports.

Operators get the readiness and attribution needed to act—not a window into every participant’s private evidence.

Community can see

  • Readiness counts
  • Campaign participation
  • Source attribution
  • Aggregate outcomes

Community cannot see

  • Private entry answers
  • Unrelated wallets
  • Full passport history
  • Project-only review evidence

04 · Deliver and measure

Meet members where they are. Keep the outcome attributable.

Announcements, reminders and private status checks can happen in Discord while the web campaign remains the canonical record.

Discord delivery

Optional interaction layer

01Campaign announcement
02Apply or continue
03Private eligibility check
04Reminder
05Result message

The public web campaign remains canonical.

Route outcomes

Entries sourced
32
Eligible
26
Selected
10
Attribution
Retained

05 · Publish

A public home for community access.

Owned campaigns, partner routes and public dates live together without turning community activity into a private-data feed.

Community workspace

Give members a route that stays visible.

Create the workspace immediately. Verification protects publishing and sensitive controls before they become public.

Open the next operating surface

Create a community