Governance & Provenance
Before an agent acts on your platform, every tool it can reach has been explicitly approved: pinned identity, typed capabilities, secrets it never sees, egress it can't exceed. While it acts, everything it does is written to an append-only provenance ledger. Capability is granted; nothing is assumed.
Applied to agent · incident-triage
What the policy gates
Only approved tool servers, with pinned identity and validated configuration, exist for the agent. Drift from the approved state is caught before execution.
Capabilities are enumerable, not implied: which queries, which namespaces, read or write. A capability that wasn't granted can't be exercised.
Credentials for your observability stack and clusters are held and injected by the runtime. They never pass through the agent's context.
The policy states what must be logged, not just what is allowed. An action that can't meet its audit obligation doesn't run.
Approve, enforce, record
Provenance isn't a logging afterthought bolted onto an agent framework. In Sentinel, the governed path is the only path: approval happens before execution, enforcement happens at execution, and the record is produced by the runtime itself.
A tool joins the platform the way a dependency should: reviewed, identified, and projected into a typed interface. Until that happens, no agent can call it, there is no ambient access to discover.
// capability is granted, never assumed const policy = await sentinel.policies.create({ name: "observability-readonly", tools: ["grafana", "kubernetes"], caps: ["query", "list"], // no writes audit: "every_call" }) → default: deny · exceptions: enumerated
When the agent asks for a tool, the runtime resolves the request against the registry and the active policy, then executes it on the agent's behalf. An out-of-policy request never runs, and the refusal itself becomes part of the record.
Tool calls and their outputs, model prompts and responses, evidence retrieved, configuration overlays, human interventions, each is an entry on a provenance ledger that only grows. From it you can reconstruct any investigation as one causal story: what triggered it, what the agent did, and how it reached its recommendation.
Trigger → evidence → report → review
Evaluation, unlocked
Approve tools before agents can touch them, fail closed on everything else, and keep a record no one can quietly rewrite.