Skip to main content
The Operations User Path is how an ops practitioner moves from discovering work to closing it with full context preserved. SpineWorkspace guides each step so nothing is lost between people, sessions, or agents.
1

Enter

Open the Operations domain. The workbench loads your personalized layout: request queue, approvals, and KPI alerts scoped to your role.
2

Discover

Review open requests, SLA warnings, and alerts. Twin highlights items that match your history and priorities.
3

Understand

Open a request to see full context: submitter profile, linked asset or vendor, related tickets, policy rules, and past resolutions for similar items.
4

Contextualize

Add notes, attach evidence, or consult the policy registry. Spine Fabric assembles related events and entity history so you can reason with the full picture.
5

Decide

Choose the next action: resolve directly, route for approval, escalate, or delegate to a domain agent for drafting a response.
6

Act

Execute the chosen action. The capability system enforces authorization, scope, and produces a receipt that records what changed and why.
7

Review

Confirm the outcome against the original request. Update the asset inventory or vendor record if the action produced a change.
8

Continue

Close the session. Continuity persists your open items, notes, and handoff context for the next practitioner or agent.
If you pause mid-ticket, Twin will surface it first on your next entry so you can resume without re-reading the history.