LLM-State Contract — Schema Agreement Between App and AI #640
Description
Is your feature request related to a problem? Please describe.
There is no agreement between app and AI about state structure. The LLM receives widget schemas but not a state manifest, so it guesses paths, can create arbitrary ones, and can vary paths between turns. Ownership of state structure (app vs. AI) is undefined.
Describe the solution you'd like
A defined state contract: a discoverable schema/manifest of allowed paths, plus guidance on ownership. Preferably, app state is the source of truth and DataModel is a derived view, with validation for path creation.
Describe alternatives you've considered
Letting the LLM create state freely, or constraining via prompt-only guidance. Both lead to brittle results (non-reactive UIs, invented paths, or inconsistent regeneration).
Additional context
Discussion: #609