Iter Iter

8-Point Safety Review

Every set of proposed steps goes through a pre-execution safety check before anything runs. Post-execution review verifies results against acceptance criteria.

Request detail showing review verdict and criteria results

Pre-execution safety check

Before any command runs or file is created, the reviewer model evaluates all proposed steps.

1

File path safety

Verify all file operations target paths within the project directory.

2

Destructive command detection

Flag rm -rf, DROP TABLE, and other destructive operations.

3

Secret exposure

Detect API keys, tokens, and credentials in file content.

4

Dependency audit

Review package installations for known malicious packages.

5

Network access

Flag commands that make external network requests.

6

Permission escalation

Detect sudo, chmod 777, and privilege escalation patterns.

7

Resource usage

Estimate execution time and flag potentially long-running operations.

8

Consistency check

Verify steps are internally consistent and don't conflict with each other.

Post-execution review

PASS

All acceptance criteria met. Request marked complete.

FAIL

Issues found. Fix steps generated and pipeline re-runs.

INFO_NEEDED

More evidence needed. System gathers file reads and command output.

Safety-first AI development