archive-protocol

To automatically move task outputs to an archives directory, apply an end-to-end archiving protocol that relocates plans, reports, and JSON artifacts with proper ARCHIVE_ID and TIMESTAMP. This ensures traceability and compliance for completed workflows.

Post-archive validation for workflow compliance is a verification mechanism that checks no artifacts remain in the working area after archiving. It generates a verification log to prove all outputs moved successfully to the archives directory.

Yes, the archiving protocol supports session tracking for audit-ready workflows. It enforces session tracking alongside post-archive validation to ensure complete traceability of all relocated task artifacts.

To ensure traceability for generated plans, summaries, and JSON artifacts, use an automated archiving protocol that moves outputs to a centralized archives area. This enforces traceability by assigning ARCHIVE_ID and TIMESTAMP records to all relocated files.

The best way to archive task outputs end-to-end for compliance is using a protocol that automatically moves all artifacts via an archive tool to a centralized area. It enforces post-archive validation to confirm no files remain in the working directory.

You need to archive task outputs to a centralized area when a project finishes and you must enforce compliance. This relocation step moves all plans, reports, and JSON artifacts out of the working area to generate a verification log.