Human Workbench
The daily surface for BizOps practitioners: tabs, tasks, and approvals.
AI Workbench
How Twin assembles, proposes, and delegates operational work.
System Flow
How Spine ingests operations data and projects it into this domain.
Execution Flow
The governed path from intent to source-system action and receipt.
- Process: defined operational procedures with steps, owners, and SLA thresholds.
- Workflow: an instance of a process running through Spine with state, handoffs, and approvals.
- Approval: a governed decision gate with authorization scope and audit receipt.
- Vendor: an external party record tied to contracts, spend, and risk assessments.
- Contract: a legal agreement tracked through lifecycle stages and renewals.
- Policy: an organizational rule with version history, attestations, and exceptions.
- OKR: an objective with linked key results, owners, and progress evidence.
- Initiative: a scoped project or program with timeline, resources, and outcomes.
- Active Initiatives: current programs with status, blockers, and resource allocation.
- Pending Approvals: open decision gates requiring human or agent action.
- Vendor Portfolio: all vendors with contract status, risk tier, and renewal dates.
- Process Health: SLA adherence, bottleneck frequency, and throughput trends.
- Approval: intake, triage, stakeholder routing, decision, source-system update, receipt.
- Vendor Onboarding: request, due diligence, contract association, system provisioning.
- Policy Review: draft, review cycle, attestation campaign, exception tracking.
- OKR Cycle: define, align, commit, progress updates, closeout.
- Process Improvement: discovery, proposal, pilot, measurement, rollout.
Domain
Operating model, responsibilities, and KPIs for Business Operations.
Domain Views
Detailed table of views and projection rules.
Business Context
Entities, relationships, events, and evidence in BizOps.
Integrations
Source systems feeding operational data into Spine.