su-reactivate

To reactivate a cancelled requirement while preserving audit integrity, use a reactivation command with the requirement ID. The system reads the defined state and EventJournal to restore it to an actionable state without losing historical cancellation reasons.

Yes, restoring a deferred task supports contextual re-entry. The system reads the previous state and EventJournal to direct the reactivated task back to the appropriate processing node for continuous project progress.

When a task is reactivated, the original cancellation or deferment reason is fully maintained. This ensures historical audit preservation, allowing teams to track why items were paused while they resume actionable progress.

You can trigger requirement reactivation by executing the command `/ccb:su-reactivate requirement_id=123`, replacing `123` with your target ID. This reads the defined state to shift the requirement back to an actionable status.

Yes, an EventJournal is required for project management task reactivation. The system reads from this journal and the defined state to accurately restore cancelled or deferred subjects while ensuring audit preservation.

Use requirement reactivation in task management workflows when previously cancelled or deferred requirements become relevant again. It allows specific subjects to progress to an actionable state while ensuring historical context is preserved for project control.