Sentinel™
Sentinel, part of SYNTHERA, is a security control plane for an agent estate: it watches tool calls and trajectories, classifies threats by deterministic pattern, shields data at the boundary, and streams governance events to a SIEM. It is deployed nowhere today, so read all of that as what the code does when you run it.
The outcome
A compromised or misbehaving agent keeps acting until a human notices – usually from a log review, long after the damage is done.
Tool calls and trajectories are watched and threat-classified as they happen and streamed to a SIEM, so misbehaviour is caught rather than reconstructed. That is what the code does; it is not yet what anything does for you. Sentinel runs in no environment, and containment is further out still — built and audited, and unreachable without a provisioned identity that has never been issued.
Sentinel is the enterprise wedge beside the stack: it consumes the same identities and the same audit-of-record every other layer does, and is where they turn into defence. Written and driven from its own entrypoints against a stubbed substrate; running in no environment today.
How it works
Sentinel is organised as six bounded responsibilities over an agent estate. Together they observe, classify, protect, report and contain. All six are written and driven from their own entrypoints; none of them is running in any environment, so read every card below as what the code does when you run it, not as something watching an estate today.
See the estate
Discover and map the agents, tools and trajectories actually running, so there's a live picture to defend.
Classify threats
Score tool calls and trajectories for threat patterns – prompt-injection, exfiltration attempts, protocol abuse – in real time.
Protect data
Shield sensitive data at the boundary, so a misbehaving agent can't quietly carry it out.
Catch protocol abuse
Intercept malformed or abusive protocol traffic before it reaches the tools an agent is calling.
Stream to SIEM
Emit governance events to a SIEM as CEF over TCP/TLS – real egress in the demo, not a dashboard you have to watch. Not connected to anyone's SIEM today, because nothing is deployed.
Contain – built, not shipped
Isolate an incident, revoke an identity, cut access. This is written, gated on a provisioned actor identity, and it writes an audit record carrying the substrate's own event id. It has never run outside a test: the mode that enforces it fails closed at boot on an identity that has not been issued, and it is deployed nowhere. Not roadmap, and not shipped.
Proof
Sentinel ships a one-command demo that boots the control plane keyless, and the SIEM egress it performs is real – CEF over syslog/TLS, the format your security team already ingests. What follows is that demo. It is the only place any of this has run: there is no deployment of Sentinel to point at.
agent:researcher → tool:http.fetch(internal-creds-store) DETECT ....... exfiltration pattern HIGH SHIELD ....... payload withheld at boundary SIGNAL ....... CEF event → SIEM sent # CONTAIN (revoke + isolate) – built and audited; not deployed anywhere
Threats are classified and streamed to your SIEM as they happen; containment is the next step, marked as such.
SYNTHERA is the trust layer for multi-agent systems: every agent gets a verifiable identity, scoped authority and a tamper-evident record, so software from different teams, vendors and frameworks can act on each other’s behalf without custom glue between every pair.