genai-preflight

Validate GenAI architecture decisions by running a preflight check against established contracts. This ensures your LLM gateway, observability, guardrails, and evaluation strategies meet defined requirements before you begin coding.

Required GenAI architecture contracts include LLM_GATEWAY_CONTRACT.md, OBSERVABILITY_LLM_CONTRACT.md, GUARDRAILS_CONTRACT.md, and EVALUATION_LLM_CONTRACT.md. These documents must exist and be consistent to pass preflight validation.

Run GenAI architecture preflight checks after completing architecture-preflight but before feature implementation. This timing catches governance and evaluation gaps early, ensuring all required artifacts and NFRs are populated.

Check LLM non-functional requirements by validating that all NFR fields are populated with non-TBD values. This ensures your architecture meets observability and evaluation criteria before development begins.

No, GenAI preflight validation requires architecture-preflight to be completed first. It validates Level 5 GenAI architecture decisions against established contracts, building upon the foundational architecture work.

Missing guardrails or evaluation contracts will cause preflight validation to fail, identifying the gaps. You must create the required contract documents and populate NFR fields to achieve end-to-end preflight readiness.