# KB Philosophy

`kb` exists because maintaining a knowledge base is a pain—and most teams never do it well, or at all. The goal is simple: you get a knowledge base for free, as a side effect of doing your real work. No double entry, no extra process, no guilt about docs getting stale. If you use `kb`, you never have to "maintain" a knowledge base; it just happens.

## Guiding Principles

### Accretion, Not Overhead

`kb` bets that if you make it easy enough, knowledge will naturally accrete. Small facts, decisions, and context get captured as you work. If something is wrong or out of date, it's easy to fix or delete. No knowledge is sacred—if it's wrong, kill it. The goal is a base that stays useful because it's never a burden.

### Descriptive, Not Prescriptive

kb doesn’t tell you how to work. It just records what happened.

Your agent talks to a separate harness backed by a semantic graph built from code and markdown. No workflows, templates, or process layer on top.

The [Agile Manifesto](https://agilemanifesto.org) still says it best:

Individuals and interactions over processes and tools  
	Working software over comprehensive documentation  
	Customer collaboration over contract negotiation  
	Responding to change over following a plan

## Change Is the Default

Everything changes. `kb` expects facts to go stale, mistakes to happen, and priorities to shift. That's normal. It's easy to update, delete, or correct anything. The only "process" is: keep moving forward, and let the knowledge base reflect reality as it changes.

## Transparency Without Effort

`kb` keeps a record of what happened, when, and why—automatically. You can always see how a decision was made, or why something changed, without digging through chat logs or old docs. If you want to go deep, the history is there. If you don't care, you never have to look.

KB Philosophy

kb exists because maintaining a knowledge base is a pain—and most teams never do it well, or at all. The goal is simple: you get a knowledge base for free, as a side effect of doing your real work. No double entry, no extra process, no guilt about docs getting stale. If you use kb, you never have to “maintain” a knowledge base; it just happens.

Guiding Principles

Accretion, Not Overhead

kb bets that if you make it easy enough, knowledge will naturally accrete. Small facts, decisions, and context get captured as you work. If something is wrong or out of date, it’s easy to fix or delete. No knowledge is sacred—if it’s wrong, kill it. The goal is a base that stays useful because it’s never a burden.

Descriptive, Not Prescriptive

kb doesn’t tell you how to work. It just records what happened.

Your agent talks to a separate harness backed by a semantic graph built from code and markdown. No workflows, templates, or process layer on top.

The Agile Manifesto still says it best:

Individuals and interactions over processes and tools  
Working software over comprehensive documentation  
Customer collaboration over contract negotiation  
Responding to change over following a plan

Change Is the Default

Everything changes. kb expects facts to go stale, mistakes to happen, and priorities to shift. That’s normal. It’s easy to update, delete, or correct anything. The only “process” is: keep moving forward, and let the knowledge base reflect reality as it changes.

Transparency Without Effort

kb keeps a record of what happened, when, and why—automatically. You can always see how a decision was made, or why something changed, without digging through chat logs or old docs. If you want to go deep, the history is there. If you don’t care, you never have to look.