Imported from Phoenix5595/ProjectCEA (Infrastructure/AGENTS.md). Install upstream with npx skills add Phoenix5595/ProjectCEA --skill Infrastructure. Copyright stays with the author.

CEA Infrastructure

Active Service Map

Source: services.yaml.

Shared Cross-Service Flow

Sensors → can-processor / soil-sensor / onewire / weather
        → Redis `sensor:raw` (maxlen 100,000)
        → TimescaleDB `measurement`
        → backend / automation / Grafana

Config changes flow from automation-service to backend to frontend via Redis Streams (cea:events:config) and WebSocket. Source: automation-service/app/events/__init__.py.

Monitoring range validation is intentionally split: monitoring-service sensor/control reads validate ranges down to 1 second (sensor_models.MINIMUM_RANGE = timedelta(seconds=1)), while automation-service projection snapshot construction independently requires ranges of at least 5 minutes (app/schemas/monitoring_models.py MINIMUM_RANGE). These are separate validators serving different purposes; neither is being changed by the plan.

Deploys restart all managed services as full-service candidates; there is no component-scoped deploy. Rollback restores code/release state but does not revert database schema. This plan performs no schema migrations.

Shared Code Ownership

See shared/AGENTS.md for boundary details.

Service Dependencies

postgresql.service
redis-server.service
    ↓
can-setup.service
    ↓
can-processor.service
cea-backend.service
    ↓
soil-sensor-service.service
weather-service.service
onewire-worker.service
    ↓
automation-service.service

Source: services.yaml start_order.

Child Guidance

Anti-Patterns

• Never skip Redis Stream writes; recent-data queries fail.
• Never invalidate only per-cluster schedule caches after a global get_schedules() consumer; clear schedules:all too.
• Never edit .service files without sudo systemctl daemon-reload.

Last updated: 2026-08-10