app-defaults

What problem does it solve?

Ensures all default, seed, and starting configuration values for the HBG Portal are managed in one canonical location so admins and developers never rely on scattered inline defaults that drift over time.

Core Features & Use Cases

• Canonical storage: Defines where market/macro, underwriting, and LLM default values are persisted (global_assumptions and researchConfig.tabDefaults).
• Resolution precedence: Documents the exact cascade used by consumers: entity-level explicit value → App Default → hardcoded system constant, and LLM-specific fallbacks for vendor/model resolution.
• Developer and admin guidance: Specifies UI placement (Admin → App Defaults), API endpoints, schema locations, and a checklist for adding new defaults to prevent ad hoc inline defaults.
• Use Case: When adding a new property underwriting seed like starting ADR, follow the checklist to add the field to ModelDefaultsTab.tsx, update the API schema, and ensure downstream consumers read App Defaults as the fallback.

Quick Start

Open Admin → App Defaults and set the seed ADR, occupancy, and LLM tab defaults to establish the canonical starting values used across projections and services.