Governance

OCC is designed around a single core principle:

Capital can fund the commons. It cannot govern the truth layer.

Roles

Role	Rep threshold	Permissions
User	0	Sign in, vote on packs
Contributor	1 (first submission)	Propose and submit packs
Pack Creator	25 (first pack approved)	Submit formal reviews on packs (not their own)
Registry Steward	500 or nominated	Approve, deprecate, or revoke packs

Roles are assigned automatically when rep thresholds are reached and never decrease. Registry Steward can also be nominated manually. The founder has no special vote on knowledge approval.

Review process

1. A Pack Creator submits a pack — it enters CANDIDATE status.
2. A Registry Steward moves it to UNDER_REVIEW.
3. One or more Pack Creators submit formal reviews (APPROVE, REQUEST_CHANGES, REJECT).
4. If changes are requested, the creator updates the pack and re-submits.
5. A Registry Steward approves or rejects based on the review record.

Pack Creators cannot review their own packs. A single formal review does not automatically trigger status change — it is advisory input for the Registry Steward.

Disputes and revocation

Any approved pack can be moved to DISPUTED if community members identify problems with sources, accuracy, or coverage. Disputes are resolved publicly via GitHub Discussions.

REVOKED is permanent and public. It appears in the transparency log and in /api/registry.json.

Future governance

OCC is designed to evolve toward an international foundation with:

• Independent governance board
• Public review logs
• Cryptographic signatures on all approved packs
• Append-only transparency log
• Domain-specific maintainer councils

This document describes the first-iteration governance model, intended to be honest, simple, and replaceable.