Archive Protocol

It handles everything from PLAN.md to JSON outputs using a dual-track path system with session IDs and timestamps. The key enforcement is that all generated content must physically move from workspace to archive, leaving nothing behind in the working directory. It mandates verification reads after every write and requires all archive operations go through a dedicated archive tool that outputs JSON status cards. If you're building workflows where audit trails and versioned outputs matter more than convenience, this protocol keeps everything organized at the cost of flexibility.