Open sourceKIP
KIP. Every write a signed fact. Every read a pure function.
A grow-only set of signed facts, and one pure function that turns them into knowledge. Two agents on the same facts agree byte for byte. asOf answers any past moment; disagreement is a typed, queryable state. Pre-release; early access on request.
01The diagnosis
The failures already have names.
Context rot. Memory poisoning. Compaction that silently drops constraints. The field describes its memory failures precisely, and then reaches for the same cure: better retrieval over a mutable store.
A mutable store can quietly lie. What an agent knows should have the properties of a ledger.
kip (Knowledge / Inference / Provenance) is a signed, git-substrate, bitemporal, typed property-graph memory SDK: a durable memory layer for agents and applications where every fact is a signed, append-only record and reads are a deterministic projection over the fact set.
Bitemporal means valid time plus record time. Ask what was true last Tuesday, or what was believed last Tuesday: different questions, and KIP keeps them apart.
02Properties
Memory as a ledger.
Two layers. Underneath, a grow-only set of signed facts. On top, one pure function that turns the facts into the graph you read. Every property below falls out of that split.
- Signed, append-only
- In practice: no process, and no agent, can quietly edit what was known.
- Deterministic reads
- In practice: the same facts give the same answer, on any machine, every time.
- Typed conflicts
- In practice: a disagreement becomes a work item you can see and resolve.
- Bitemporal
- In practice: you can answer an auditor about what was true, or what was believed, last Tuesday.
- First-class forgetting
- In practice: a deletion request is honored on the record, provably.
- Git substrate
- In practice: memory you can back up, diff, and host anywhere git runs.
The mechanism behind each row (signatures, projections, bitemporal time) is specified in the design record.
03Interfaces
Two bins over one core.
KIP is a library, not a runtime. Two bins sit over the same core: the kip CLI for a human at a terminal, and kip-mcp, an MCP server exposing ten tools to an MCP-speaking agent. Both read and write the same signed graph.
Typed nodes, edges, and properties via putNode and putEdge; bounded typed traversal via query; retrieval via ask, lexical or --semantic, with contradictions between sources surfacing in the results. Schemas are versioned facts checked at read time, never a write gate. Integrity checking via fsck, which verifies that heads match the projection and every signature holds.
04Early access
Read it, then ask for it.
The design record runs to 36 spec documents, in the kip-sdk package on GitHub with the rest of the stack. KIP is not yet on npm; early access is by request.
05The other half
KIP is the data half of the argument. The process half is Babysitter.
Want deterministic memory operated for your domain? Request a demo.