Change the issues type filter
Issues
is:issue state:open
is:issue state:open
Issues
- StepzeroLab/research-git#41 · opened
on Jul 23, 2026 1 - StepzeroLab/research-git#39 · opened
on Jul 19, 2026 Support updating capsules as the codebase evolves
Filter by Description: ## Problem Feature Capsules are created against the codebase at the time they were captured. Over time, the surrounding code changes: modules move, dependencies are renamed or removed, APIs change, data assumptions drift, and the original implementation context may no longer exist in the same shape. research-git currently has only a narrow update path: after a successful recall/regeneration, the flow can refresh a capsule's `resurrection_guide`. That helps the capsule learn a better re-apply recipe, but it does not address the broader aging problem. There is no clear workflow for updating an existing capsule's stale context, such as: - dependencies that have changed or disappeared - `depends_on` / relationship edges that are no longer accurate - code slices pointing at symbols or files that have moved - assumptions that are no longer true in the current codebase - knobs or implementation notes that need to be revised after the project evolves This means an old capsule can remain recallable by name/intent, but become increasingly hard for an agent to regenerate correctly because the stored context describes an older version of the codebase. ## Current limitation The system can create capsules, recall them, regenerate them, and optionally refresh the `resurrection_guide` after a successful run. But it does not have a first-class capsule update/maintenance flow for keeping approved capsules aligned with today's codebase. In other words: capsules are durable memory, but their dependency/context metadata can go stale, and research-git does not yet have a good story for detecting or updating that staleness.Filter by Priority: MediumStepzeroLab/research-git#28 · openedon Jul 5, 2026 3