Governance
Formal issuance and production certificate status are shown on Rank and Status. Document version badges do not indicate issuance status.
The VGO is the machine-world visibility governance system, initiated and maintained by Omseek.
Roles
- Maintainers: decide releases, merge proposals and protect conceptual coherence.
- Contributors: propose definitions, metrics, research, examples and corrections.
- Reviewers/Domain experts: may provide non-binding technical or industry review.
Decision model
Community contribution does not imply automatic acceptance. Maintainers may accept, revise, defer or reject proposals. Material changes should include rationale in the repository history.
Neutrality of the system
The system should distinguish general VGO methodology from Omseek-specific product features. Omseek implementations may extend the system, but proprietary behavior should not be presented as a universal VGO requirement.
Public evaluation
Published evaluation cases should follow EVALUATION-PROTOCOL.md: disclose the protocol version, sample denominator, four conclusion counts, missing cases, and conflicts of interest. Dual independent coding is required. Omseek private scores do not resolve disagreements. External comments do not imply endorsement of VGO.
Action and automation proposals
Proposals for new action methods should identify inputs, a responsible actor, a concrete output, verification evidence, failure modes and any required human review. Automation proposals must state which steps can be automated and which require approval or override. Proprietary Omseek behavior must not be claimed as a universal VGO requirement.
Versioning
- Patch: wording/clarification without conceptual change.
- Minor: backward-compatible additions.
- Major: material changes to scope, pillars or definitions.