{
  "id": "page:docs-user-guide-ecosystem-kip-sdk",
  "_kind": "Page",
  "_file": "wiki/docs/user-guide/ecosystem/kip-sdk.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/user-guide/ecosystem/kip-sdk.md",
    "sourceKind": "repo-docs",
    "title": "kip-sdk — memory substrate (SPEC / DESIGN ONLY)",
    "displayName": "kip-sdk — memory substrate (SPEC / DESIGN ONLY)",
    "slug": "docs/user-guide/ecosystem/kip-sdk",
    "articlePath": "wiki/docs/user-guide/ecosystem/kip-sdk.md",
    "article": "\n[Docs](../index.md) › [Ecosystem](./overview.md) › kip-sdk\n\n# kip-sdk — memory substrate (SPEC / DESIGN ONLY)\n\n**Package:** no published package (spec-only) · **Path:** `packages/kip-sdk` · **Maturity:** Spec only — **not implemented**\n\n> **This is the most important thing to know about kip-sdk:** it is **spec/design only**. The package is **entirely Markdown** — there is **no `package.json`, no `src/`, and no shipping code**. You cannot install or run it. Treat every kip \"feature\" described below as **design intent, not a capability you have today**.\n\n**kip-sdk is the design for the *ideal core* beneath a future context-management product: a memory substrate that the rest of the ecosystem would consume. It is published as a specification so the design can be reviewed and grounded before any implementation exists.**\n\n---\n\n## On this page\n\n- [Status: spec only](#status-spec-only)\n- [What it designs](#what-it-designs)\n- [Stack role](#stack-role)\n- [What is actually in the package](#what-is-actually-in-the-package)\n- [Next steps](#next-steps)\n\n---\n\n## Status: spec only\n\nThe package's own status banner reads: \"Ship-quality v6 … Spec-only. Illustrative TypeScript interfaces are normative for *shape*, not implementation.\" There is no runtime. Any TypeScript you see in the spec describes the intended *shape* of interfaces — it is not code that runs.\n\n---\n\n## What it designs\n\n\"KIP\" stands for **K**(nowledge) / **I**(nference) / **P**(rovenance). The design describes:\n\n- A **git-substrate, bitemporal, signed-fact property-graph memory** whose unit of synchronization is an append-only, signed temporal fact.\n- **Git as the sole source of truth** — the graph is a deterministic, rebuildable *projection* of a grow-only, Ed25519-signed fact set (a CRDT under union), giving coordinator-free convergence.\n- **Hybrid retrieval:** vector search → graph expansion → reciprocal-rank fusion (RRF).\n- **Episodic / semantic memory** with salience and decay.\n\nA guiding principle from the design: \"memory is a substrate, agents are clients (the Letta pitfall).\" kip is positioned as a **library, not a runtime**.\n\n---\n\n## Stack role\n\nThe design (`docs/28-stack-integration.md`) positions kip as the **memory substrate** for the ecosystem: babysitter-sdk, genty, the adapters family, atlas, and kradle would all be producers/consumers/clients of its seams. Integration points are explicitly tagged in the spec as `ALREADY-IN-SPEC`, `GROUNDED-NEW`, or `SPECULATIVE` — a reminder that this is forward-looking design, not delivered integration.\n\n---\n\n## What is actually in the package\n\nThe package contains only Markdown:\n\n- `SPEC.md`, `PRIOR-ART.md`, `SCORECARD.md`\n- numbered design docs `docs/00..90`\n- adversarial design reviews under `reviews/iter-*-adversarial.md`\n\nNo `package.json`. No `src/`. Nothing to build or install.\n\n---\n\n## Next steps\n\n- **See where it would sit:** [Architecture & How It Fits Together](../architecture.md) (kip is shown as design-stage)\n- **Ecosystem map:** [Ecosystem Overview](./overview.md)\n- **What ships today instead:** [babysitter-sdk overview](./babysitter-sdk.md) and [Journal System](../features/journal-system.md)\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-user-guide",
      "to": "page:docs-user-guide-ecosystem-kip-sdk",
      "kind": "contains_page"
    }
  ]
}