Skip to the content
Krizaka Agents

Proofs: what you can check yourself

§ 1 — What we can show

The code of Krizaka Agents is private. So this page lists only what anyone can open: blog chapters, with their dated measures and their limits, and merged pull requests of public repositories. A proof we cannot show is not cited here.

§ 2 — The chapters

The measures already quoted on this site: 190,000 → 40,000 tokens on a session's first turn · 92 PRs merged and 37 skipped in 48 h · 18 of 18 sessions finished.

Subject Chapter What you find
Architecture The architecture of krizaka-agents five checked views, the caps per session, two read-only audits (332 launches, 0 environment drift)
Rules that say no Working with agents real refusals, with their exit code
Coordinator Agents under a coordinator three failed tests, then a wave that lands; what is not proven
Start Every agent starts in the same world 190,000 → 40,000 tokens on the first turn; 18 of 18 sessions finished
Teams How our agent teams talk four audits in one day: 14, 8, 10 then 7 bugs
Founder and CTO How the CTO agent and I work who decides what
Trains All aboard the pull request queue
Cockpit One local cockpit the screen, figures of 15 November

§ 3 — Merged pull requests, in public

Krizaka's agents open pull requests on the organisation's public repositories, and the trains merge them. Two examples from 16 November, opened by the agents' app: blog PR 379 (a chapter) and PR 378 (the workflow pins update). Each public repository shows the history of its merged pull requests; that is the proof you can browse yourself.

§ 4 — What this page does not prove

The two 48-hour audits and the organisation-wide pull request counts rest on private logs and tickets: we quote them in the chapters, but you cannot replay them. We will make them checkable or withdraw them.