koi-gov

KOI Governance & Naming Conventions

Repository Status: Active Development
Lead Maintainer: Gregory Landua
Last Updated: April 16, 2025

---

🌱 Overview

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.

💡 New to KOI or GitHub?
This repo is for everyone — not just coders! If you’re a scientist, community builder, designer, or strategist, KOI helps you contribute documents that are clear, consistent, and findable. Start with our Semantic Naming via Properties guide.

---

📌 Key Documents

📄 Document	🧭 Purpose
KOI.naming-convention-manifesto.v1.0.0.md	Defines the KOI naming system and versioning rules
CONTRIBUTING.md	How to propose naming conventions or contribute documents
changelog.md	Tracks all changes and updates to KOI naming standards
semantic-naming-properties.md	How to use Notion, GDocs, or GitHub with KOI structured naming

---

📚 Repository Structure

KOI-governance/
│
├── README.md
├── KOI.naming-convention-manifesto.v1.0.0.md
├── CONTRIBUTING.md
├── changelog.md
├── docs/
│   └── semantic-naming-properties.md

---

🚀 How to Contribute

We enthusiastically welcome contributions from everyone! Here's how you can help:

• Review the KOI Manifesto: Understand how our naming system works.
• Use KOI Naming: Apply it to any document you create for Regen Network.
• Propose Improvements: Open issues or PRs to improve naming clarity or structure.
• Join the Conversation: Attend KOI sync calls or participate in async discussions.

---

📖 Semantic Naming Quick Reference

Naming Structure

[relevance].[type].[subject].vX.Y.Z

Relevance Levels

• core: Foundational, widely used, and trusted.
• relevant: Actively cited, helpful in ongoing work.
• background: Informative, ambient, or historical.

Object Types

• memo: Strategic or operational documents.
• analysis: Data-driven or qualitative breakdowns.
• notes: Informal, exploratory documentation.
• decision: Records of formal decisions.
• readme: Descriptive documentation of a folder or pattern.

Semantic Versioning

• vX.0.0: Major conceptual shifts
• vX.Y.0: New content or moderate updates
• vX.Y.Z: Minor or editorial changes

---

🧠 Property-Based Naming Format (New)

When using modern tools like Notion, you can separate the KOI title and metadata:

• Human-friendly title: e.g. "Q2 Strategy – Commons Activation"
• Properties:
  • KOI Name: core.objective.q2-commons-activation.v2025-Q2.v1.0.0
  • Type, Version, Relevance, Status (stored in tool-native fields)

➡ See: semantic-naming-properties.md for examples in Notion, GDocs, and GitHub

---

🌿 Why KOI Matters

Implementing clear, semantic naming isn't trivial—it's foundational. It:

• Facilitates trust and clarity across distributed teams
• Enables decentralized governance and documentation
• Supports AI and agent-based coordination with structured knowledge

Let’s tend our shared garden of meaning, one clear name at a time. 🌱