# Analyzer Runtime, Rerun, and Packaging Policy

## Stage5B cost

The user's current system requires more than 100 minutes for a full Stage5B
run. Treat a completed Stage5B result set as expensive evidence.

## Required decision sequence

- Do not rerun Stage5B to fix Markdown, CSV formatting, report labels, ranking
  presentation, ZIP contents, or helper-only defects.
- Compile and run source-local unit/smoke checks first.
- Use model filters or explicit input indices for semantic smoke tests.
- Write smoke outputs to a distinct output directory.
- Confirm the producer/version line in the smoke log.
- Run the full corpus only after the evidence-generating behavior changes.
- End run instructions with a command that archives the generated results.

## Stable interfaces

Installable ZIPs keep canonical names such as:

- `hlds_stage1_extractor.py`
- `hlds_stage2_normalizer.py`
- `hlds_stage3_router.py`
- `hlds_stage4_decryptor.py`
- `hlds_stage5a_disassembler.py`
- `hlds_stage5b_analyzer.py`
- `make_recipient_rankings_table.py`

Package filenames may carry versions. Installed CLI filenames do not change
without an explicit interface migration.
