app-defaults

Centralize application default and seed configuration values by managing them in a single canonical location like the global_assumptions table and admin research-config endpoints, preventing scattered inline defaults from drifting over time. Admins set market, underwriting, and LLM tab defaults through the Admin UI to establish starting values used across projections.

The resolution precedence for app defaults follows a strict cascade: entity-level explicit value takes priority, then the App Default, then hardcoded system constants, with LLM-specific fallbacks for vendor and model resolution. Downstream services inherit these values during projection and analysis workflows.

To add new property underwriting seeds like starting ADR without inline defaults, follow the developer checklist: add the field to ModelDefaultsTab.tsx, update the API schema, and ensure downstream consumers read App Defaults as the fallback. This enforces a single source of truth for application settings.

LLM vendor and model tab defaults are persisted in researchConfig.tabDefaults and the global_assumptions table, accessible through admin research-config endpoints and managed via the Admin → App Defaults UI location. This provides canonical storage for LLM default values across services.

Yes, you can use admin research-config endpoints to set global assumptions for downstream projection services. Services inherit these canonical default values during analysis workflows, ensuring projections start from centralized market and underwriting seeds rather than scattered inline values. The Admin UI provides the interface for managing these settings.