Chirality Agent User Manual · Edition 4 · Accepted 10 October 2026 · Source 22dd62a7f0 ↗ · Markdown

6. Select proportionate verification

Root's rule is consequence-based:

Change	Typical verification
Routine and reversible	Inspection or direct exercise.
Ordinary implementation	A focused check of the affected behavior.
Numerical meaning, persistence, permissions or destructive operations	Targeted regression checks and independent scrutiny by a separate agent.
Release	Examination of the actual product; release remains reserved.

Do not alter a criterion merely to obtain a pass. Establish whether the source requirement, test or implementation is wrong. Preserve protected oracles and meaningful limits unless their owner authorizes a substantive change.

The single required GitHub result is harness. It combines repository checks and selected App v4 and Piping jobs. App v3, Runtime and PEC have no verification jobs. See CI selection for the maintained policy.

The aggregate fails when selected work fails, is cancelled or does not run. Unselected work is reported as unselected. A reused result names its earlier run and candidate; it does not claim new tests ran.

Do not repeat a passing hosted suite locally without a new change or unresolved concern. Check selection must cover actual consumers; an empty selection is not proof of safety.

For Root tools, inspect and then run the affected suite selection:

python3 tools/run_affected_tests.py --dry-run
python3 tools/run_affected_tests.py

For Piping, the profile selector accepts project-relative paths:

python3 tools/software_workflow/select_affected_checks.py projects/chirality-piping/software-workflow.json core/model_transform/physical_to_analytical/_solver_boundary_adapter.py

This command selects checks; it does not execute them. Piping's CI strategy explains its current numerical, browser and Python coverage. DEC-025's blanket local sweep is not a merge requirement. The release sweep remains a separate optional release-preparation tool.