Ideas · Builder Notes
Kognita 0.5 begins: agents get an identity, limits and a taint label
The evening of 18 October: six 0.5 workstreams for Kognita alpha, covering agent identity, workload credentials, delegated authority, blast radius, taint isolation, containment and reversibility.
Why start 0.5 the same evening?
0.4 governed what an AI was used for. It said little about the agent itself. An agent with no identity is an anonymous script holding credentials, so 0.5 started with who the agent is and what it may do. The work was already planned in six slices, and 0.4 was out.
What went in?
- Identity and autonomy: every agent has an owner-approved deployment hash, an expiring review date, per-verb permissions and an autonomy level. Existing agents migrate to level 0 with no tools.
- Credentials and authority: hashed workload credentials verified at the gateway and MCP proxy, and a call needs both the human's entitlement and a live delegation. Tier 2 and above must use an enforcement point that cannot be bypassed.
- Limits: per-agent blast radius, rate limits, tool allow-lists and per-purpose field minimisation, all inside decide() so they are cited and replayable.
- Isolation: runs touching external content or client data carry sticky taint, can't call write tools, and can't reach the public lane afterwards.
And the last two slices?
Anomaly detection keeps per-agent baselines and contains an agent on volume spikes, privilege probing or odd tool sequences: kill switch, credential revoked, tools stopped, then an alert. Agent-to-agent delegation can only narrow authority, and kognita evidence authority traces an action back to a human. Tools declare whether they are reversible, recovery runs compensations in reverse, the MCP proxy cancels in-flight calls, and a threat model sits in the repo next to its tests.
What didn't hold up?
The first review pass started before midnight. It found the gateway could still forward a request after recording had flipped the decision to deny. I fixed that at 11:47 pm, and it was the first of many. The library path skipped the credential check when no credential row existed, a gap that lasted until 0.5.1.
What would I tell another builder?
Contain first, then alert. The alert is for the human. The containment is for the clock.
Sources
Kognita is an open-source alpha. This note comes from Kognita PR #54, Kognita PR #55, Kognita PR #56, Kognita PR #57, Kognita PR #58, Kognita PR #59, Kognita PR #60, Kognita PR #61, Kognita PR #62, Kognita PR #63 in the Kognita repository.
