Files
geointel/docs/40-build-launch/FOLDER_OWNERSHIP.md
Jens faeb58ef6d
GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
Initial public release
2026-08-31 21:56:53 +02:00

76 lines
1.4 KiB
Markdown

# FOLDER OWNERSHIP AND RESPONSIBILITIES
Codex must keep responsibilities separated.
## `backend/app/api/`
HTTP routes only. No heavy business logic.
## `backend/app/schemas/`
Pydantic request/response models and API DTOs.
## `backend/app/models/`
Database ORM models.
## `backend/app/services/`
Business logic and orchestration.
## `backend/app/repositories/`
Database access patterns if repository layer is used.
## `backend/app/workers/`
RQ/Celery/background job entry points.
## `backend/app/geo/`
GIS-specific helpers: CRS, geometry validation, bounds, area calculations.
## `backend/app/storage/`
File storage logic.
## `backend/tests/`
Backend tests. Tests should not live beside production modules unless project conventions are changed deliberately.
## `frontend/src/pages/`
Route-level pages.
## `frontend/src/components/`
Reusable UI components.
## `frontend/src/features/`
Feature-oriented frontend modules, e.g. projects, datasets, map, exports.
## `frontend/src/services/`
API client/services.
## `frontend/src/stores/`
Client state only if needed.
## `docs/`
Architecture, specs and governance. Update docs when contracts or build rules change.
## `demo/`
Small golden fixtures and demo manifests. Not production storage.
## `datasets/`
Local development data folders. Do not commit large real datasets.
## `storage/`
Runtime storage. Keep `.gitkeep`, do not commit generated artifacts.