Tracking issue from PR#6 review
Post-merge implementation item surfaced during squad review of KNOWLEDGE-DECAY.md.
Problem
When a parent node is deleted (not just resolved to contested), its dependents retain dependency_taint: true with a taint_origin_id pointing to a deleted/retired node. Without a sweep, those taints are orphaned indefinitely.
Required behavior
The cascade-clear worker must:
- Check if
taint_origin_id resolves to an existing, non-deleted node before processing
- If the origin node has been deleted/retired (tombstone check), auto-clear the taint on all dependents
- Log cleared orphan taints for audit trail
Notes
- Depth-1 taint boundary means this sweep scope is bounded — only direct dependents of deleted nodes, not transitive
- Can be implemented as a separate sweep pass or folded into the existing cascade-clear worker logic
- See PR#6 comments and squad review thread for context
Tracking issue from PR#6 review
Post-merge implementation item surfaced during squad review of
KNOWLEDGE-DECAY.md.Problem
When a parent node is deleted (not just resolved to
contested), its dependents retaindependency_taint: truewith ataint_origin_idpointing to a deleted/retired node. Without a sweep, those taints are orphaned indefinitely.Required behavior
The cascade-clear worker must:
taint_origin_idresolves to an existing, non-deleted node before processingNotes