Knowledge scattered across mail, meetings and systems drifts — unseen, unstructured, unchecked. And agents are reading and writing it now. Kyyn gives agents and humans one validated ground truth to build together: the agent proposes; you accept.
It evolves out of sight — in inboxes, decks and docs nobody re-reads, in formats too loose to hold structure. Nobody notices when it goes wrong.
Every agent you run tomorrow acts on what the KB says today. Typed, validated facts keep them honest — a chat log or vector store can't.
Review isn't just a gate. Every accept extends the context you and your agent share — you see what it learned; it learns what you value.
Who it serves, why it exists, and a live todo list — grown from mail, calendar and transcripts. The inbox is evidence; the KB is the concise, current memory.
Research project, product catalogue, family archive, investment thesis — the schema travels with the KB, no domain compiled into Kyyn itself.
Curate only strategic accounts and material opportunity changes from Salesforce — the translation happens at the normal review seam.
CVs, interview transcripts and scorecards land as evidence; candidates, rounds and offers become typed records — every decision traceable to the notes behind it.
Invoices, statements and collection threads curated into obligations with owners and due dates — chased from the record, not the inbox.
Standups, boards and decision threads distilled into milestones, risks and commitments — the project's actual state, not its last status deck.
Runbooks, vendors, renewals and incident history as living records — the tribal knowledge that usually walks out the door with people.
Every customer's promises, escalations and renewals curated from mail and meetings — the context a handover actually needs.
Distilled from the doctrine that governs the code. Each one is enforced by mechanism — the accept gate, the repo format, or the plugin boundary — not by convention. All six serve one goal: knowledge that stays correct while agents and humans build it together.
Every change — records and schema alike — stages on a scoped Git proposal ref. Nothing reaches the checkout branch until the owner accepts the diff.
Facts, schema, sources and receipts are ordinary files in an ordinary repo — portable, diffable, and readable without kyyn. Git history is the audit trail.
A KB is a (tree, validator) pair: acceptance runs the tree's own committed WebAssembly validator over the whole result, and pull is fail-closed. Any machine replays the same verdict.
One binary supplies proposals, validation, queries, MCP and the web UI. Every plugin — first-party included — is a tap the KB pins at a commit; even the starter template is fetched, not embedded.
Sources preserve original provider bytes as hashed, immutable evidence. Deciding what evidence means happens only at the reviewed curation seam — which is also how two KBs federate.
A schema change and the record rewrites it demands land as one atomic proposal — whole-tree validation forces it. The diff is the migration; the commit is the schema version.
Load-bearing, not aspirational. Each principle is mechanism — remove one and the accept gate, the repo format, or the plugin boundary stops holding. The guarantees below are where that enforcement surfaces.
Register the MCP server and an agent can inspect the schema, curate evidence, and stage proposals. Only you accept them.
Kyyn is under active development. Join the waitlist and we'll reach out as onboarding opens.