- PERFORMANCE_BASELINE.md
- reports/performance_baseline.json
- PHASE6G_PERFORMANCE_BASELINE_SNAPSHOT.md
- Execution timings were gathered locally on Windows utilizing PowerShell's
Measure-Commandutility to track complete execution cycles from start to finish. - Tested all commands to verify they execute successfully, complete without error flags, and exit with status 0.
- Executed double runs to confirm baseline consistency under dev profile setup.
- Measured file sizes in bytes using standard filesystem info calls.
- Validated that
artifacts/spark/extraction.spkg,artifacts/spark/context.json,artifacts/spark/context_render.txt, andreports/latest.jsonare present and correct. - Generated SHA-256 hashes using PowerShell
Get-FileHashto register deterministic signature keys.
- Validated that the output in
reports/performance_baseline.jsoncomplies with JSON syntax rules. - Run validator tool
python -m json.toolto verify structural format validity.
All assertions follow standard formatting rules:
- Offline behavior was deterministic in the validated test scope.
- Configured leak checks passed in the validated scope.
- No blocking risks found in the validated scope.
- Required Wording:
- Performance baseline measured on local validation environment.
- No performance optimization was performed in this phase.
- Measurements are local and environment-specific.
- Forbidden Claims Avoided:
- All forbidden claims, certifications, or official compatibility statements are strictly avoided.
cargo fmt --all --check-> PASScargo check-> PASScargo test-> PASScargo clippy -- -D warnings-> PASScargo run --bin agy-ct -- run-> PASSpython -m json.tool ../reports/latest.json-> PASSpython -m json.tool ../reports/performance_baseline.json-> PASS