UI Projections
UI projections create model-projected wireframes that bind screen controls to projection entities. Control types are inferred automatically from data shapes, and API annotations connect screens to integration operations.
Model-Projected Wireframes
UI projections bind screen layouts to projection entities. Form fields, lists, and detail views reference real properties from the model or a projection. Control types are inferred from data shapes, so a boolean becomes a toggle, a date becomes a date picker, and an enum becomes a select. This means your wireframes stay grounded in the actual data structure rather than being aspirational drawings.
Binding to Projection Entities
UI projections bind to the target entities of a projection, not the raw model. This gives end-to-end lineage: model to projection to UI. If a projection renames a field or changes its type, the UI projection reflects that transformation. You can trace any screen control back through the projection layer to the original model property.
API Annotations
Each screen can be annotated with the API operations it consumes. Specify the endpoint, the HTTP method, and whether the screen reads or writes. This connects the UI design to the integration layer, making it clear which API calls power each screen. When an endpoint changes, you can trace the impact to every screen that depends on it.