geointel/prompts/codex/M11_ARCHITECT_MASTER_PROMPT.md

M11 Architect Master Prompt for Codex

You are implementing GeoIntel Kempen.

Before coding, read:

1. docs/00-start/START_HERE.md
2. docs/governance/GEOINTEL_CONSTITUTION.md
3. docs/governance/ARCHITECTURE_INVARIANTS.md
4. docs/governance/FORBIDDEN_DECISIONS.md
5. docs/governance/DECISION_PRECEDENCE.md
6. docs/specs/CANONICAL_DOMAIN_MODELS.md
7. docs/specs/GIS_STANDARDS.md
8. docs/specs/RASTER_STANDARDS.md
9. docs/specs/STATE_MACHINES.md
10. docs/workflows/GOLDEN_PATHS.md
11. docs/build/BUILD_ORDER_DEPENDENCY_GRAPH.md
12. docs/build/CODEX_OPERATING_SYSTEM.md

Your mission is not to invent a new product. Your mission is to implement the documented GeoAI Workbench.

First implementation target

Build the smallest stable vertical slice:

• backend skeleton;
• config/env loading;
• database connection placeholder or implementation;
• project, area and dataset domain models;
• response envelope;
• error catalog integration;
• demo reference and predicted building fixture loading;
• QA/QC matching function on fixtures;
• GeoJSON export for QA outputs;
• minimal frontend route/shell if backend foundation is stable.

Strict rules

• Do not introduce unapproved architecture.
• Do not build frontend-only mock workflows.
• Do not implement live YOLO before detection result lifecycle exists.
• Do not implement live GRB WFS before demo reference workflow is stable.
• Do not skip tests or smoke checks.
• Do not remove docs to reduce conflicts; update canonical docs instead.

Acceptable autonomous improvements

You may add:

• typed schemas;
• helper services;
• repository pattern if simple;
• tests;
• fixture validators;
• clearer error messages;
• frontend empty/loading/error states;
• docs updates.

Required final response from Codex

At the end of the pass, report:

Pass name:
Implemented:
Files changed:
Commands run:
Tests passed:
Tests failed:
Golden paths status:
Architecture invariant status:
Known limitations:
Next recommended pass: