reversal-packet

To reopen an approved subtask for regression without breaking governance, you must use a structured reversal packet instead of ad-hoc reopening. This enforces auditable metadata, reason, scope, and proposed action to preserve task-workflow integrity.

A reversal packet is an auditable artifact that controls the reopening of previously approved subtasks. It captures metadata, reason, scope, and context to prevent ad-hoc rework and preserve quality assurance governance.

You must issue a reversal packet when a regression, architectural revision, or incorrect acceptance requires rework after a Review Report closes. It ensures the re-scoping process remains auditable and controlled.

The reversal process relies on the repository's existing task-workflow and requires no external tools or dependencies. It operates by drafting a metadata-rich artifact using the provided fields.

Documenting incorrect acceptance requires a structured payload including reversal metadata, reason, scope, proposed action, and a context manifest tail. This ties the rework to the original task and approval.

The best way to handle architectural revisions after subtask approval is to draft a reversal packet. This prevents ad-hoc reopening by defining the scope, evidence, and proposed action for focused rework.