1
Enter
The TAM logs into SpineWorkspace and lands on the Implementation Portfolio. Active implementations, health alerts, and open escalations are pre-assembled and prioritized.
2
Discover
Twin surfaces notable technical changes: integration failures, API error spikes, missed milestones, or architecture review deadlines. The TAM reviews flagged items in the Action Center.
3
Understand
Drilling into an account reveals full technical context: architecture diagrams, integration configs, API usage trends, ticket history, and deployment status. Evidence is linked across systems.
4
Contextualize
The TAM reviews prior architecture reviews, implementation milestones, and known technical debt. Twin adds comparable account patterns and platform health context.
5
Decide
Based on assembled context, the TAM selects the appropriate intervention: technical escalation, architecture guidance, integration remediation, or debt prioritization. Twin proposes ranked options.
6
Act
The TAM executes a governed capability: creating a Jira ticket, updating an implementation status, scheduling an architecture review, or documenting debt. Each action is authorized and receipted.
7
Review
Outcomes appear in the account timeline. The TAM confirms resolution, updates milestone status, and verifies that monitoring reflects improvements. Health scores recalculate automatically.
8
Continue
Session context, technical notes, and next steps persist. Coverage handoffs and agent collaboration resume with full state available through Continuity.