closing-stale-packets

To close stale change packets, you implement a decision contract by completing, closing with rationale, or deleting them as appropriate. This restores integrity to the change-management workflow by ensuring no silent half-done work remains.

A NUCLEAR-GRADE-CLOSED rationale line is a documented record required when closing stale change packets. It ensures a traceable history by enforcing a clear, documented decision and status update for any abandoned or superseded packet.

You identify scaffold or invalid packets by running ng status to flag stale change packets. Once identified, you apply the decision contract to close them with rationale or delete them, preventing silent half-done work in your workflow.

The best way to handle superseded packets is to evaluate their terminal state and apply a decision contract. You either complete them, close them with a NUCLEAR-GRADE-CLOSED rationale, or delete them to maintain workflow integrity and traceable history.

Recording a rationale prevents issues by enforcing a documented decision and status update for every stale packet closure. It maintains a traceable history and stops silent half-done work from disrupting the change-management workflow.

Yes, you use ng status to identify stale packets flagged as scaffold or invalid. This flags abandoned or superseded packets so you can apply the decision contract and close them with the required rationale.