KSoR

<p align="center">
  <img src="https://raw.githubusercontent.com/panaversity/ksor/main/repo-image.png" alt="KSoR — open, vendor-neutral knowledge infrastructure for AI-native organizations" width="100%">
</p>

[Watch the video: KSoR Introduction](https://www.youtube.com/watch?v=EeTGuQJbHCg&t)

# KSoR

**Open, vendor-neutral knowledge infrastructure for predictable enterprise and education agentic systems.**

A company cannot expect predictable AI-agent behavior if its agents operate from scattered, conflicting, or outdated knowledge.

An education institution cannot deliver an organized AI-assisted course if its tutors, teaching assistants, and assessment agents operate from different curricula, sources, or rules.

> **You cannot build predictable AI systems on an undefined source of truth.**

A **Knowledge System of Record (KSoR)** solves that problem by giving an organization **one governed, authoritative knowledge record** that humans and AI agents operate from.

For an enterprise, that record can contain approved:

- policies,
- procedures,
- rules,
- methods,
- standards,
- definitions,
- controls,
- decision criteria,
- and institutional knowledge.

For an education institution, it can contain approved:

- curriculum,
- learning objectives,
- concepts and definitions,
- pedagogy,
- course sequence,
- source material,
- assessment rules,
- grading criteria,
- and the current course version.

The AI can still reason, explain, personalize, and adapt. What it should not have to invent is **which institutional or academic knowledge is authoritative**.

> **Enterprise agents need a KSoR so they operate from the same governed institutional truth.**  
> **Education agents need a KSoR so they teach from the same governed academic truth.**

KSoR does not make a probabilistic language model deterministic. It makes the **knowledge environment governed, bounded, traceable, and testable**: which source is authoritative, which version is current, who approved it, who may see it, which knowledge may be retrieved, and when an agent must abstain instead of improvising.

The framework reduces to three commitments:

> **One authoritative record.**  
> **One governance boundary.**  
> **Many open projections.**

And one operating principle:

> **Govern knowledge once. Project it many ways.**

The result is not merely a documentation site, knowledge base, vector database, RAG system, or MCP wrapper.

> **KSoR is an open knowledge infrastructure framework that makes governed knowledge usable by people, AI agents, and other knowledge systems without giving any one vendor ownership of the record.**

<p align="center">
  <a href="https://docs.google.com/presentation/d/1lLF3PZBQ3vbeSdCKqPbMDTN9a6bgP6msDvbBIrEdeko/edit?usp=sharing">
    <img src="https://raw.githubusercontent.com/panaversity/ksor/main/slides-ksor-8-concepts.png" alt="KSoR in eight concepts — title slide: One Book Everyone Must Follow" width="90%">
  </a>
</p>

<p align="center">
  <strong><a href="https://docs.google.com/presentation/d/1lLF3PZBQ3vbeSdCKqPbMDTN9a6bgP6msDvbBIrEdeko/edit?usp=sharing">KSoR in eight concepts →</a></strong><br>
  17 slides, one hospital, plain language, no code. One authoritative record, what belongs in it, provenance, the governance boundary, abstention, citation, how new knowledge gets approved, and the many open projections that read it — the deck to open when you are introducing KSoR to a team.
</p>

---

## Start here

All you need is [Node 24 or newer](https://nodejs.org/en/download). Use whichever package manager you already
have — npm, pnpm, or bun — and the project it creates will use that same
manager everywhere:

**npm**

```bash
npx @panaversity/ksor@latest init my-knowledge-sor
cd my-knowledge-sor && npm install && npm run dev
```

**pnpm**

```bash
pnpm dlx @panaversity/ksor@latest init my-knowledge-sor
cd my-knowledge-sor && pnpm install && pnpm dev
```

**bun**

```bash
bunx @panaversity/ksor@latest init my-knowledge-sor
cd my-knowledge-sor && bun install && bun run dev
```

Open `http://localhost:3000`. The site is running, and it reloads as you edit
the Markdown files in `knowledge/`. What you have is a complete, ordinary
project — a working website, a CI workflow, and instructions for coding agents
— and it is entirely yours: nothing is downloaded at build time, and nothing
phones home. The five documents in it are KSoR's own starters, there to be
deleted as your knowledge arrives.

Ask it to publish and you meet the point of all this:

```console
$ pnpm exec ksor build
ksor build: 6 document(s), 5 admitted to a machine surface
```

Six documents, five admitted. The one you just wrote is a `draft`, so it
reaches no surface an AI agent reads — not `llms.txt`, not the markdown twins,
nothing — until a human approves it. Approve it and the count moves.

**[Hello world](docs/tutorials/01-hello-world.md) walks that end to end in
about fifteen minutes**, from an empty directory to your own coding agent
answering from your

... (truncated)