Use cases

What the kernel does in 0.2.2, applied to four kinds of work. The demo and the benchmarks use one corpus, the MCP specification. The scenarios below show how the same mechanism applies to other text; they are not measured results.

Three papers, a conclusion resting on each. One paper is retracted: only the conclusion resting on it falls.

Proposed use case, not a measured study.

Scientific reviews

A team of agents reads a set of papers and writes conclusions, each resting on exact quotes. A paper is retracted. The owner withdraws its text, and the kernel finds the conclusions that lost their support and leaves the rest standing.

Details
What the kernel does here
Accepts only quotes that occur byte for byte in the paper’s text. Finds the conclusions registered on a withdrawn paper without asking a model. Keeps the journal, so the state before and after can be checked. Since 0.2, sbgk audit-read fallen names each conclusion that lost a ground, the quotes that went and why, the quotes under it that still stand and what to reread, from the journal and with no model.
What to know
Convert PDF and Word to text first. The journal keeps the full text of the papers: share it only when their licenses allow.
Several agents around the kernel. The kernel leases each task to one agent at a time; a lease that runs out is taken back and the task goes to another agent.

Teams of AI agents

Several agents, possibly of different models, read and write on the same corpus. The kernel hands each agent one bounded task at a time, accepts what passes its checks and records which conclusions rest on which quotes.

Details
What the kernel does here
Leases each task to one agent at a time and takes expired leases back. A retry with the same submission id returns the original receipt. Gives each agent its own token and role. The owner closes the run when it is complete.
What to know
Up to 8 agents at once are recommended, as measured on 0.1. The server has no TLS: for other machines use a secure tunnel or a TLS proxy, and keep agent tokens secret.
A code file and two findings. The finding whose quote is in the file is accepted; the made-up one, whose quote is in no file, is refused. When the file changes, the findings are checked again.

A working example in the repository (examples/findings-gate), on the library.

Checking code and findings

An example in the repository puts a security review’s findings on code files through the kernel. Every step of a finding carries a quote copied byte for byte from the file. Of three findings, one is made up: it cites a real file and real lines, and its quotes are in no file.

Details
What the kernel does here
Refuses a finding whose quote is not in the source files and stores nothing of it. When a reader goes silent, the task goes to another after the lease. When the files change, the findings quoted from the old bytes lose their grounds and are checked again on the new ones.
What to know
On sbgk audit-serve the file set is fixed when a run starts; this example puts new versions in through the library.

examples/findings-gate

A folder of documents, each pinned by the hash of its bytes. A clause of one document is withdrawn: only the claim resting on it falls.

Documents and policies

The journal keeps the full text of the files it reads, so share it only with people allowed to read them. --docs takes a folder of UTF-8 text files, such as contracts, policies, logs or code. Agents answer with exact quotes of them. When a clause is withdrawn, the claims that rested on it lose their support.

Details
What the kernel does here
Pins each file by its path in the folder and the SHA-256 of its bytes, and leaves out hidden files, service folders and links. Since 0.2, sbgk audit-read coverage says from the journal what each list item, paragraph and table row of the files came to, and sbgk audit-proof cuts one conclusion with everything it rests on into a file that sbgk audit-proof-verify checks alone.
What to know
Convert PDF and Word to text first. The file set is fixed when a run starts. A quittance shows that a record was in the journal at a signed checkpoint, not that it stands now.