init-task-persistence

To preserve operator intent across an AI workflow pipeline, you create an append-only init-task artefact at task initialization that every subsequent stage must read to detect and reconcile drift from the original brief.

An append-only task lifecycle artefact is a chronological record storing verbatim operator commands and amendments. You need it when multi-stage execution workflows require stable context across requirements, planning, QA, and archival phases.

You reconcile drift in downstream pipeline stages by enforcing mandatory reads of the init-task artefact during each phase, allowing commands like /dr-prd and /dr-qa to validate their outputs against the original operator intent.

You can recover a workflow validation pipeline if initialization is skipped by using a retroactive backfill path to seed the missing init-task artefact, ensuring later QA utilities can proceed with downstream validation.

Audit trail logging for operator amendments works through a structured YAML schema that chronologically appends operator inputs and Q&A blocks to the task artefact, ensuring traceability without modifying previous entries.

Task lifecycle persistence requires a closed YAML artifact schema for compliance validation, ensuring that the init-task record strictly captures the verbatim operator brief and append-log to meet stage audit requirements.