Agent Guardrails and Secure Development
Keep the repair inside its reviewed scope
The test disappears
Botie’s patch makes the test run green by deleting a protected assertion. Inspect the changed files before trusting the result.
BOTIE
The inputs we are comparing
Proposed patch entries
Only the parser changes
[
{
"kind": "edit",
"path": "src/date.py"
}
]The assertion is deleted too
[
{
"kind": "edit",
"path": "src/date.py"
},
{
"kind": "delete",
"path": "tests/required.py"
}
]Approved paths
Same in both cases
- 0src/date.py
Independent tests passed?
Same in both cases
true
Result for only the parser changes
ready for review
The approved destination hides an unapproved source
This check uses the pieces from “Keep scope and verification independent”.
BOTIE
- Proposed patch entries
[ { "kind": "rename", "oldPath": "tests/required.py", "path": "src/date.py" } ]- Approved paths
- 0src/date.py
- Independent tests passed?
true
Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.
Build a construction in the workspace above first. This case will test those pieces.
Which files in your own project could alter the checks or permissions of future agent runs?
Review changes to verification and agent configuration as control changes.
These are invented records and deterministic policy checks. The browser runs no agent, shell command, MCP server or network request. Passing these fixtures establishes only the stated policy behaviour.
Work through the Python challenges →