practice-implementation-first

This gating process requires per-commit test coverage by identifying the relevant §13 layer for each commit and verifying corresponding tests exist. It specifically activates when feature pipelines select the implementation-first path, ensuring discipline across all change types.

The implementation-first approach prioritizes writing implementation code before tests, requiring a gating process to prevent test omissions. It mandates attaching tests to every commit across unit, integration, and E2E layers, with changelog notes recording any postponed tests.

Yes, the commit gate enforces per-commit test coverage aligned with the §13 layering system across unit, integration, and acceptance layers. It specifically applies when a feature pipeline selects the implementation-first path, guaranteeing coverage regardless of change type.

The best way to prevent silent test omissions is enforcing commit-level test coverage via a gating process. This requires identifying the relevant §13 layer for each commit, verifying corresponding tests exist, and recording changelog notes for any postponed tests.

You should avoid the implementation-first approach when you cannot guarantee commit-level test coverage via a gating process. Without enforcing per-commit tests across unit, integration, and acceptance layers, the approach risks silent test omissions and unverified code changes.