Do we need to change our agent framework?
No. Spctre is stack-neutral. You can start with CLI hooks, SDK ingestion, REST calls, MCP tools, or framework adapters without migrating to a new runtime. Start in observe mode to build confidence, then move selected agents to enforcement when your policy workflow is ready.
How long does integration take?
Most teams have audit log ingestion running within a day. Start in observe mode, then move selected actions to gateway enforcement after validating policy impact against real traffic.
What does enforcement actually block?
Spctre evaluates the agent, connector, action, environment, and runtime context against your active policy bundle. A DENY halts the action and records the decision. A REVIEW pauses the workflow and routes it to a human approver before the action can proceed. An ALLOW records the decision and lets the agent continue.
What audit records are kept for each decision?
Every decision record includes the agent identity, connector, action, environment, runtime target, matched policy references, reviewer state, decision status, timestamp, and artifact hash of the active policy bundle. Review decisions additionally store the approver identity, rationale, and resolution time.
Can Spctre support human review before an agent acts?
Yes. REVIEW decisions pause the workflow, route the action to a named approver, and preserve the full claim, resolution, reviewer identity, rationale, and policy references in the operations ledger. Approvers can act from the Spctre UI or via API.
What does Spctre not do?
Spctre governs agent actions — it does not train models, route LLM traffic, or manage cloud infrastructure. It also does not replace your provider invoices: cost and token figures in the dashboard are directional governance telemetry, not billing records.