R∴
Contribution OS setup
Meridian Systems · Tom Askew (administrator)
Save & exit
✓ Organization ✓ First mission ✓ Participants ✓ Integrations 5 Contribution principles 6 Launch

Contribution principles

These rules protect honesty. They are visible to every participant and enforced by the platform — including against administrators.

Contributions may be anonymousAnonymity is permanent and technically enforced; it cannot be lifted later, even by admins.
Private contributions stay hidden until a room beginsPrevents anchoring on early or senior voices.
Raw contributions visible to facilitators onlyUnchecked: the mission team sees raw contributions once a room opens.
AI interpretations require participant confirmationThe AI may classify or summarize, but the contributor must confirm before it counts.
Contribution content ✓Participation frequency ✓ Dissent or objections ✓Room attendance ✓
This exclusion is written into the workspace policy and surfaced in the privacy center. It cannot be silently changed — edits appear in the audit log.
Setup summary
OrganizationMeridian Systems · B2B SaaS · 450 people · EMEA/NA
First missionIncrease qualified pipeline by 20%
Sponsor / ownerD. Reyes / S. Okafor
Decision ownersJ. Lindqvist +1
Contributors22 invited · 3 reviewer roles
ConnectedSlack · HubSpot · GA4 · Search Console
DeferredSalesforce · Jira · Zoom · Teams · Google Ads · Asana
First question“What creates activity but not qualified demand?”
First Contribution RoomMon Jul 27 · 10:00 CET
Mission examples used earlier
  • Increase qualified pipeline by 20%
  • Reduce customer acquisition cost
  • Improve customer retention
  • Launch a new market
  • Build a new website and demand system
Launch the first mission →