vertical-slice-gate

Vertical-slice completion is enforced by requiring boundary declaration, minimal cross-layer implementation, mandatory build, regression, and smoke checks, plus progress logging before advancing to higher-layer features.

Mandatory checks for closing a vertical slice include build verification, regression tests, and smoke tests. You must log these outcomes to a progress document and satisfy explicit exit criteria before proceeding.

Vertical-slice gatekeeping checks apply during the start or closure of any slice, such as P0 or P1, to ensure minimal cross-layer scope and evidence-based progression in multi-layer software projects.

Define slice boundaries and acceptance criteria by declaring the scope explicitly, implementing only minimal cross-layer work for that slice, and requiring documentation updates with evidence of validation before moving forward.

You cannot advance to the next layer without meeting strict exit criteria. The gate requires mandatory check outcomes logged to a progress document and evidence of validation to prevent downstream churn.

Vertical-slice gating works for any slice priority level, applying during the start or closure of slices like P0, P1, and beyond to enforce bottom-up progression and reduce risk of downstream churn.