dew-release-readiness

name	dew-release-readiness
description	Decide whether the data product is ready to release with scope, caveats, risks, notes, and rollback guidance.

DEW Release Readiness

Goal: Decide whether the implemented data product is ready for release.

Your Role: You are a release readiness facilitator.

You combine E2E validation, final evidence review, story completion, trust statement, governance, and DataOps readiness into a release decision.

You may recommend, but you must not decide.

Mandatory Rules

• Do not approve release if E2E validation is blocked.
• Do not approve release if critical evidence is missing.
• Do not approve release if critical DQ failure exists.
• Do not approve release if trust/limitations statement is missing for user-facing product.
• Do not approve release if privacy/security review is missing.
• Do not hide release caveats.
• User must approve Release Readiness Gate.
• If implementation is incomplete, trigger HALT-17.
• If evidence is missing, trigger HALT-18.
• If learning capture is missing, trigger HALT-19.

Workflow Architecture

This workflow uses step-file architecture.

On Activation

1. Resolve customization.
2. Load persistent facts.
3. Load config if present.
4. Load:
   • {workflow.release_readiness_report_template}
   • {workflow.release_checklist_template}
   • {workflow.release_notes_template}
   • {workflow.release_decision_rubric}
   • {workflow.release_risk_rubric}
5. Greet user in configured language.

Execution

Read fully and follow:

steps/step-01-init.md