Ideas · Builder Notes
Blast-radius limits, rate limits and field minimisation
Kognita alpha 0.5 enforces per-agent blast-radius limits, rate limits, tool allow-lists and purpose-specific field minimisation inside the decision.
What was wrong?
Even a well-authorised agent can do too much, too fast.
What did I build?
A per-agent BlastRadius is enforced in decide(), independent of run budgets, including per-minute and per-hour limits. Agents have a tool allow-list, and a per-purpose field allow-list minimises records, with the minimisation evidenced. Access windows can be tied to events.
An agent's maximum damage became a configured, evidenced number.
What surprised me?
Limits live in the decision, so they are cited and replayable like any other rule.
What's still open?
Concurrent calls could race the counters, which was fixed with atomic admission.
What would I tell another builder?
Decide your blast radius before you need it.
Sources
Kognita is an open-source alpha. This note comes from Kognita PR #57 in the Kognita repository.