saf-feature-dev

Feature development workflow for multi-crate static analysis environments is structured into eight phases from planning through wrap-up, generating PROGRESS updates and traceable decisions. It guides exploration, design, testing, and review with tool-mapped prompts and checklists.

AIR-only analysis enforces determinism by restricting intermediate representations to AIR-only IR and generating deterministic BLAKE3 IDs. This ensures reproducible results and cross-crate stability across frontend, core analysis, Python SDK, and CLI components.

Yes, the workflow applies to SAF feature additions, bug fixes, and workflow governance across frontend, core analysis, Python SDK, and CLI work. It uses dockerized experiments and CI-friendly steps to validate changes in these environments.

The best way to ensure documentation and tests in static analysis feature development is following an invariant enforcement workflow that hard-requires both. It enforces determinism, AIR-only IR, and deterministic IDs while mandating documentation and tests across all phases.

Deterministic BLAKE3 IDs are needed for cross-crate static analysis stability because they enforce invariant rules ensuring reproducible results. They guarantee that analysis outputs remain consistent and traceable across frontend, core analysis, Python SDK, and CLI work.

You should not use the 8-phase structured workflow for rapid prototyping or exploratory changes that do not require strict determinism, AIR-only analysis, mandatory documentation, or cross-crate stability enforcement in a multi-crate static analysis environment.