Where CKB is going
Today your agent asks CKB questions. This page describes where that goes next.
Not shipped yet. This is direction, not a promise with dates. Everything below is written in future tense on purpose.
An after-change check
ckb changes will report what your agent actually touched, once it has made a change: affected tests, public symbols that changed (flagged as a possible contract change — it is a heuristic, not a guarantee), related decisions, and suggested reviewers. It will work on uncommitted changes, not just committed diffs.
An activity ledger
A local record of what your agent asked CKB, how long each call took, and how much it returned — so you can see what evidence your agent actually got. It stays on your machine.
Honest benchmarks
We will measure an agent working with CKB against an agent working alone, on real sessions, by joining the activity ledger with session transcripts — and publish how we measure it.
Not planned for 1.x: a browser UI, and per-call "tokens avoided" numbers.
A console
A console to see what CKB knows about your system, and what evidence your agent received before it acted.
Your agent will state its intent
Instead of your agent asking CKB one question at a time, it will state what it is about to do, and CKB will assemble the relevant evidence itself.
Knowledge you can correct
Corrections to what CKB knows — ownership, decisions — will be kept in versioned files in your repo, not buried in a database.
Tell us what you need
This direction isn't final. If you have a use case it should cover, say so.