File and command access
Inspect file access and command effects separately. Naming a project directory does not authorize access to the home directory, other projects, or every record in a connected account.
Inspect Desktop targets
- Confirm the directory in the project or coding workspace and match terminal execution to it.
- Name readable inputs and writable outputs, including material excluded from sending, committing, or publication.
- Inspect actual request paths and arguments. Stop and review scope if another directory, account, or remote environment appears.
- Check the diff or output file and command results.
Project membership and written instructions are not operating-system isolation. Use Git worktree for a separate code copy; it does not isolate networking or the OS account.
A verifiable task boundary
Read only Markdown under this project's docs/ and write reports/link-check.md.
Exclude .env, identity directories, and other projects. Do not install, commit, or push.
List the checks before running them; report changed files and actual results.
Inspect unexpected changes before recovery. Do not clear directories or reset the entire workspace. See project development for a complete example.
Define scope before execution
List readable directories, editable files, excluded locations, and required outputs. Include dependency installation, generation, and formatting in the change budget. Record the starting Git diff or workspace snapshot and preserve existing edits.
Inspect arguments, working directory, redirection, pipelines, scripts, and network destinations. Pass external text as data rather than building shell instructions from it. Do not print complete environments or secret files.
Standalone Evolver budgets
Evolver validates file counts, line counts, and forbidden paths. Compare Gene declarations with the actual diff. Stop and split an oversized change instead of increasing limits to conceal an overrun. These controls validate Evolver changes; they are not filesystem isolation for every Desktop tool.
Inspect the result
Review tracked files, untracked files, and external effects. Restore only task-owned changes. Git recovery does not undo messages, publication, database writes, or remote deletion.