Repository Status: Active Development Lead Maintainer: Gregory Landua Last Updated: February 12, 2026
Welcome to the KOI (Knowledge Organization Infrastructure) Governance Repository. This space holds the canonical semantic naming conventions and governance documents stewarded by Regen Network Development, PBC.
KOI is our collective infrastructure for creating coherent, transparent, and actionable knowledge objects within Regen Network. By maintaining semantic clarity, we enable decentralized teams, AI agents, and community participants to collaborate meaningfully.
| Document | Purpose |
|---|---|
KOI.regen-naming-convention-manifesto.v1.1.0.md |
Defines the KOI semantic naming schema, versioning practices, object types, and governance process. |
CONTRIBUTING.md |
Explains how to propose, pilot, and ratify changes to the KOI naming schema. |
changelog.md |
Tracks all approved changes and updates to the naming conventions. |
koi-gov/
│
├── README.md # You are here
├── KOI.regen-naming-convention-manifesto.v1.1.0.md # Current manifesto
├── KOI.regen-naming-convention-manifesto.v1.0.0.md # Previous version (archived)
├── CONTRIBUTING.md # Contribution guidelines
├── changelog.md # Record of changes
└── LICENSE # MIT License
We enthusiastically welcome contributions from everyone! Here's how you can help:
- Review the KOI Manifesto: Familiarize yourself with the current naming conventions.
- Open an Issue: Suggest new prefixes, types, or relevance tiers.
- Create a Pull Request: Propose changes formally with your semantic reasoning and pilots.
- Participate in Governance Discussions: Join our regular calls or async forums to discuss proposals and feedback.
See CONTRIBUTING.md for detailed instructions.
[relevance].[type].[subject].vX.Y.Z
core: Fundamental, actively used, essential to strategic decisions.relevant: Informative, actively cited, influential in ongoing work.background: Contextual, supportive, historical, or ambient reference.
| Type | Description |
|---|---|
memo |
Structured strategic or operational documents. |
analysis |
Data-driven or qualitative deep dives. |
notes |
Informal or exploratory ideas and documentation. |
decision |
Official organizational decisions. |
readme |
Canonical documentation for directories or patterns. |
strategy |
Forward-looking strategic frameworks or business models. |
docs |
Reference documentation, specifications, or guides. |
feedback |
Structured feedback on proposals, products, or processes. |
research |
Investigative or exploratory research output. |
press |
External-facing communications and media materials. |
prompt |
AI prompt templates, agent configurations, or instruction sets. |
transcript |
Meeting or conversation transcripts, typically AI-generated. |
vX.0.0: Major conceptual shiftsvX.Y.0: Minor, meaningful content updatesvX.Y.Z: Editorial, non-conceptual adjustments or clarifications
Implementing clear, semantic naming isn't trivial—it's foundational. It:
- Facilitates trust and clarity within distributed teams and collaborators.
- Supports adaptive governance and decision-making.
- Empowers human-AI collaboration through semantic precision.
Let's tend our shared garden of knowledge and coherence together.
Questions? Reach out directly to Gregory or open an issue in this repository.
Thank you for nurturing our collective coherence and stewardship!