validate-artefacts

To validate discovery artefacts, run a process that checks Epics for outcome orientation and Stories for measurable acceptance criteria. This ensures generated artefacts are clear, governed, and complete before proceeding to the Delivery phase.

Artefact governance enforcement is the process of verifying that Epics and Stories align with predefined rules. It identifies scope contradictions and rule violations, acting as a mandatory gate to prevent ambiguous requirements from reaching development teams.

You can check for measurable acceptance criteria by running an automated validation process against generated Stories. It cross-references rules and artefacts to ensure every Story has clear, testable conditions before coding begins.

Yes, this serves as a mandatory delivery gate that blocks incomplete or ambiguous Epics. It enforces outcome orientation and checks for scope contradictions, ensuring no epic proceeds without meeting governance quality bars.

To cross-check artefact readiness comprehensively, you need files from contexts/artefacts/epics, contexts/artefacts/stories, and contexts/rules. These inputs allow the validation process to identify contradictions and enforce governance standards.

When scope contradictions are found during artefact validation, the process flags these violations. The artefacts are blocked from handover to Delivery until the contradictions are resolved and alignment with governance rules is confirmed.