geointel/docs/governance/FORBIDDEN_DECISIONS.md

Forbidden Decisions

Codex and contributors must not make the following decisions without creating/updating an ADR and receiving explicit approval.

Technology changes

Forbidden without ADR:

• replacing FastAPI;
• replacing React/TypeScript;
• replacing PostgreSQL/PostGIS;
• replacing Redis + RQ as the default queue strategy;
• introducing a second ORM or data access pattern;
• introducing a second map rendering framework for the same purpose;
• replacing MapLibre/Deck.gl before V1;
• adding a non-approved AI framework as a core dependency.

Architecture changes

Forbidden:

• direct model-to-frontend coupling;
• frontend calling external geodata providers directly;
• AI services writing directly to core tables without an analysis run;
• storing geometries only as JSON files instead of PostGIS records;
• bypassing the response envelope;
• bypassing state machines;
• creating synchronous long-running endpoints for heavy operations;
• hardcoding demo data as if it were production data.

Product changes

Forbidden:

• making reporting the primary product;
• making chatbot the primary interface;
• removing QA/QC from the V1 critical path;
• moving LiDAR/training/MLOps into V1 critical path;
• changing the primary region away from the Kempen.

Data changes

Forbidden:

• dropping CRS metadata;
• accepting geospatial data without validation state;
• silently transforming CRS without recording it;
• treating OSM as more authoritative than GRB-like reference data for the V1 QA workflow;
• deleting original uploaded datasets when processing succeeds.

Quality changes

Forbidden:

• removing smoke scripts to pass CI;
• marking a pass complete without running relevant checks;
• adding TODO, pass, placeholder endpoints or fake success responses as completion substitutes;
• ignoring failing golden path tests.