deferred-tracking

Tracking deferred work items requires capturing structured records with priority, gate conditions, and traceable sources into a project graph. This approach centralizes deferred items for recurrent triage, ensuring work deferred during planning or implementation remains visible, actionable, and objectively evaluated.

A deferred work gate is a verifiable condition attached to a deferred item that defines when it should be acted upon. When gate conditions are met, such as a project phase completing, the gate evaluation flags the item for triage and prompts a user decision to tackle, update, or remove it.

Auto-detection of deferral language during planning and implementation captures items automatically. When phrases like defer to Phase 3 are detected, the system creates a structured deferred item with a gate that later triggers a review when that phase completes.

Triage a deferred work backlog by loading active items from the project graph and evaluating their gate conditions. This process flags ready items whose gates are met, identifies stale items needing updates, and highlights approaching items to reprioritize.

SeleneDB integration is required to persist deferred work items and gate records. The database stores DeferredItem and Gate nodes, updates status, met flags, and evidence, and maintains relationships between sessions, topics, and related items for longitudinal visibility.

Managing tech debt and deferred work requires centralizing items in a project graph with structured capture of priority, gates, and source links. This ensures deferred work has verifiable gates and traceable sources, enabling objective decisions and preventing items from becoming stale or blocking progress.