Knowledge as Code

A pattern for building knowledge bases that verify themselves, resist decay, and serve both humans and machines from plain text files.

Canonical pattern definition: https://knowledge-as-code.com

The Pattern

Knowledge as Code applies software engineering practices to knowledge management. The knowledge lives in version-controlled plain text files. It is validated by automated processes. It produces multiple outputs from a single source. And it actively resists becoming outdated.

Six Properties

Property	What It Means	In This Project
Plain text canonical	Knowledge in human-readable, version-controlled files. No database, no CMS, no vendor lock-in.	Markdown and YAML files in `data/`
Self-healing	Automated verification detects when knowledge drifts from reality. Flags decay before humans notice.	Verification scripts and AI-assisted freshness checks
Multi-output	One source produces every format needed — human-readable, machine-readable, agent-queryable.	HTML site, JSON API, MCP server, SEO bridge pages, sitemap, `llms.txt`
Zero-dependency	No external packages. Nothing breaks when you come back in a year.	One Node.js script, no `package.json`, no `node_modules`
Git-native	Git is the collaboration layer, audit trail, and deployment trigger.	Issues, PRs, CI/CD, version history — all through Git
Ontology-driven	A vendor-neutral taxonomy maps to domain-specific implementations.	1 Obligations across 4 Instruments

The Ontology

Every Knowledge-as-Code project has four entity roles:

Authority → Instrument → Term → Obligation

Role	This Project	What It Is
Primary	Obligation	Stable anchors that persist when sources change
Container	Instrument	Grouping entities that contain provisions
Authority	Authority	Source entities that produce containers
Secondary	Term	Mapping entities connecting containers to primaries

Primaries are stable; containers are unstable. When a instrument is amended, its terms change, but the underlying obligations persist.

Standing on Shoulders

File over App — Steph Ango on durable digital artifacts as files you control
Docs as Code — Managing documentation with version control, pull requests, CI, plain text formats. Write the Docs community
Living Documentation — Cyrille Martraire on documentation that evolves with the system it describes
GitOps — Git as single source of truth with automated drift detection. Coined by Weaveworks (2017)
Anti-entropy — Distributed systems pattern for detecting and repairing state divergence (Dynamo, Cassandra)

Live Examples

AI Tool Watch

AI model capabilities across 12 products

Every AI Law

Global AI regulatory landscape

Meeting Standards Reference

Meeting facilitation standards

Ecosystem

Knowledge as Code — The pattern definition and community hub
Every AI Law — Global AI regulatory landscape — statute reference spine for PubLedge JIAs
gist (Semantic Arts) — Upper ontology PubLedge schemas bind to (CC-BY 4.0)
Skill Provenance — Manifest + hash integrity pattern PubLedge ships from day one
Siteline — AI agent readiness scanner for websites

Get Started

git clone https://github.com/snapsynapse/knowledge-as-code-template.git
cd knowledge-as-code-template
node scripts/build.js
open docs/index.html

Template: github.com/snapsynapse/knowledge-as-code-template

Knowledge as Code is a PAICE.work project.