Summary
The Kuai KB knowledge tier went live, serving the real database read-only behind a review board and audit log; the fetch tier lands sha256-checked records hourly.

The knowledge tier is live

Kuai KB — the knowledge core of OpenKuai — is now running on the box at :8787, serving the real kuai database through a read-only role that is enforced twice: at the database role level and again at the application layer. The review board, chat surface, and audit log ship with it.

What feeds it

The fetch tier lands sha256-checked raw lines hourly from named sources onto the append-only pad. A ledger applier applies KB SQL through the recorded ledger, so every row that enters the knowledge base can be traced back to the run that fetched it.

Retrieval runs over PostgreSQL + pgvector — HNSW for vector search, trigram for lexical matching, and a local reranker on top — exposed through MCP bindings that any prime-agent can call.

What this unblocks

Product enquiry answers are only as good as the knowledge they cite. With the KB tier live, the 1:1 WhatsApp agent draws from a reviewed, citation-backed source of product truth — and the roadmap items that depend on governed knowledge (the promotion fence, the published-set runner, the agent MCP-verbs door) now have a running surface to land on.