Operational Patterns
Six workspaces show how OPERATOR components come together in a product. Each has one fictional setting, its own working layout, and controls you can use.
Industrial
| Pattern | Product view | Work it supports |
|---|---|---|
| Asset Management | Equipment register and inspector | Find equipment, inspect condition, create records and revise service assignments. |
| Facility Monitoring | Camera and telemetry console | Review industrial camera evidence, measurements and events at the same moment. |
| Maintenance Planning | Resource lanes and work-order inspector | Schedule service windows, review dependencies and resolve resource conflicts. |
Military
| Pattern | Product view | Work it supports |
|---|---|---|
| Operations Map | Area map and linked reports | Locate reported teams and equipment, inspect freshness and uncertainty, and annotate a site. |
| Incident Response | Priority queue and case workspace | Take ownership, review evidence, resolve support incidents and hand over work. |
| Communications Console | Channel list, conversation and composer | Exchange local example messages, track delivery and acknowledgment, and retain drafts through connection changes. |
Use Open workspace on any pattern to explore it at full width. Each example has a dedicated context; edits stay in memory for the session. The shared components remain usable in either domain.
Use a recipe
Recipes are application source, composed from the public component APIs. Copy the source bundle from the pattern page or install it through the CLI. The manifest includes every local module and its package dependencies. Applications supply persistence, permissions, reporting policies and service adapters.
Shared detail presentation
EntityPreview presents identity, facts, condition and report quality. DescriptionList with layout="details" provides the same label-left, value-right arrangement for other metadata. Status labels use the text-only Badge appearance in dense views.