beads-evolve

Adaptive refinement of the issue graph handles this by supporting in-flight adaptation such as re-sequencing dependencies and discovering blockers. This ensures your development workflow maintains traceability even when initial planning needs adjustment.

You can split issues to enable parallel work through a structured workflow using session lifecycle commands. Starting with beads-orient initiates the evolution session, and beads-checkpoint captures progress while preserving the history.

Git-tracked JSONL stores evolution history to provide safe and auditable issue graph refinement. This format enables automatic graph recalculation while maintaining full traceability and reproducibility of all structural changes.

Re-sequencing dependencies is supported through enforced safe graph operations that maintain traceability. The system orchestrates evolution commands to ensure dependency changes are captured in the git-backed history without breaking reproducibility.

Adaptive refinement is needed when implementation reveals what you could not anticipate during initial planning. The issue graph acts as a living model of work, requiring in-flight adaptation like splitting issues or re-sequencing dependencies as development progresses.

Automatic graph recalculation is required because the issue graph is a living model rather than a contract. As implementation reveals unanticipated dependencies and blockers, recalculating the graph ensures the evolving model stays accurate while preserving history.