gate-p2

/gate-p2 – Quality Gate 2: Validation → Architecture

Checks whether all critical Assumptions have been validated and a well-founded Go/No-Go/Pivot Decision can be made. This is the most important gate in the model – here it is decided whether to invest in the cost- and time-intensive architecture and implementation phase. No argument – this gate always checks the complete checklist.

No Argument ($ARGUMENTS not applicable)

Gate commands do not accept arguments. They always check the complete current project status.

Execution

1. Read Preflight Report

Read docs/.gate-preflight-p2.md as the primary source of information. This report contains:

• Artefact existence and mandatory sections (mechanically checked)
• Content check (regex-based: risk assessments, validation status, results, PoC)
• Document summaries (via Ollama, if available)

If the preflight report does not exist or is older than 10 minutes, read the validation documents directly instead — always start with the phase index:

1. docs/validation/VALIDATION.md (phase index) — gives you the detail-file table, key decisions, open risks.
2. From the index's detail-file table, load only the detail files you need:
   • docs/validation/ASSUMPTIONS.md (register with validation status)
   • docs/validation/MARKET_VALIDATION.md
   • docs/validation/POC.md (plus poc/ code directory if relevant)
   • docs/validation/REGULATORY_CHECK.md
3. P1 reference (only when validation findings impact concept/financials): docs/concept/CONCEPT.md (index), then BUSINESS_MODEL.md / FINANCIAL_PLAN.md / DSGVO_INITIAL_ASSESSMENT.md selectively.

1a. Constitution Inviolables (mandatory pre-gate)

If docs/CONSTITUTION.md exists, the preflight report (docs/.gate-preflight-p2.md) includes a section "Constitution Inviolables (Required Read)" with the project's non-negotiable rules.

These Inviolables are mandatory input for the gate:

• Include the Inviolable bullets verbatim in the agent prompt (Step 2 below).
• The agent must check each evaluated phase-decision against the Inviolables.
• Any violation is an "Inviolable breach" — surface it explicitly in the verdict and treat it as a No-Go signal (Conditional Go only if the user explicitly waives; document the waiver).