occ / governance
How trust works
OCC is an open network. Anyone can participate. But not all knowledge is equal. The following rules define how packs earn trust, how disputes are resolved, and who is accountable for what.
Capital can fund the commons.
It cannot govern the truth layer.
01 / principles
Anyone can create a pack.
Network-approved packs require formal review.
Reviewers cannot approve their own packs.
Sources must be public and traceable.
Every approved pack must have a version history.
Packs can be disputed, deprecated, or revoked.
Money can fund work and infrastructure, but cannot determine knowledge approval.
The founder has no special vote on knowledge approval.
02 / roles
Anyone who signs in via GitHub. Can vote on packs.
Earned automatically on first pack submission. Can propose and submit packs.
Earned when first pack is approved. Can submit formal reviews on packs they did not create.
Reached automatically or by nomination. Can approve, deprecate, or revoke packs. Accountable for registry integrity.
Roles are assigned automatically when rep thresholds are reached. They never decrease. Registry Steward can also be nominated manually.
03 / pack lifecycle
Approved packs can move to DISPUTED, DEPRECATED, or REVOKED. Revocation is public and permanent in the transparency log.
04 / future
OCC is designed to evolve toward an international foundation with transparent governance, public review records, open infrastructure, and accountable stewardship. The governance model described here is the first iteration — intended to be simple, honest, and replaceable by a more formal structure as the project grows.