`docs/plan/` — WiqAIa+ Implementation Plan

The plan that drives the build. Start with 00-overview.md.

Foundation docs

File	Purpose	Required reading before
`00-overview.md`	Strategic frame, principles, milestone roadmap, parallel tracks	Anything
`01-architecture-summary.md`	Locked tech stack with rationale per choice	Touching architecture
`02-cost-guardrails.md`	The five layers of bill protection; pilot budget envelope	Touching infrastructure
`03-data-protection.md`	Encryption, audit, RLS, NCA + PDPL alignment	Touching anything that stores or transmits data
`04-abstractions-and-contracts.md`	Interface boundaries; the `packages/contracts/` package; driver pattern	Adding any external integration
`05-contingencies.md`	What we do when things go wrong (on-prem GPU, LLM swap, CNTXT delay, hardware delay, scope cuts)	Whenever something feels stuck

Milestone docs

ID	File	One-line goal
M01	foundations	GCP project + cost guardrails + KMS + GKE + CI/CD + `packages/contracts/` + hello-world apps deployable
M02	identity-and-authorization	Real auth (Keycloak), real RBAC, real MFA, real audit log
M03	multi-tenant-data-layer	Full data model in Postgres with PostGIS, RLS on every table
M04	camera-ingestion-and-live-viewing	Cameras stream via WebRTC; frames extracted at 1 fps
M05	tier0-and-tier1-ai	Motion filter + YOLO + anomaly autoencoder + per-camera calibration
M06	tier2-llm-analysis	Multimodal LLM (Gemma 4 with verified fallbacks) producing structured threat assessments
M07	spatial-correlation-fire-panel-alerts	Fire panel → AI correlation → operator-visible evidence in < 30s. The signature demo.
M08	dashboards-and-fd-view	Polished operator dashboard + stripped-down FD view + EN/AR with RTL + KPI panels
M09	edge-supervisor-and-auto-update	One-line bootstrap install; cloud-pushed blue/green container updates with auto-rollback
M10	hardening-and-uat-prep	DR drill; on-prem-GPU dry run; KPI verification; operator training; final acceptance

Dependency graph

M01 ──┬──> M02 ──> M07 ──> M08 ──> M10
      ├──> M03 ──> M07
      ├──> M04 ──> M05 ──> M06 ──> M07
      └──> M09 ──────────────────────> M10

After M01, M02 / M03 / M04 / M09 can run in parallel. M07 is the integration point.

Tracking progress

COMPLETION_LOG.md — sign-off entries appended at each milestone exit.
The harness’s task list mirrors high-level milestone progress.
Per-milestone files have explicit Verification checklists; a milestone is not complete until every verification passes.

How this plan stays alive

Working documents. If you find something out of date or wrong, fix it in place. If a major decision changes, write an ADR in docs/architecture/ and link it from the affected plan doc.