Community
The people building things that last.
Saroir is not a network. It is not a feed. It is a workspace for contributors who want their work on record.
Every project here is a collaboration between people who found each other because of what they are trying to build, not who they already knew. Contributions are reviewed by people in the domain, not by algorithms. Credentials are issued when the work meets the standard, not when the submission count reaches a number.
How Saroir works
Every number on this platform has a definition behind it. Every process has a public record. Every standard is documented, independently verifiable, and owned by the community that maintains it.
This page explains how Saroir counts what it counts, how contributions are reviewed and accepted, and how the platform's promises are kept structurally rather than asked for on trust.
Community projects
Saroir is built by the community as much as it is built for the community. Two categories of project live on the platform. Each has different origins, different governance, and different credit structures. Both produce knowledge that belongs permanently to everyone.
Platform projects are defined by Saroir and maintained by the community. They are the infrastructure projects that keep the platform running and growing. The domain wallet system, the email marketing layer, the hiring pipeline, the university enrolment channel. Each is scoped and documented before it opens. Each carries founding contributor credits for the people who build it.
Community projects emerge from contributors and domain communities. A gap in verified open knowledge. A problem that needs structured community research. A standard that needs writing. Any contributor can propose a community project. Domain Moderators review the proposal and, if accepted, the project enters the community build queue with its own attribution record.
Company sponsorship is available for community projects. An organisation that wants to fund the community to solve a problem openly can sponsor an existing or new community project. The company allocates budget, and domain Moderators scope and approve the sponsorship before it goes live. The community works on solutions. The solution enters the permanent public record, available to every company and practitioner in the industry. The sponsoring company receives permanent attribution on the project timeline as the funder of that knowledge. Sponsorship does not grant the company ownership of the output, direction authority over the project, or access to contributor identities.
This model changes something structural about how industry knowledge works. Right now a company that cannot solve a problem internally hires a consultancy. The consultancy solves it, owns the methodology, and sells the same solution to the next company at full price. The knowledge never becomes public. On Saroir, the solution belongs to the community that built it. Every company in the industry can use it. The consultancy no longer owns the knowledge because the knowledge belongs to everyone.
This is not an argument against consultancies. It is a better model for them. A consultancy that contributes their methodology to the platform trades a private advantage that expires when someone else rediscovers it for a public advantage that compounds every time someone builds on it. The implementation work remains. The gatekeeping ends. And the agency anywhere in the world with genuinely better insight can demonstrate it to the entire industry, get permanent credit for it, and compete for implementation work on the strength of what they actually built rather than what they privately hold.
The implementation engagement does not disappear because the approach is public. Every company's infrastructure is unique. The integrations, the legacy systems, the internal constraints, the organisational context that no public record can capture. The consultancy implementing a validated Saroir solution works from a verified starting point rather than defending a methodology the client cannot independently assess. Less time convincing the client the approach is sound. More time on the work that actually requires expertise. No more frustrating cycles of change requests driven by doubt rather than need. A validated public approach is not a ceiling on the consultancy's value. It is the floor they get to start from.
Project moderation
Sponsored community projects are scoped by domain Moderators before going live. A company cannot sponsor a project that is proprietary research dressed as a community problem. If the problem genuinely belongs in the domain and the solution will genuinely be public, it goes on the page. If the company intends to patent or productise the solution, it does not. This constraint is visible. The reasoning is documented. The moderation is what keeps the category trustworthy.
Contributor activity
When you see a domain with 800 active contributors, that number means something specific. It is not a signup count. It is not a total account count. It is 800 people who have met a defined standard of contribution within a defined period of time. Here is exactly what that standard is.
A contributor is active if they have three or more accepted contributions in the past 12 months. That is the full definition. No formula, no weighting, no proprietary scoring. Three accepted contributions. Twelve months. Verifiable.
Contributors who joined recently or who have been quiet for a while are in one of two other states. Stale means a contributor has been on the platform for over a year with fewer than three accepted contributions, or has not contributed for 12 months. Inactive means a contributor has been stale for a further 18 months with no activity. Active counts reflect active contributors only. The methodology behind every domain count is linked directly from the statistic wherever it appears.
Neither stale nor inactive removes a contributor's record, their credentials, or their history on the platform. Those are permanent. Activity states describe only current engagement.
A contributor who becomes stale receives a single notification. It is sent once and not repeated regardless of whether the contributor responds. It is not a warning. It acknowledges that their record is waiting and that their domain is open whenever they are ready. A contributor who has two accepted contributions and is approaching stale status will see a single contextual note on login: that they are one contribution away from active standing. This is information. The contributor decides what to do with it.
A contributor who becomes inactive sees a simple banner on their next login explaining their status and a single path back. One accepted contribution returns them to active standing immediately. There is no waiting period and no reapplication process. The barrier to return is deliberately low.
The total grace period from joining to inactive status is 30 months. Twelve months to stale, eighteen further months to inactive. This is deliberate. Life intervenes. Intentions take time to become actions. The platform is patient by design.
The thresholds behind these definitions are not fixed by Saroir. They are founding defaults, set to give the platform a sensible baseline at launch. As domains mature, their communities may propose changes through the governance process. Any change is documented in the public record with a clear explanation of what changed, why, and when. The history of how the platform defines meaningful contribution is itself part of the platform's record.
Contribution review
Every contribution on Saroir goes through a review process before it enters the permanent record. The review is conducted by domain Moderators, verified practitioners whose own records are publicly visible and whose review decisions are permanently attributed to them.
A Moderator who accepts a contribution is staking their own record on that decision. A Moderator who declines a contribution provides a documented reason. The review process is not hidden behind an algorithm. It is conducted by people with genuine domain knowledge, and those people are accountable for what they accept.
The review criteria for each domain are documented in the domain's standards section. They are written by the domain community, reviewed by Moderators and Councillors, and publicly readable before you make your first contribution.
Credentials
A Saroir credential is a W3C Verifiable Credential signed with a cryptographic key. It contains a record of what was contributed, when it was accepted, who reviewed it, and the cryptographic proof that the record has not been altered since it was issued. It does not contain your name, your email address, or any personal information that connects your credential to your identity unless you choose to make that connection yourself.
Verifying a Saroir credential does not require trusting Saroir. The cryptographic signature is the verification. It is valid or it is not valid. There is no middle ground and no third party whose continued existence is required for the verification to work.
The technical standards underpinning Saroir credentials are fully documented. The specifications are public, the implementations are open source, and the verification tools are available to anyone.
Privacy architecture
Saroir is built privacy-by-architecture from the ground up. Your identity and your contribution record are structurally separated. They do not share a database. They do not share an encryption key. They are not joinable by a foreign key. A breach of one cannot expose the other.
Your contribution record is pseudonymous by default. What you build here is public. Who you are is yours.
The technical documentation for the privacy architecture is publicly available in the open source repository. It is not a policy document. It is a structural description of a system that can be independently audited. The tools to verify every privacy claim are publicly available.
Open standards
Every standard Saroir is built on is public, documented, and independently verifiable. The credential format is W3C. The identity layer is decentralised identifiers. The content integrity system is SHA-256 with OpenTimestamps anchoring. The review process is attributed and permanent.
None of this is proprietary. None of it requires Saroir's continued operation to remain valid. A credential issued today is verifiable in twenty years by anyone with access to the public specification, regardless of whether Saroir still exists.
That is not a confidence statement about Saroir's longevity. It is a statement about how knowledge infrastructure should work. It belongs to the person who earned it. Permanently. Independent of the platform that witnessed it.
Who maintains these standards
The founding standards on this page were written by Saroir before the platform opened. They define the baseline the community builds from.
From the point the platform opens, standards are maintained by the community. Domain standards are maintained by domain Moderators and Councillors. Platform-wide standards require a governance decision with a documented record. The history of every change to every standard is public and permanently attributed.
If you believe a standard is wrong, incomplete, or needs updating, the process for proposing a change is documented in the platform wiki. The proposal itself is a contribution. If it is accepted, it is in the record.
The wiki itself is a community project. It is not a deliverable with a completion date. It is infrastructure that grows as the platform grows. Every edit is attributed. Every change is versioned. Contributing to the wiki is a recognised contribution type on the platform and counts toward your record the same way any other contribution does. The people who maintain it are doing work that belongs in the permanent record of this platform.
Marks of contribution
Platform-wide recognition. Earned automatically through accepted contributions. Thresholds are set and owned by community governance, not by Saroir.
Mark 1 Contributor
Your first accepted contribution is where your record begins. It is the moment Saroir confirms that real work has been done and reviewed. Your public profile becomes visible, your credential wallet receives its first entry, and up to five founding invites unlock progressively as you continue contributing. Mark 1 is not a participation badge. It is earned through work that passed review by domain practitioners, not by an algorithm.
- First accepted contribution to a real project
- Public profile visible, credential wallet begins
- Up to 5 founding invites unlock as contributions are accepted
- Can create projects, join cohorts, apply for Cohort Lead
Mark 2 Contributor
At Mark 2, your contribution record has demonstrated consistent depth across the platform. Your work becomes visible to organisations with platform access as a verified, pseudonymous signal. They see contribution depth and domain breadth. They do not see your name or contact details. You also become eligible to take on Facilitator roles within projects and to move into the platform-wide facilitator path. Mark 2 is where the platform starts reflecting back what you have built.
- Governance-decided threshold met in at least one domain
- Pseudonymous signal visible to partner organisations
- Eligible for Founder-assigned project Facilitator role
- Eligible for grants from the Knowledge Treasury
Mark 3 Contributor
Mark 3 contributors have built a record across multiple domains that the governance community has defined as senior depth. At this level you become eligible to take on project management responsibility as a Cultivator PM, setting the direction and prioritising the work of an entire project. The platform surfaces you to teams that need someone with cross-domain range to lead.
- Higher threshold crossed across multiple domains
- Full platform access: every domain, cohort, and thread
- Eligible for Cultivator PM designation on projects
- Early cohort visibility and moderator application prompt
Mark 4 and above
Marks beyond 3 are defined and owned by the contributor community through governance votes. The platform provides the infrastructure. The community decides what level of contribution record earns each recognition. At the threshold the community sets for Mark 4, an optional path to platform moderation opens on your dashboard. You are never pushed toward it. If you choose to apply, existing moderators review you before any authority over other contributors' work is granted.
- Thresholds set by community governance votes
- Mark 4 unlocks the optional moderator application panel
- No ceiling: new marks defined by the community over time
How contribution thresholds are set
The mark thresholds on this platform are not fixed by Saroir. They are set by each domain community through the governance voting system and reviewed annually. The numbers you see today are the founding defaults, chosen to give the platform something to run on at launch. As domains mature and communities develop a better understanding of what meaningful contribution depth looks like in their field, those numbers will be refined. A domain with a high volume of short contributions may set a higher threshold. A domain where each contribution represents months of work may set a lower one. The threshold is a reflection of what the community has decided genuine depth means here, not an arbitrary number imposed from outside.
Project roles
Scoped to a specific project. Assigned within the project by the Founder or through the project's own processes.
Project Founder
The person who proposes a project is its permanent founding contributor. That record is cryptographically signed and Bitcoin-anchored at the moment the project is approved. It does not expire. If the project runs for ten years and the founder steps back after the first month, their founding record is intact and independently verifiable for the life of the platform. The Founder assigns a Cultivator PM to manage day-to-day direction and a Facilitator to keep the work moving, then holds the final confirmation that the project is ready to go public.
- Any contributor can propose a project, no minimum mark
- Permanent founding attribution on the project timeline
- Assigns Cultivator PM and project Facilitator
Cultivator PM
A Cultivator PM is the person responsible for where a project goes. They set priorities, manage the work queue, and decide when a goal is complete. The role requires the contribution depth that Mark 3 represents, which means the person making direction decisions has demonstrated cross-domain range before being trusted with it. There is one Cultivator PM per project. Their decisions on project direction are permanent on the timeline.
- Requires Mark 3+, assigned by Project Founder
- Owns project direction: backlog, goals, ticket closure
- One per project, no HR authority over contributors
Facilitator (Project-Scoped)
A project-scoped Facilitator keeps the work moving without controlling its direction. Where the Cultivator PM decides what gets built, the Facilitator makes sure the cohorts doing the building do not get stuck. If a project page shows that a Facilitator role is open, anyone can volunteer for it. No contribution record is required to facilitate. Taking on facilitation does not mean stepping away from contributing. Both paths run in parallel, with separate permanent records for each.
- No mark requirement for volunteer path, Mark 2+ for Founder-assigned
- Updates cohort progress, nudges stale members, flags blockers
- Contribution and facilitation records are separate and permanent
Cohort Lead
Every cohort has a Lead. This is the person who takes responsibility for the group's coordination within a specific ticket: who joins, when the work is complete, and when the cohort's report is ready to become part of the project's permanent record. The Cohort Lead does not set the project's direction. They own the work within their cohort and the moment of closing it. A Mark 1 contributor can hold this role. Running a cohort well is part of how contributors build the kind of depth that the platform recognises over time.
- Requires Mark 1+, emerges from within the cohort
- Approves join requests, initiates closure and report elevation
- Scoped to a single cohort, no project direction authority
Watcher
Watching a project means you are following it without yet contributing. You can see what the project is working toward, what has been completed, and where open problems remain. The way to move from watching to contributing is to attempt a ticket. There is no intermediate membership step. Saroir does not have a concept of joining a project as a member before doing any work. The contribution is the join.
- Any visitor or authenticated user, no approval or mark required
- Read-only: tickets, goals, cohort states, merged contributions
- Cannot see discussion threads, cohort chat, or project documents
Moderator ladder
Entry requires Mark 4+. An optional application prompt appears on the dashboard. Application reviewed by a Subdomain Moderator or above. Founding moderators are appointed directly by the Saroir team.
Platform role. Six levels. Single ladder. Each level expands scope and authority. Content review and quality decisions only. Entirely separate from governance.
L1 Moderator
An L1 Moderator reviews flagged content and makes initial decisions within one subdomain. This is the entry point of the moderator ladder and the place where the platform's quality standard is applied most directly and most often. Every decision is attributed to the moderator's cryptographic identity and is part of their permanent record.
- Scope: assigned subdomain only
- Reviews flagged content, makes initial approve or reject decisions
L2 Moderator
An L2 Moderator reviews content and also manages how that review work is distributed across the subdomain's L1 moderators. When the queue needs to be balanced, the L2 makes that call. It is an operational step before a quality oversight step.
- Scope: assigned subdomain only
- Everything L1 does, plus reassigns queue items to L1 moderators
L3 Moderator
An L3 Moderator adds quality oversight to the subdomain's moderation work. They review a sample of decisions made by L1 and L2 moderators below them. Those reviews feed directly into the scoring formula that determines whether lower-level moderators advance. The L3 level is where the moderation system becomes self-correcting.
- Scope: assigned subdomain only
- Peer-reviews L1 and L2 decisions, feeds scoring formula
L4 Moderator
An L4 Moderator has earned the authority to bring new moderators into the system. They review applications from contributors who want to join the moderation team in their subdomain. Every moderator on the platform was approved by someone at this level or above. Deciding who is trusted with review authority is a formal, permanent act.
- Scope: assigned subdomain only
- Approves new L1 moderator applications within subdomain
Subdomain Moderator
A Subdomain Moderator has full oversight of everything that happens within their subdomain: content, contributions, cohort disputes, and agent behaviour. They can override any decision made below them and are responsible for the guardrails that define how AI agents operate in their subdomain. Their scope is narrower than a Domain Moderator but their authority within it is complete.
- Full oversight of one subdomain: content, agents, disputes
- Overrides any L1 through L4 decision, sets agent guardrails
Domain Moderator
A Domain Moderator oversees the full domain: every subdomain, every project, every cohort, and every agent operating within it. They can suspend agent keys, override subdomain-level decisions, and approve the promotion of subdomain moderators. This is the highest level of the moderation ladder. The people who hold this role arrived here through every level below it, with a contribution record that the community defined as sufficient before any authority was granted.
- Full domain scope: all subdomains, projects, cohorts, agents
- Can suspend agent keys, approve Subdomain Moderator promotions
Facilitator ladder
Open entry: no mark requirement at any level. Anyone on the platform can volunteer to be a Facilitator if a project page shows the role is open. Facilitation and contribution run independently with separate permanent records.
Platform role. Five levels. Focused entirely on cohort health and momentum. Separate from the moderator ladder. Runs in parallel with the contributor path.
L1 Facilitator
An L1 Facilitator takes responsibility for one cohort. When a project page shows that a Facilitator role is open, anyone can step forward. No contribution record is required. Some people come to Saroir specifically to facilitate, the way a scrum master brings structure to a team without doing the technical work themselves. You watch the work, track where the group is in its progress, and surface anything slowing it down. If you also contribute to tickets, both records are yours. If you only facilitate, that record is yours too.
- Scope: one cohort, no mark or contribution requirement
- Tracks progress state, surfaces blockers to PM and moderator
L2 Facilitator
An L2 Facilitator manages the momentum of multiple cohorts simultaneously. Carrying the same responsibility across several groups develops a clearer picture of what causes cohorts to stall and what helps them move. The patterns that emerge across different teams become the knowledge that the facilitator path is built on.
- Scope: multiple cohorts simultaneously
- Appointed based on demonstrated L1 performance
L3 Facilitator
An L3 Facilitator does the work of facilitation and also teaches it. The knowledge of how to keep a cohort productive is not just applied at this level. It is passed to L1 and L2 facilitators who are still finding their approach. The platform's facilitation capacity grows through L3 facilitators working with the levels below them.
- Multiple cohorts plus training responsibility for L1 and L2
- First level where facilitation knowledge is formally transferred
Subdomain Facilitator
A Subdomain Facilitator oversees the health of every cohort in their subdomain. They do not run each cohort individually but they hold responsibility for whether the cohorts collectively are doing good work and moving at a reasonable pace. When a cohort in the subdomain is blocked, the Subdomain Facilitator is who the Domain Moderator hears from first.
- Scope: all cohorts within one subdomain
- Responsible for collective cohort productivity and progress
Domain Facilitator
A Domain Facilitator holds responsibility for the collaborative health of an entire domain. Every cohort, in every subdomain, across every project. This role works alongside the Domain Moderator: moderators handle what is produced, facilitators handle the health of the groups producing it. Both are necessary. Neither replaces the other.
- Scope: all cohorts across a full domain and its subdomains
- Works alongside Domain Moderator: quality vs collaborative health
Founding record
Founding record badges are permanent. They are historical credits that never expire, never change, and cannot be removed. They record who made Saroir possible.
Founding Team
The founding team built the platform and operates it. During the closed beta they review every application, issue every invite, and handle every administrative decision. As the community grows, those responsibilities transfer to elected moderators, domain councils, and the governance council. The founding team's permanent designation is as the origin of the platform's infrastructure, not as its permanent governors.
- Performdigital Private Limited, led by the platform's founder
- Full admin access during founding period
- Operational authority transfers to community as the platform scales
Founding Moderators
The founding moderators were chosen before the platform opened to contributors. They are domain practitioners who know their field well enough to recognise when real work has been done and when it has not. Before the community is large enough to produce moderators through the ladder, they set the standard that all future moderators will be measured against. Every contribution accepted or rejected in the early days of Saroir carries the decision of one of these people.
- 7 moderators at launch, appointed directly by Saroir team
- Operate as Subdomain or Domain Moderators from day one
- Approve the first L1 moderator applications as the platform scales
Founding Contributors
Founding contributors joined before the platform was fully open. Their records began before most people had heard of Saroir. The Founding Contributor badge is permanent on their credential record. It cannot be purchased, applied for, or earned after the closed beta ends. The people who helped shape what Saroir became carry that in their record for the life of the platform, alongside every contribution they have made since.
- Joined during closed beta, permanent badge on credential record
- Up to 5 founding invites, unlocking as contributions are accepted
- Access to governance discussions shaping the Platform Constitution
Founder
The Founder badge belongs to the person who originated Saroir before it existed as a platform. Who held the idea, made the first decisions, took the first risks, and built the foundation everything else stands on. It is a permanent record of origin. A Founder may hold active governance roles or they may not. The founding credit is independent of any current role.
- Permanent record of who originated the platform
- Independent of any current governance role
Tier 1 Founding Partner
Founding Partner Tier 1 organisations are among the first eight companies to formally support the Saroir knowledge commons. The majority of their annual contribution goes directly to the Saroir Knowledge Foundation to fund contributor grants, domain research, and platform development. Company representatives participate as contributors. They earn marks. They form cohorts. The company affiliation is on the record but it does not grant any special access to contributor identities or override the common good review that every project must pass. Founding designation is permanent regardless of what comes next.
- First 8 organisations with advisory seats and domain shaping
- Full Signal API access including subgraph licence
- Permanent founding designation regardless of future tier changes
Tier 2 Founding Partner
Founding Partner Tier 2 organisations are part of the first hundred companies to formally commit to the Saroir knowledge commons. Their contribution routes to the same Knowledge Foundation as Tier 1, and their founding designation is equally permanent. The difference between tiers is access depth, not the permanence or intent of the commitment.
- First 100 organisations who committed early
- Signal API read access, permanent founding designation
- Same permanence as Tier 1, different access depth
About the two tiers
Both tiers hold rate locks that never expire. Both are in the founding record permanently. The distinction between them is not a rank. It is a reflection of the different roles they played in making the platform possible.
Active governance
Active governance roles are accountable and renewable. They can be held, lost, or changed as the platform evolves. Holding a founding record badge does not automatically confer an active governance role. They are earned or elected independently.
Separate appointment. Not linked to the mark ladder or moderator ladder. Being constituted as the platform reaches scale.
Councillor
Councillors hold the platform's constitutional authority. Any change to the locked sections of the Platform Constitution requires Councillor consent and a thirty-day public comment period open to the full contributor community. Councillors are appointed initially and elected by the contributor community as the platform grows. The role exists to ensure that what is locked stays locked until there is genuine community will to change it, expressed through a defined process rather than a unilateral decision.
- Constitutional amendments, platform-level policy decisions
- Term-based and renewable, community can choose not to re-elect
Ambassador
Ambassadors represent the contributor community in governance decisions that cut across domains. Where domain councils advocate for their specific field, Ambassadors ensure that platform decisions reflect the community as a whole. The role is about coordination and representation, not authority over any single domain or domain's work.
- Cross-domain coordination and community representation
- Facilitates coordination across domain councils
Champion
Champions are the formal voice of a specific domain in platform governance. When a governance decision affects how a domain operates, the Champion represents the contributors who work in it. The role requires deep domain knowledge and the trust of that domain's community. Champions exist so that domain-specific context is never lost in platform-wide decisions made by people who do not work in that domain.
- Formal voice of a specific domain in governance
- Requires deep domain knowledge and community trust
Organisation roles
External to the contributor community. Companies and institutions interacting with the platform in a formal capacity.
Company Representative
Company representatives on Saroir are contributors first. They earn marks the same way everyone else does: through accepted contributions reviewed by domain practitioners. The company affiliation is a badge on their record. On their full profile all badges are visible. Within a specific project, they can choose whether that badge appears next to their name. When a company representative proposes a project and the company also sponsors it, both facts are permanently on the project's public timeline. The community knows exactly who proposed it and who funded it.
- Contributors first, earn marks through accepted work
- Company badge visible on profile, toggleable within projects
- No access to contributor PII, cannot bypass common good gate
University Partner
Universities on Saroir have free access, permanently. That is a structural commitment built into the platform's model, not a time-limited offer. The contribution records students build here do not belong to the university. They belong to the students. When a student graduates or leaves, their credential record travels with their cryptographic identity, not with their institution login. The university's value is in connecting students to real work. The record of that work is the student's to keep.
- Free access permanently, a structural commitment
- Verifies student enrolment only, no access to student contributions
- Student records belong to the student, not the institution
Knowledge Foundation
Saroir Knowledge Foundation
The Saroir Knowledge Foundation receives the majority of everything the platform earns. It is a separate legal entity with its own bank account, its own trustees, and its own governing charter. The Foundation funds contributor grants, scholarships, domain research, and platform infrastructure. No business decision by the commercial entity can redirect Foundation funds. The separation is not a policy commitment. It is a structural one, enforced by separate legal registration, separate banking, and separate payment routing.
- Separate legal entity from Performdigital Private Limited
- Section 8 Company (India), Stichting (Netherlands), 501c3 (US, future)
- 5 trustees, governing the Knowledge Treasury and grant allocation
- Foundation funds structurally inaccessible to commercial entity
The people who built these standards did not have to document them publicly. Neither did the ones before them. Knowledge shared openly belongs to everyone who needs it and finally finds it.
Closed Beta · 2026
Ready to build something?
Whether you are an experienced practitioner or a new contributor looking for real-world collaboration, Saroir has a place for you.