Upgrade to Pro — share decks privately, control downloads, hide ads and more …

KYB: Shared Operational Memory for AI Agents

Sponsored · SiteGround - Reliable hosting with speed, security, and support you can count on. →

KYB: Shared Operational Memory for AI Agents

A 12-slide technical introduction to KYB (Know Your Business), a Git-backed knowledge base, incident tracker and task store for AI agents.

Covers the Git canon and derived search index, BM25 plus optional semantic retrieval, version history, archiving and retraction, task deadlines, and CLI, HTTP API, MCP and web-console interfaces. Based on KYB v0.3.3. Examples are synthetic; no private operational data or new performance claims.

Project: https://github.com/alex09x/kyb
Website: https://kybmemory.com
Presentation archive: https://zenodo.org/records/23911562
Software archive v0.3.3: https://doi.org/10.5281/zenodo.23683977

By Alexander Panasenko: https://prod.codes/about/

Alexander Panasenko

November 03, 2026

Transcript

12 slides
  1. Knowledge between sessions 01 02 03 An agent learns The

    session ends The record remains A session discovers a deployment rule or resolves an incident. Another agent needs the same context in a different checkout. KYB keeps a searchable record outside the model's context. KYB v0.3.3 / Source and scope 02
  2. Three kinds of operational records Knowledge How a service works,

    where it lives, and why a decision was made. Incidents What broke, its impact, the workaround, and the resolution. Tasks An owner, progress, blockers, and an optional deadline. KYB v0.3.3 / Source and scope 03
  3. Git is the source of record Git Clients CLI HTTP

    API MCP Web console KYB server Markdown and commits Rust service Read and write routes Search index Rebuilt from history One Markdown file per entry. One commit per change. KYB v0.3.3 / Source and scope 04
  4. Lexical and semantic search Question Candidate search Rank fusion Read

    Terms or phrasing BM25 and optional vectors Reciprocal ranks Results The embedding model runs on the server CPU. Without it, lexical search remains available. KYB v0.3.3 / Source and scope 05
  5. Closing work keeps its outcome Knowledge Update or retract Retraction

    removes the record from default search. Git retains its earlier versions. Incident Resolve with an outcome The live file leaves the tree. The final report remains in default search. Task Complete or drop The task leaves the active queue. Its final outcome remains searchable. KYB v0.3.3 / Source and scope 06
  6. Current answers and historical context Default search History search Latest

    content for each active key, plus final archived tasks and incidents. Search earlier versions of records. Inspect one key with kyb history. kyb query "deployment" KYB v0.3.3 / Source and scope kyb query "deployment" --history 07
  7. A changed route, with its earlier record Synthetic example Revision

    A Revision B api-route Public API uses /v1 api-route Public API uses /v2 The same key identifies the entry. A commit identifies its version. kyb history api-route kyb get api-route --at COMMIT_SHA KYB v0.3.3 / Source and scope 08
  8. Task deadlines stay visible A task carries its own date

    Due dates can be hard or provisional. An event can determine the final date. Closing still requires an outcome. Illustrative task metadata due: 2026-12-01 hard: false remind_days: 7 assignee: agent-a The CLI and read responses surface due items. The console includes a by-date view. KYB v0.3.3 / Source and scope 09
  9. One service, several interfaces CLI MCP HTTP API Console People,

    scripts and agent shell workflows Agents that speak HTTP-based MCP Programmatic reads and writes A browser view of records and deadlines Deploy with the project's setup guide and the toolchains you need. KYB v0.3.3 / Source and scope 10
  10. Operating boundaries Retrieval Evaluate results against your own questions and

    records. This deck makes no general speed or agent-productivity claim. Access Authentication is off by default. Choose a trusted bind, configure tokens, and use TLS beyond a trusted network. Provenance History records changes. It does not certify the truth of a claim or prove who made a direct Git edit. KYB v0.3.3 / Source and scope 11

Other Decks in Programming