Governance
How the ZeroHuman protocol is maintained, moderated, and evolved. Designed for durability, transparency, and community participation.
Principles
Open by default
The protocol spec, reference implementation, and governance process are all public.
Git-native
Proposals are discussed in GitHub Discussions. Accepted changes become PRs. The authoritative state lives in Git.
Deterministic
Conflict resolution, precedence, and validation rules are explicit and testable.
Backwards compatible
Breaking changes go through a formal RFC process with migration guides.
Governance Tracks
The protocol separates governance into three tracks to keep discussions focused.
Protocol Governance
Changes to schemas, precedence rules, required files, and validation rules.
- ·Schema changes require an RFC with at least 14-day comment period
- ·Breaking changes require major version bump
- ·New primitives require community consensus via Discussion
- ·All changes must include migration guides
Ecosystem Governance
What qualifies as a listing, moderation rules, verification, and deprecation.
- ·Listings must include a valid zerohuman.yaml manifest
- ·All packages are validated against the protocol schema automatically
- ·Verification requires passing security audits
- ·Official status requires maintainer review and ongoing commitment
- ·Deprecated packages are flagged but not removed
Framework Governance
Runtime behavior, loaders, validators, SDKs, and reference implementations.
- ·Reference implementation changes follow semver
- ·SDK releases are tested against protocol conformance suite
- ·Runtime behavior changes require backwards compatibility
- ·New adapters must pass integration tests
Trust Levels
Every package in the ecosystem has a trust status managed by the middleware layer. These states are assigned based on validation, audits, and maintainer verification.
Proposal Process
Open a Discussion
Start a new thread in the appropriate governance category.
Community review
Minimum 14-day comment period for protocol changes.
Create a PR
Once consensus is reached, formalize the change as a pull request.
Merge & release
Approved changes are merged, tagged, and documented.
Join the conversation
All governance happens in public. Proposals, debates, and decisions are open for anyone to participate in.