verification-rules

To enforce verification documents for chapter generators, you apply a universal rule set that mandates a verification file before main content production. This mechanism prevents invalid outputs by validating content at each phase progression.

Required naming conventions and storage locations for verification files are explicitly defined by the governance rules. Specifying target locations and file naming ensures consumer visibility and keeps all generated chapters aligned within the workflow.

Workflow output fails without a verification document because the rules enforce mandatory validation before progression. Generating content without this file causes misaligned workflows and invalid outputs, halting the chapter generator process.

To auto-generate missing verification files, run the orchestrator with auto_mode enabled. This provides fallback guidance to generate and attach the required documents automatically, maintaining process continuity before the generator continues.