Evidence record / omnigent
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-09-21-omnigent-policy-engine-hardening-spawn-bounds-persist-sub-agents-enforce-their-own-guardrails-verdi
Policy engine hardening: spawn bounds persist, sub-agents enforce their own guardrails, verdicts are attributed. Before v0.14.0 the spawn_bounds fan-out cap reset on every deployed tool call because each call built a fresh engine with an empty counter; the count now persists per session. v0.13.0 enforces a sub-agent’s own guardrails on its conversation. Policy API mutations are audit-logged and denials carry the owning workspace id.
Channel: tagged-release. Half: defect (closed). Date: v0.13.0 and v0.14.0.
Operator consequence: If you relied on spawn_bounds to limit fan-out on a deployed server before v0.14.0, it did not bind; re-check fleet cost for that period. On any tag through v0.14.0, a policy function that fails to resolve may not fail loudly (#6357 unreleased); test that each custom policy actually loads.
Receipt
Finding metadata
Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0
Finding ID: 2026-09-21-omnigent-policy-engine-hardening-spawn-bounds-persist-sub-agents-enforce-their-own-guardrails-verdi
Profile citations
- omnigent / claim / policy-engine-hardening
Source links
Primary links, including exact changelog lines when available.
Versioned source: run artifact