Local validation complete; public distribution blocked
The command itself is local-only and does not require an Argos account, connected agent, or network connection.
Minimal reproducible example
In a Git repository with an existing package script named test:password-reset, inspect the working tree and explicitly approve that one script:
argos inspect-change \
--check test:password-reset \
--output /absolute/path/outside-the-repositoryUse an external output directory. Without --base, the comparison is HEAD versus the current working tree. To compare from another revision:
argos inspect-change \
--base <git-ref> \
--check test:password-reset \
--output /absolute/path/outside-the-repositoryWhat is inspected
- Tracked changes
- Staged and unstaged tracked changes are included from the selected base revision.
- Untracked paths
- Detected and disclosed, but their source contents are not copied into the report or content-verified.
- Git-ignored files
- Excluded from the change set.
- Working-state changes
- If relevant repository state changes while checks run, the result becomes NOT ESTABLISHED.
Checks require explicit approval
Missing scripts, unavailable tooling, timeouts, or incomplete execution are reported as NOT ESTABLISHED. The checks run independently of the coding agent, but Argos does not claim they were written or approved by a human.
Local evidence only
Argos writes deterministic JSON and self-contained HTML outside the repository by default. Reports contain repository boundaries, changed paths, check outcomes, bounded diagnostics, provenance, timestamps, and limitations. Change Proof uploads no source code and includes no environment values, credentials, or source contents by default.
The files are local reports, not signed attestations.
Read the result precisely
- PASS means every explicitly approved check passed in the inspected working state.
- FAIL means at least one approved check failed in that state.
- NOT ESTABLISHED means the available evidence did not establish every requested check.
- Passing tests do not prove complete correctness or make a change safe to merge.
- Argos does not automatically verify undocumented behavior.
- Without comparable baseline evidence, Argos does not claim that the change caused a failure.
- Local validation does not mean public distribution or production availability.