Parking lot — Tier 4 candidates¶
Status: Parked. Renamed from
phase-4-expansion.mdon 2026-04-22 to reflect the R3 tier reclassification. See plan.md for active phases and phase-3-vision-draft.md for full rationale on each item.
Purpose¶
This file catalogs ideas that are not committed to any phase. They are filed here (and eventually as GitHub issues per the Tier 4 policy in the vision draft) so they stay searchable and debatable without blocking planned work.
Every item here was evaluated in the Phase 3+ vision draft (R1-R4) and explicitly demoted to Tier 4 / parking-lot, or was a Phase 4 candidate in the original expansion plan that no longer fits the current roadmap.
Promotion rule: a parking-lot item becomes phase-scoped when (a) a user / design partner asks for it, (b) a dependency changes (e.g., engine ships uncertainty), or (c) the context around it shifts materially. At that point, move the entry into the relevant phase file or open a new phase file, and delete the entry here.
Candidates¶
Grouped by risk cluster for readability. Numbers reference the vision draft's idea numbering.
Hosting & infrastructure¶
| Item | Origin | Notes |
|---|---|---|
| Full Kubernetes managed hosting | #29 full impl | Helm + ArgoCD + cert-manager + external-dns. Gated on phase-managed-hosting.md revival. |
| Stripe metering integration | #M billing | Observability slice shipped in Phase 6 §6.11; billing wiring only when managed hosting goes live. |
| Security threat model | gap-9 | Full threat-model doc. User direction: "much later; revisit before any first public deployment." |
| GPU acceleration | gap-5 | JAX / CuPy engine backend. ADR-only until a real perf need emerges. |
UI & rendering (beyond Phase 4)¶
| Item | Origin | Notes |
|---|---|---|
| Building-level disaggregation + 3D | #25 | Microsoft / Overture building footprints + MapLibre 3D extrusions. User flagged as "much later." |
| Map drawing tools (ad-hoc area) | #K | User drew polygon → compute impact. Tier 3 in the vision draft, but gated on a default exposure layer. |
| Heatmap / polyline full LayerSpec | #4 full | Phase 4 shipped raster + vector points; heatmaps + lines layered in later. |
| Pre-computed admin-2 tile pyramids | #5 full pre-computed | Phase 4 shipped on-the-fly + MVT; pre-computation deferred until scaling demands. |
Extensibility & integrations¶
| Item | Origin | Notes |
|---|---|---|
| Non-CLIMADA adapters beyond GEM | #12 later | Hazus, OASIS LMF, MunichRe NatCat. GEM was the first (Phase 7); others as specific demand emerges. |
| User-provided engines (Level 3b, remote webhook) | #24 L3b | Security-sensitive; requires result validation + trust-boundary design. |
| Bulk scenario submission | #H | Power-user CSV upload → N parallel scenarios. Defer until a research user asks. |
| Webhooks / async notifications (push) | #J | No pressure without SDK usage driving it. |
| TypeScript SDK | #I TS | Python SDK lands in Phase 5; TS only if a real UI-adjacent integration emerges. |
Reports & reproducibility¶
| Item | Origin | Notes |
|---|---|---|
| Custom report templates | #14e | User-uploadable Quarto / Word templates with placeholders. Confirmed parking-lot by user. |
| Scenario versioning | #P | Copy-on-write when underlying dataset / impact-function changes. Tier 3 in vision; parked pending demand. |
| Data versioning / schema contracts | gap-8 | Paired with #P; needed when real dataset updates start hitting saved scenarios. |
| Frequency-curve uncertainty bands | #L | Gated on engine uncertainty quantification landing. |
Context & data¶
| Item | Origin | Notes |
|---|---|---|
| Per-country macroeconomic tables | #11 later | SSP-scenario GDP / population projections. Tier 3 later-in. |
| Context overlays UI ("CRED-like tab") | #13 | Sidecar datasets for narrative context. Data model design cheap; UI on-demand. |
| CMIP6 intensity scaling | Phase 4 candidate | scenario goes from metadata label to actual data transform. Engine-side work. |
| Data marketplace (paid packages) | #19 full | Beyond the 3-dataset catalog in Phase 6. Tier 4 until revenue is real. |
Platform presence¶
| Item | Origin | Notes |
|---|---|---|
| In-app news / changelog landing | #31 | User: "not a strong opinion." Revisit when a user asks. |
| Desktop app (Tauri / Electron) | #23 + P4 candidate | Architectural affordances landed throughout Phase 3-7 per vision #23. Full port Tier 4. |
Issue policy¶
Per the vision draft R3 policy ("file every deferred or Tier 4 item as a
GitHub issue regardless"), each of the above should have a corresponding
GitHub issue in the appropriate repo (climate-lama for cross-cutting,
climate-lama-engine for compute, climate-lama-ui for UI-only) tagged
tier-4-parking-lot. Issues get filed per-phase rather than all at once,
so this file stays the master list until issues exist — consistent with
A6 in the vision draft.