The evaluation planner

One action.
A plan to test it.

Turn an integration idea into a focused local evaluation. Choose a starting point, name its limits, and take a test plan back to your team.

Build your plan

An execution boundary, illustrated. AI-generated artwork.

Make the first test specific.

A planning worksheet, not a live policy engine. Nothing here executes an action or verifies your system.

01 Choose what needs a check

Control a tool callgove-zoneCheck a Python actionACGS-LiteReview a cloud planCFT Governance Pack

02 Define the action and boundary

Plan an evaluation of one tool and its authorization boundary.

What should be allowed?Where should it stop?

Use a fictional or sanitized example. Your draft stays in this tab and is cleared when you reload.

03 Select checks for your plan

Select the checks you intend to run. Selection does not mean a test has passed.

Prepare allowed and denied tool callsChoose one permitted call and one prohibited call; plan to observe whether the executor invokes the tool.Compare the exact call argumentsPlan a changed-argument case and inspect whether the decision binds to the actor, tool, and exact arguments used at execution.Trace escalation and alternate pathsPlan an escalation case and inspect alternate tool paths for calls that avoid the integrated executor.Plan evidence retention across restartsChoose audit storage and signing-key handling; prepare to retrieve and verify retained records after a process restart.

Evaluation worksheetDraft

Your first boundary.

gove-zone

Allowed action: Define one action to evaluate.
Stop condition: Describe what must not happen.

0 of 4 checks selected for the plan

Keep this limit in view

Only paths routed through the integrated executor are covered. gove-zone 1.0.0rc2 is a prerelease; evaluate signing, identity, replay protection, and storage for your deployment.

View Markdown

# Evaluation plan

Product: gove-zone

## Action to evaluate

> To be defined

## Intended boundary

> To be defined

## Preparation checks

Checked items are included in this plan; they do not record test results.

- [ ] Prepare allowed and denied tool calls: Choose one permitted call and one prohibited call; plan to observe whether the executor invokes the tool.
- [ ] Compare the exact call arguments: Plan a changed-argument case and inspect whether the decision binds to the actor, tool, and exact arguments used at execution.
- [ ] Trace escalation and alternate paths: Plan an escalation case and inspect alternate tool paths for calls that avoid the integrated executor.
- [ ] Plan evidence retention across restarts: Choose audit storage and signing-key handling; prepare to retrieve and verify retained records after a process restart.

## Scope limit

Only paths routed through the integrated executor are covered. gove-zone 1.0.0rc2 is a prerelease; evaluate signing, identity, replay protection, and storage for your deployment.

## References

- [Setup guide](https://acgs.ai/products/gove-zone/#start)
- [gove-zone 1.0.0rc2](https://pypi.org/project/gove-zone/1.0.0rc2/): Published prerelease package and release metadata.

Continue with gove-zone

Go to the source.

Read the setup and release limits before running your evaluation.

Open the evaluation guide