Enterprise data grid
Reusable table with selection, sorting, filtering, export, configurable columns, states and row actions.
Shared componentFuture Spec 16 →Current-state summary
A shared enterprise grid pattern appears across Teammates, Teams, Role Labels, Tasks and Files. It consistently supports headers, sorting, Export and Columns, with optional search, filters, selection and bulk actions. Domain coverage varies: some grids have rich metrics and filters while others expose only a basic zero state, and shared taxonomies are not always synchronized with builder options.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Query controls | Search, filters and sort appear by domain, but availability and labels vary. | Verified across live grids |
| Columns | Column selector is common; persistence and per-user saved views are unverified. | Visible |
| Selection and bulk actions | Tasks supports row selection and bulk State change; other domains vary. | Verified without mutation |
| Export | Common action; output, permission redaction and audit were not exercised. | Visible only |
| States | Loading, populated and empty states exist but do not always preserve stable layout or explain unavailable functionality. | Verified |
User journeys
Current flows
Find and act on records
- Open directory
- Resolve authorized dataset
- Search/filter/sort
- Configure columns
- Select permitted records
- Preview bulk action
- Execute with per-record validation
- Audit/export result
State model
Current and expected states
Some metrics flash zero while records resolve.
Tables render with domain-specific quality.
Core row and action patterns are present.
Bulk controls appear where supported.
Not explicitly represented.
Product rules
Non-negotiable boundaries
- All query, count, export and bulk operations use the same permission-scoped dataset.
- Columns and filters use canonical field definitions.
- Bulk actions validate each record and return partial-failure detail.
- Exports never bypass field permissions.
- Table keyboard and screen-reader semantics are mandatory.
Known current limitations · 5 mapped
What is missing, broken or unverified
Future Spec 16 owns closure →- No saved views.
- Column persistence unverified.
- Export output/audit unverified.
- Taxonomy conflicts can make valid records unfilterable.
- Loading metrics may briefly misrepresent zero.
Future alignment
Required evolution
- 01Make the grid a documented shared component with domain adapters.
- 02Add saved views, URL state, server-side query, accessible virtualization and export jobs.
- 03Standardize empty, error, redacted and partial-failure states.
Current baseline
Acceptance record
- Counts and rows reconcile.
- All visible columns and filters share canonical fields.
- Export and bulk actions honor permissions.
- Every state is accessible and explicit.
Reverse-spec completeness
Documentation coverage
The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.
Purpose and user outcome
DocumentedRoles and access
DocumentedRoutes and entry points
DocumentedPage and component anatomy
DocumentedFields and displayed data
DocumentedPrimary actions
DocumentedForms and validation
DocumentedStates and transitions
DocumentedEmpty, loading and error states
DocumentedResponsive behavior
PartialAccessibility behavior
PartialActivity and audit events
PartialData sources and persistence
DocumentedNotifications and automation
PartialKnown defects and limitations
DocumentedReusable component dependencies
DocumentedFuture-spec conflicts
PartialVisual and repository evidence
DeferredAcceptance of current baseline
Documented