Norm
Be precise
Prefer contracts and invariants over marketing language. If a claim matters, link to the canonical source.
OpenAgent · Community
A constellation of
implementers
OpenAgentID evolves in the open. If you're building a verifier, integrating an SDK, or reviewing the contract, this is where you plug in.
Discussions
Public
Decisions
Recorded
Bias
Implementer-first
A closer lookA decision, held together.
Independent participants contribute to a shared threshold. Authority is established by the configured policy.
- 01Independent participants
- 02Bring the shares together
- 03Meet the threshold
- 04One verifiable result
§ 01Entry points
Start here
Four paths into the ecosystem depending on what you're trying to do: ship code, review changes, propose a contract update, or understand how decisions get recorded.
GitHubSource code, issues, pull requests, and discussions. The repository history is the record.Source + issuesRFCsThe public process for proposing, reviewing, and recording changes to the specification.Contract changesContributingA guide to contributing across spec, SDKs, docs, and the website — with a bar focused on verifiability.How to helpGovernancePrinciples and pipeline for decisions: public review, recorded outcomes, implementer-first priorities.Decision model
§ 02Norms
How to contribute well
A community standard is only as good as its review culture. These norms keep proposals precise and verifiable.
Norm
Optimize for verifiers
Review proposals through verifier behavior: what should pass, what should fail, and why.
Norm
Keep it public
Design discussions should happen in issues and PRs so implementers can audit the record.
Norm
Treat security seriously
Threat model and authority boundaries belong in the conversation any time verification rules change.
Next
Bring edge cases early
If you found an ambiguous verifier rule, an interoperability issue, or a missing failure mode, open an RFC so the record stays public and implementers can review it.