Keep the failure that taught the fix.
Save a reproducible defect with its typed test evidence, resolve it against current bytes, and reopen the record when later changes make that resolution stale.
How it actually works
Exactly what it does — and when.
The original failure and its typed TAP check remain attached to the regression record. When a later refactor changes the parser, the old resolution no longer matches current bytes and reopens for review instead of remaining silently closed.
- A fix erases the failure that motivated it
- Passing status lacks an executed check
- Later edits inherit stale resolution
- Retain the original failure beside its repair
- Require an executed typed Node TAP check
- Reopen stale resolutions when the artifact or evidence changes
Use it to…
Real ways people run Genesis Regression Memory.
Capture a regression
Create a record from the failing artifact and an executed typed TAP check.
Resolve a defect
Bind the repair to current bytes and the test that now passes.
Reopen stale evidence
Return a prior resolution to active review after the artifact or test changes.
What's inside
Who it's for
Maintainers with recurring defects
need the original reproducer to survive the fix
Integration teams
need stale resolutions to reopen visibly
Reviewers
need current test evidence behind a resolved label
Questions, answered
Ready to put Genesis Regression Memory to work?
Instant download · one-time price · own forever · all sales final