Policy & Config
Policy Violations
Section titled “Policy Violations”False Positives
Section titled “False Positives”Symptoms: Policy violations that seem incorrect.
Solutions:
-
Inspect violations:
Terminal window arxo analyze --format json --output report.jsonjq '.violations' report.json -
Adjust thresholds in
policy.invariants(e.g. lowervalueforagent_architecture.overall_agent_health). -
Exclude paths in
data.import_graph.excludeif needed (e.g.**/legacy/**).
Cannot Reproduce Locally
Section titled “Cannot Reproduce Locally”Symptoms: CI fails, local run passes.
Solutions:
- Clear cache:
arxo cache clearthenarxo analyze. - Specify config in CI:
arxo analyze --config .arxo.yaml. - Match version:
arxo --versionin CI and locally.
Configuration Issues
Section titled “Configuration Issues”Invalid Configuration
Section titled “Invalid Configuration”Error: “Invalid config: unknown field ‘foo’”
Solution: Validate config:
arxo config validate --config .arxo.yamlCommon mistakes:
- Typos — e.g.
metriksinstead ofmetrics. - Indentation — Use 2 spaces in YAML.
- Invalid operators — Use
==,!=,<,<=,>,>=inpolicy.invariants, notless_than.
Config Not Found
Section titled “Config Not Found”Error: “Config file not found: .arxo.yaml”
Solutions:
- Create config:
arxo init - Specify path:
arxo analyze --config path/to/config.yaml - Check working directory: run from project root where
.arxo.yamllives.
Next steps
Section titled “Next steps”- Troubleshooting — Overview
- Configuration — Full config reference