Bosun
Agent action governance mesh.
It controls what agents do, passing every action through Fathom-powered policy before execution.
What Bosun does.
Nautilus controls what agents know, and Bosun controls what they do. Every action, including tool calls, escalations, handoffs, and external API requests, passes through governance rules before execution.
Agents must declare their context sources when taking action. "I'm acting on output from Agent A's session X." This creates an audit trail of claimed provenance, letting Nautilus retroactively correlate exposure state.
Generates compliance attestations across agent fleets. Built on Fathom's CLIPS engine and Ed25519 signing infrastructure. Every authorized action is cryptographically attested and logged.
Bosun owns the action governance layer.
Each tool in the Kraken stack owns a single concern. Bosun sits at the action governance tier — adopt it on its own, or descend the whole column.
Nautilus governs what agents know, covering data access, classification, and clearance envelopes. Knowing the right data and doing the right thing are separate problems. An agent with valid clearance for a dataset can still take an unauthorized action with that data: escalate to the wrong team, call an external API it should not touch, or hand off context to an agent that is not cleared to receive it. Bosun closes that gap. It sits at the action boundary the same way Nautilus sits at the data boundary.
The core mechanism is context declaration. Before an agent takes any action, it declares the provenance of the context it is acting on, for example “I am escalating based on output from Agent A’s session 47.” That declaration gets logged as an audit trail. Bosun does not verify provenance in real time, since that would require it to broker all inter-agent data, which is Nautilus’s job. Instead, it records the claim. Nautilus can then correlate after the fact: was Agent B actually authorized to see Agent A’s session 47 output? If not, the attestation chain is broken and the action is flagged. This catches lateral movement patterns that neither system would detect alone.
Policy evaluation runs on the same Fathom engine that powers Nautilus, with sub-millisecond decisions, CLIPS-based deterministic rules, and Ed25519-signed attestations for every authorized action. There is no probabilistic filtering and no LLM in the policy decision path, so a deny stays a deny. The rules are auditable, the decisions are reproducible, and the attestations are cryptographically verifiable after the fact.
Bosun is currently in design phase. It is being developed alongside Fathom and Nautilus as the action governance layer of the stack. The architecture is specced, the Fathom integration points are defined, and the context declaration protocol is drafted. Active development begins once Nautilus v0.3 stabilizes the data broker interfaces that Bosun depends on.