What are data views?
Data views are saved presentations of context registry data — curated ways to filter, group, and display information from your entity types and context types without rebuilding a query every time. Where context operations define how to read or write data, data views define how results should be experienced — which columns matter, which filters apply by default, and how overseers or agents should scan the information.Screenshot placeholder
Views landing page (
/v) — when catalog is live, show list of saved views with names and linked entity types.Views vs. operations vs. pages
Operations fetch the data. Views shape how operators explore it inside registry tooling. Pages publish that experience to end users in your app.
Current status
The Views catalog in Intelligent Registries is expanding. The route exists (/v for the list, /v/[view-id] for detail) so your workspace can adopt saved views as they roll out.
If you open Views today and see a placeholder, that is expected — the navigation and detail routes are ready; the full catalog UI is coming soon. You can still plan view names and column needs with your team or the Use Case Brainstorm agent in Evolve.
Screenshot placeholder
Views placeholder page (“Coming soon”) — replace when catalog ships; or mockup of intended list UI with view name, entity type, last updated.
When to use data views (planned workflows)
Even before the catalog is complete, it helps to think about views you will want:
Each view will tie to underlying context operations and entity types — design those first in Entity types & context types and Context operations.