44 lines
952 B
Markdown
44 lines
952 B
Markdown
# Improvement Policy
|
|
|
|
GeoIntel should be strict enough for autonomous execution but flexible enough for good engineering.
|
|
|
|
## Desired improvements
|
|
|
|
Codex is encouraged to improve:
|
|
|
|
- typed API clients;
|
|
- service boundaries;
|
|
- validation specificity;
|
|
- reusable geospatial utilities;
|
|
- test determinism;
|
|
- frontend state handling;
|
|
- developer commands;
|
|
- logging and diagnostics;
|
|
- small UX clarity improvements.
|
|
|
|
## Undesired improvements
|
|
|
|
Do not add:
|
|
|
|
- unrelated dashboards;
|
|
- user accounts before V1;
|
|
- payment/billing;
|
|
- social features;
|
|
- generic file manager replacing dataset manager;
|
|
- raw LLM chatbot as a central feature;
|
|
- unsupported live data scraping;
|
|
- excessive styling frameworks beyond the chosen frontend stack.
|
|
|
|
## Improvement report format
|
|
|
|
When making improvements beyond the exact prompt, add:
|
|
|
|
```text
|
|
IMPROVEMENT:
|
|
- what changed
|
|
- why it helps GeoIntel
|
|
- why it does not change scope
|
|
```
|
|
|
|
inside `docs/CODEX_EXECUTION_LOG.md`.
|