Experience surfaces
One application. Every useful surface.
Runtime keeps the same records, actions, rules and authority behind each experience. The interface can adapt to the moment without creating another application to reconcile.
01
Responsive web and PWA
Role-aware lists, records, forms, actions and dashboards adapt from a desk-sized workspace to focused work in the field.
one application definition02
Mobile and device context
Use location, camera, barcode or QR scanning, uploads and media capture where the application and device permissions enable them.
context at the point of work03
Documents and media
Keep operational files, generated documents and supporting media beside the records and workflow stages that give them meaning.
evidence in context04
Action-ready UI
Surface the next valid action, the information behind it and the status that follows without forcing people through disconnected screens.
work, not navigationEnterprise hierarchy and access
The experience knows who is acting, where and with what authority.
Identity is not a login bolted onto the page. Runtime uses hierarchy, role and organisation scope to shape what a person can see, decide and do inside the application.
Enterprise scopeExample authority graph
EnterpriseNorthwind Group
Business unitField services
West regionSouth region
Job titleRegional lead
Review exceptionsAssign work
Data scopeOwn region
Records · allowedSensitive ID · masked
Resolved at RuntimeMira may review ORD-2194role + job title + west region + workflow stage
Enterprise hierarchy
Represent organisations, business units, regions, teams, job titles and reporting relationships as part of application context.
Role-based authority
Control pages, records, fields, actions and workflow decisions through explicit roles, job titles and organisation scope.
Scoped data visibility
Apply record and field visibility to the user’s operating scope, with masking available where the validated application policy calls for it.
Reviewable activity
Retain the actor, application action and state change needed to inspect important operational decisions.
Collaboration in context
The conversation stays attached to the work.
Comments, mentions, ownership, activity and configured notifications keep teams aligned around the same record and process state. Exact delivery paths follow the application’s notification and connector setup.
Comments
Discuss the work on the record instead of losing context in a separate thread.
Mentions and ownership
Bring a named person or team into the exact item that needs attention.
Notifications
Route configured application events into in-product or connected notification paths.
Shared activity
See the relevant actions, changes and decisions around the work as it moves.
ORD-2194 · activity3 participants
AG
Application eventPromise risk moved from Medium to High.10:12 · Runtime
LS
Leena Shah@Mira The allocation is held. Please review the customer proposal.10:14 · Comment
MP
Mira PatelReviewing now. Keep the revised date as a proposal until approval.10:17 · Regional lead
Add a comment or mention a teammate
Brand and distribution
Your operating experience can carry your identity.
Apply approved identity, colour, typography, domains and application naming across the Runtime experience. Selected deployments may add branded mobile packaging and store distribution as an explicit release service.
AMOGAField Operations
ThemeNorthwind Indigo
Domainoperations.northwind.example
ApplicationNorthwind Field
Accessible application palette
- 01
Brand profile
identity · colour · typography · domain
- 02
Application package
responsive web · PWA · selected mobile path
- 03
Signing and review
publisher account · policy · release evidence
- 04
Distribution
managed access · Play Store · App Store where contracted
Native packaging, publisher ownership, signing, store review, release support and update responsibilities are confirmed for the selected deployment. Store acceptance is governed by the relevant store operator, not promised by the platform.
Dashboards, analytics and data movement
See the operation, then act in the same context.
Runtime brings operational insight close to the records, decisions and queues it describes. Governed data paths connect wider analytics and enterprise systems without blurring the boundary between a configured dashboard, GRID reasoning and a contracted data service.
Exception recovery · illustrativeLast 8 weeks
Open exceptions128↓ 18 this week
Median recovery6.4hexample interface data
W1W2W3W4W5W6W7W8
Operational dashboards
Bring current work, queues, exceptions and measures into role-aware views.
Reports and exports
Give authorised teams a controlled route to scheduled and on-demand operational outputs.
Data movement
Use governed import, export, API, event and ETL paths for the deployment’s approved data flows.
GRID reasoning
Ask cross-application questions with the context and authority defined for GRID, without turning a dashboard into an ungoverned data copy.
Omnichannel operations
Many channels. One governed work item.
Bring supported customer and employee touchpoints into the application context so identity, consent, routing, history and the next action can follow the work. Channel availability depends on the selected connector, provider, region, consent model and deployment.
Runtime work itemidentity · consent · state · owner
Connected conversationCustomer · C-4817
WhatsApp
Delivery-date question received.
acceptedAEGIS
Identity, consent and route policy checked.
governedRuntime
Conversation attached to ORD-2194.
contextualisedMira
Approved response sent through enabled provider.
completedAEGIS at the boundary
Connected execution stays governed and inspectable.
AEGIS applies identity, schema, scope, policy, routing and recovery controls to supported events crossing the application boundary. It is the governed path behind integrations and connected channels, not a bypass around Runtime authority.
- 01→
Receive
event · API · webhook
accepted - 02→
Validate
identity · schema · scope
checked - 03→
Govern
policy · filter · rate
controlled - 04→
Route
transform · publish · consume
traced - 05
Recover
retry · replay · review
durable
Responsive and reliable operation
Responsiveness by design. Availability by explicit agreement.
Runtime is designed for responsive interaction and operational continuity through observable, policy-governed and recoverable execution. Exact availability targets, support windows, maintenance terms and recovery objectives are confirmed for the selected deployment and service agreement.
Observe
Metrics, logs, traces and application signals expose health and failure paths.
Protect
Identity, policy and AEGIS controls govern access and connected events.
Recover
Retry, replay and durable execution support bounded recovery from interrupted work.
Agree
Availability targets, support windows, recovery objectives and exclusions belong in the deployment agreement.
Bring one operation into Runtime.
We will trace its people, devices, hierarchy, channels, data and integrations, then show how one governed application can carry the work.