VERDICT
Governance before execution.
An open-source pre-deployment decision engine.
Verdict evaluates supported infrastructure-as-code changes against declared policies and conditions before execution—while there is still an opportunity to govern what happens next.
BEFORE THE CHANGE
Governance has more leverage before execution.
Infrastructure delivery workflows can turn proposed configuration changes into deployed infrastructure quickly.
Organizations may already have policies, security requirements, architectural constraints, and approval expectations that define what should and should not happen. But identifying a problem only after infrastructure has been deployed changes the task from governing a proposed action to responding to something that has already occurred.
Verdict is designed to bring the governance decision into the pre-deployment path, where supported changes can be evaluated before execution.
EVALUATE BEFORE EXECUTION
Put a governance decision in the delivery path.
A supported infrastructure change is proposed.
- Proposed change
- Policy evaluation
- Governance decision
- Recorded reasoning
- Delivery response
Verdict evaluates the change against the declared policies and conditions that apply to the evaluation, then produces a governance decision with reasoning that can be inspected and preserved as part of the audit record.
That decision can be incorporated into the delivery workflow so execution can respond to the governance result—including blocking execution when the configured enforcement path requires it.
CAPABILITIES
More than a single policy check.
Verdict supports the work around a governance decision as well as the evaluation itself.
Evaluate before execution
Evaluate supported infrastructure-as-code changes against declared policies and conditions before those changes proceed to execution.
Validate and test policy
Validate policy artifacts and test expected behavior before relying on them in an infrastructure delivery workflow.
Simulate decisions
Explore how policies and context evaluate without requiring each simulation to represent a live deployment decision.
Examine coverage
Analyze how policy conditions map to supported governance and control-framework coverage.
Explain decisions
Inspect the reasoning associated with a governance decision so the result can be understood rather than treated as an unexplained allow-or-deny output.
Inspect the audit record
Review preserved evaluation records to examine what was evaluated, what decision was produced, and the reasoning associated with it.
Verify what follows
Compare subsequent supported infrastructure plans against prior governance decisions to identify relevant change or drift after the original evaluation.
IN THE DELIVERY WORKFLOW
Bring governance closer to infrastructure delivery.
Verdict is designed to operate before supported infrastructure changes are executed.
It can run locally during development or within CI/CD workflows, allowing governance evaluation to occur closer to the infrastructure changes being considered.
- Proposed infrastructure change
- Verdict
- Governance decision
- Delivery proceeds according to the configured response
This gives teams a decision point before execution while preserving the reasoning and audit information associated with the evaluation.
EXPLICIT AUTHORITY
AI may advise. AI may not authoritatively govern.
Within Verdict, authoritative governance decisions are produced through deterministic policy evaluation—not probabilistic inference.
Probabilistic analysis may inform risk or provide advisory information where supported, but it does not override the condition evaluation that determines the governance decision.
Authority remains explicit. Decisions remain reproducible and explainable.
BUILT IN THE OPEN
Inspect it. Run it. Integrate it.
Verdict is open source under the Apache 2.0 license and publicly available as a Python package and GitHub Action.
You can inspect the source, run Verdict locally, or integrate it into supported CI/CD workflows.
GET STARTED
Put Verdict in front of a supported infrastructure change.
Start with the open-source package, inspect the source, or work through the technical documentation.