Skip to main content
The AI Flow in Business Operations is the loop Twin follows when processing operational events. It aligns to the standard OODA-inspired sequence, adapted to the BizOps domain.
1

Observe

Twin monitors event streams from Google Workspace, Asana, Notion, and ERP for new approvals, vendor changes, policy updates, and OKR movements.
2

Orient

Twin classifies the event by domain entity, urgency, and SLA impact. It tags it as approval, vendor risk, policy exception, or initiative change.
3

Context Assembly

Twin resolves the requester, related policy, vendor, contract, or objective, and assembles a contextual dossier from the Spine Fabric.
4

Reason

Twin evaluates against policy rules, SLA thresholds, and historical precedent. It identifies anomalies and risks.
5

Discover

Twin queries for missing context: open blockers, prior exceptions, related approvals, or pending vendor renewals.
6

Delegate

Twin routes the assembled dossier to the appropriate human or agent with a recommended action.
7

Collaborate

Twin supports back-and-forth refinement: answering questions, adding evidence, or adjusting the recommendation based on human input.
8

Decide

The human or pre-authorized agent confirms the action. Twin records the decision rationale.
9

Act

Twin invokes the governed capability, writes to the source system, and generates a receipt.
10

Continue

Twin updates continuity state so the next session or handoff retains full context.
Related