Source evidence
Contracts, SLAs, invoices, work product, vendor communications, acceptance criteria, IP language, and delivery evidence enter the protocol.
Turn contracts, SLAs, invoices, delivery evidence, IP obligations, service performance, and vendor actions into hard gates, payment decisions, audit trails, escalation paths, and governance-ready records.
Workspace state
LiveWorkspace state
Sources, graph, scoring, actions, and exports remain connected.
Live operating state
Actions update the graph, dashboard, reports, and exports.
Operating flow
The protocol structures source evidence, applies its method, records management actions, and updates the resulting operating state.
Contracts, SLAs, invoices, work product, vendor communications, acceptance criteria, IP language, and delivery evidence enter the protocol.
Vendors, obligations, SLAs, invoices, deliverables, owners, approvals, penalties, compliance gates, and evidence become mapped.
MCOS calculates compliance, invoice approval status, SLA risk, penalty exposure, audit readiness, and vendor health.
Teams validate SLAs, block invoices, release payment, confirm IP assignment, assign remediation owners, and escalate issues.
Actions update invoice status, vendor score, compliance health, SLA risk, audit log, penalty exposure, and governance report.
Ask about vendor status, SLA gates, or invoice holds. Answers are grounded in the live governance engine state, not a static snapshot of the contract.
Workspace modules
Dashboards and exports matter. The deeper value is the structured evidence, operating state, decision logic, and management workflow that can be revisited and updated.
Shows vendor health, SLA compliance, invoice status, unresolved gates, exposure, and executive governance state.
Compares evidence against contractual SLAs, acceptance criteria, delivery obligations, and performance thresholds.
Blocks or releases payment based on evidence, obligations, approvals, and unresolved governance conditions.
Verifies whether IP, work product, ownership, deliverables, and transfer obligations are satisfied.
Turns unresolved risks into remediation owners, escalation actions, and tracked governance outcomes.
Creates a tamper-resistant decision trail for payment, compliance, approvals, exceptions, and audit review.
Management actions
Validations, owner assignments, risk decisions, and approved changes are operating events. They should update the underlying state rather than remain comments beside a static report.
Validate SLA
Recalculates state
Block Invoice
Recalculates state
Release Payment
Recalculates state
Confirm IP Assignment
Recalculates state
Escalate Vendor Issue
Recalculates state
Operating view
Sentinel Governance turns vendor and contract evidence into payment gates, compliance checks, escalation paths, and audit-ready decisions.
Governed output layer
Sentinel Governance produces vendor compliance scoring, invoice decision logs, SLA evidence packages, IP checks, escalation paths, and board-ready audit trails.
Output package
The Engine
The hard gates, the MCP tool surface, the deterministic engine and the audit chain, with a human on the loop issuing clearances — and the three ways to run it. Below that, the end-to-end journey from what you hand it to the governed endpoint.

Click to view full size — ecosystems in · one /mcp · human on the loop · three ways to run it

Click to view full size — the seven-step journey, ending at one /mcp endpoint
Enforcement, against a named target
PwC and OpenAI now sell a native, agentic finance function built on one lab. When an AI agent books real numbers, an auditor cannot accept “the model decided” as a control. That is exactly the gap Sentinel closes: hard gates the agent cannot bypass, a tamper-resistant decision trail, and a live operating state that recalculates as actions occur.
The most audit-sensitive systems in the company, wired to a single lab, inherit that model's pricing, access, and gating exposure and still cannot prove control. Sentinel supplies enforcement the client owns, independent of which model ran the step.
Enforce-before-execution
GSIs and platform vendors are security-reactive: they detect and remediate after execution. Sentinel is enforce-before-execution. The gate is open or it is not, and every decision is written to a tamper-evident SHA-256 audit chain agents cannot override.