Storage Levers

What needed solving.

Bring facility data, pricing decisions, competitor signals and customer calls into usable operator workflows while supporting separate app runtimes and controlled releases.

1. 01Facility + market data
2. 02Domain APIs + guardrails
3. 03Previewed operational decisions

Simplified from the implementation and project notes.

How it fits together.

The monorepo retains independently deployed applications and runtimes rather than forcing one framework: Next.js frontend and marketing site, FastAPI backend, AWS call-scoring/fetch scheduler and GoTo/OpenAI voice gateway. Shared generated API contracts connect typed consumers.

The FastAPI domain includes new-customer-rate recommendations, pricing configuration, competitor snapshots, operational reports and integrations. NCR assembles facility/unit hierarchy and metrics, applies strategy guardrails, and supports preview, commit, overrides and experiments with persisted history.

Root task metadata declares app ownership/dependencies; lint checks graph boundaries, and contract checks validate generated consumers. Releases are explicit manual commands rather than implicit pushes.

Building and checking it.

Operational and competitor inputs flow through backend APIs and scheduled pipelines; pricing suggestions can be previewed and committed, while the dashboard surfaces reporting and analysis. The multi-app repo uses scoped tasks and transitive consumer verification.

The README documents an NCR Redis integration check and broader checks; deployment docs distinguish target-specific release and rollback procedures.