Digital Virtual Office Workflows
Status flows for AI employees, work requests, approvals, executive plans, tasks, knowledge indexing, runtimes, work items, meetings, minutes, decisions and action items, with the action that moves each record.
Digital Virtual Office Workflows
Every record in the Digital Virtual Office moves through a fixed set of statuses. The server checks each move, so a page offers only the actions that are valid for the current status and for the signed-in person's permissions.
Hub: Target Document Flow. Overview: Digital Virtual Office. PDF: Digital Virtual Office Guide.
Request path
From an instruction to a result
flowchart TB
Person((Person)) --> Pages[DVO pages]
Pages --> Api[API /api/v1/Dvo]
Api --> Services[Services and rules]
Services --> Queue[Work queue dvo]
Queue --> Host[Runtime host]
Host --> Orch[Orchestrator]
Orch --> Router[Model router and providers]
Orch --> Check{Authority check}
Check -->|Allowed| Tools[EGKits tools through the mediator]
Check -->|Needs approval| Approval[Approval Center]
Check -->|Refused| Denied[Step denied]
Approval -->|Approved| Tools
class Person egkStart
class Pages,Api,Services egkDraft
class Queue,Host,Orch,Router egkActive
class Check egkDecision
class Tools egkSuccess
class Approval egkWarn
class Denied egkError
The authority check runs before every tool call: tool policy, configuration, grant, declared permissions, app entitlement and data scope, the requester's live permissions, and the autonomy level.
AI employees
#Statuses
Draft, Active, Suspended, Archived
Employee lifecycle
flowchart TB Start((Hire or apply template)) --> Draft[Draft] Draft -->|Activate| Active[Active] Active -->|Suspend with reason| Suspended[Suspended] Suspended -->|Activate| Active Draft -->|Archive with reason| Archived[Archived] Active -->|Archive with reason| Archived Suspended -->|Archive with reason| Archived Archived -->|Restore| Draft class Start egkStart class Draft egkDraft class Active egkSuccess class Suspended egkWarn class Archived egkTerminal
| Action | Enabled when | Notes |
|---|---|---|
| Activate | Draft or Suspended |
A saved configuration version is required |
| Suspend | Active |
A reason is required |
| Archive | Not Archived |
A reason is required; direct reports move to the employee's manager |
| Restore | Archived |
Returns as Draft so a person reviews it before it works again |
Work requests
#Statuses
Queued, Running, WaitingForDelegates, WaitingForInput, WaitingForApproval, Blocked, Succeeded, Failed, Cancelled
Work request lifecycle
flowchart TB Start((Start work)) --> Queued[Queued] Queued --> Running[Running] Running -->|Delegate| WaitDel[Waiting for delegates] WaitDel -->|Delegates finish| Queued Running -->|Ask or escalate| WaitIn[Waiting for input] WaitIn -->|Person replies| Queued Running -->|Tool needs approval| WaitAp[Waiting for approval] WaitAp -->|Decided or expired| Queued Running -->|Budget, quota or configuration| Blocked[Blocked] Blocked -->|Resume| Queued Running -->|Submit result| Succeeded[Succeeded] Running -->|Coded failure| Failed[Failed] class Start egkStart class Queued egkDraft class Running egkActive class WaitDel,WaitIn,WaitAp,Blocked egkWarn class Succeeded egkSuccess class Failed egkError
Cancel paths
flowchart TB Queued[Queued] -->|Cancel| Cancelled[Cancelled] Running[Running] -->|Cancel| Cancelled Waiting[Waiting or Blocked] -->|Cancel| Cancelled Cancelled --> Children[Delegated children and open approvals cancelled] class Queued,Running egkActive class Waiting egkWarn class Cancelled,Children egkTerminal
| Scenario | Result |
|---|---|
| The employee delegates to its team | WaitingForDelegates until every delegate finishes |
| The employee asks a question | WaitingForInput; the reply box appears on the request page |
| A tool needs approval | WaitingForApproval; the request appears in the Approval Center |
| A budget is used up | Blocked before the next model call; Resume after the limit is raised |
| The provider fails after all retries | Failed with provider.failed; no result is invented |
| The server restarts mid-run | Resumes from the last completed step |
Approvals
#Statuses
Pending, Approved, Consumed, Rejected, Expired, Cancelled, Invalidated
Approval lifecycle
flowchart TB Start((Tool needs approval)) --> Pending[Waiting for a decision] Pending -->|Approve| Approved[Approved] Approved -->|Operation runs once| Consumed[Used] Pending -->|Reject| Rejected[Rejected] Pending -->|72 hours by default| Expired[Expired] Pending -->|Work ends| Cancelled[Cancelled] Approved -->|Work ends before use| Cancelled Approved -->|Input changed| Invalidated[Input changed] Invalidated -.->|New approval requested| Pending class Start egkStart class Pending egkWarn class Approved egkActive class Consumed egkSuccess class Rejected,Invalidated egkError class Expired,Cancelled egkTerminal
| Rule | Detail |
|---|---|
| Who may decide | A person with DvoApprovals Approve or Reject who also holds every permission the operation uses |
| Never | An AI execution, including on its own request |
| Irreversible operations | Need someone other than the person who requested the work |
| Binding | The operation runs only if its SHA-256 fingerprint still matches and the approval is unused |
| Rejection or expiry | Reaches the model as a refusal with the reason; the work continues without that action |
Executive plans
#Statuses
Drafting, Proposed, Dispatched, Discarded, Failed
Plan lifecycle
flowchart TB Start((New plan)) --> Drafting[Being prepared] Drafting -->|Planner proposes| Proposed[Ready for review] Drafting -->|No plan produced| Failed[Failed] Proposed -->|Requester starts selected steps| Dispatched[Started] Proposed -->|Requester discards| Discarded[Discarded] Dispatched --> Steps[Each step becomes a work request and a board task] class Start egkStart class Drafting egkActive class Proposed egkWarn class Dispatched,Steps egkSuccess class Failed egkError class Discarded egkTerminal
The planner may only propose a plan or ask a question; any other tool call is refused with planning.only. Only the requester can start steps or discard the plan.
Tasks
#Statuses
Draft, PendingApproval, Ready, Assigned, InProgress, WaitingForInput, WaitingForApproval, Blocked, Completed, Failed, Cancelled
Task lifecycle
flowchart TB Start((Create task)) --> Draft[Draft] Draft -->|Submit, approval needed| Pending[Waiting for approval] Draft -->|Submit, no assignee| Ready[Ready] Draft -->|Submit, assignee set| Assigned[Assigned] Pending -->|Approve| Ready Pending -->|Approve with assignee| Assigned Pending -->|Reject| Draft Ready -->|Assign| Assigned Assigned -->|Unassign| Ready Assigned -->|Start| InProgress[In progress] InProgress -->|Execution succeeded| Completed[Completed] InProgress -->|Execution failed or cancelled| Failed[Failed] Failed -->|Start again| InProgress class Start egkStart class Draft egkDraft class Pending egkWarn class Ready,Assigned egkDraft class InProgress egkActive class Completed egkSuccess class Failed egkError
While in progress the task follows its work request
flowchart TB InProgress[In progress] <--> WaitIn[Waiting for input] InProgress <--> WaitAp[Waiting for an action approval] InProgress <--> Blocked[Blocked] InProgress -->|Cancel| Cancelled[Cancelled] class InProgress egkActive class WaitIn,WaitAp,Blocked egkWarn class Cancelled egkTerminal
| Action | Enabled when |
|---|---|
| Submit | Draft |
| Approve / Reject | PendingApproval, by a person other than the author |
| Assign / Unassign | Draft, PendingApproval, Ready, Assigned or Failed |
| Start | Assigned or Failed; now, or once every dependency is completed |
| Cancel | Any status except Completed and Cancelled |
A task never shows as running without work behind it: the execution is queued in the same save that moves the task to InProgress. Board drag and drop uses the same rules and offers only valid drop targets.
Knowledge indexing
#Statuses
Pending, Indexed, KeywordOnly, Unsupported, Failed, Superseded
Indexing of a document version
flowchart TB Start((Upload or text)) --> Pending[Indexing] Pending -->|Embedding model available| Indexed[Indexed] Pending -->|No embedding model| Keyword[Keyword search only] Pending -->|File has no readable text| Unsupported[Not searchable] Pending -->|Error| Failed[Indexing failed] Failed -->|Re-index| Pending Indexed -->|New version uploaded| Superseded[Replaced by a newer version] Keyword -->|New version uploaded| Superseded class Start egkStart class Pending egkActive class Indexed egkSuccess class Keyword egkWarn class Unsupported,Superseded egkTerminal class Failed egkError
Only the current version of an active document is searched, and only when an access rule allows the employee and the requester may read the document.
Runtime and work items
#Runtime statuses
Provisioning, Active, Suspended, Retained, Failed
Tenant runtime lifecycle
flowchart TB Start((dvo app enabled)) --> Provisioning[Provisioning] Provisioning -->|Isolation verified| Active[Active] Provisioning -->|Error| Failed[Failed] Failed -->|Isolation verified| Active Active -->|Suspend| Suspended[Suspended] Suspended -->|Resume| Active Active -->|App removed or deprovisioned| Retained[Retained, data kept] Suspended -->|App removed or deprovisioned| Retained Retained -->|Resume| Active class Start egkStart class Provisioning egkDraft class Active egkSuccess class Suspended egkWarn class Retained egkTerminal class Failed egkError
A runtime suspended by the platform can only be resumed by the platform. Suspending keeps queued work queued and refuses new submissions.
#Work item statuses
Pending, Leased, Parked, Succeeded, DeadLettered, Cancelled
Work item lifecycle
flowchart TB Start((Submit)) --> Pending[Pending] Pending -->|Dispatcher claims| Leased[Running, leased] Leased -->|Done| Succeeded[Succeeded] Leased -->|Waits for a person| Parked[Parked] Parked -->|Person acts| Pending Leased -->|Error or expired lease, attempts left| Pending Leased -->|Last attempt or permanent error| Dead[Dead-lettered] Leased -->|Runtime suspended, attempt not used| Pending Dead -->|Requeue on the Runtime page| Pending Pending -->|Cancel| Cancelled[Cancelled] class Start egkStart class Pending egkDraft class Leased egkActive class Parked egkWarn class Succeeded egkSuccess class Dead egkError class Cancelled egkTerminal
Retries wait with a growing backoff. Requeueing gives a dead-lettered item a fresh attempt budget, and the action is audited.
Meetings and their results
#Meeting statuses
Scheduled, Live, Processing (shown as Drafting results), Completed, Cancelled
Meeting lifecycle
flowchart TB
Start((New meeting)) --> Scheduled[Scheduled]
Scheduled -->|Start, or the time of a meeting of AI employees only| Live[Live]
Scheduled -->|Cancel with reason| Cancelled[Cancelled]
Live -->|End, idle time, agenda finished or limit reached| Ending{Transcript kept and something said?}
Ending -->|Yes| Processing[Drafting results]
Ending -->|No| Completed[Completed]
Processing -->|Minutes drafted, failed or invalid| Completed
class Start egkStart
class Scheduled egkDraft
class Live egkActive
class Ending egkDecision
class Processing egkWarn
class Completed egkSuccess
class Cancelled egkTerminal
| Action | Enabled when | Notes |
|---|---|---|
| Edit | Scheduled |
The owner or the human moderator changes the details, people and agenda |
| Start | Scheduled |
The owner or the human moderator. A meeting of AI employees only starts by itself at its time |
| Join | Live |
An invited person joins before speaking, and consents when a transcript or recording is kept |
| Next topic | Live |
The owner or the moderator |
| Interrupt | Live |
The owner or the moderator stops every answer being prepared; a participant in the room stops the answers they asked for |
| End | Live |
The owner or the moderator. The meeting also ends after the idle time (30 minutes by default) and, for AI employees only, when the agenda or a limit is reached |
| Cancel | Scheduled |
With a reason. A live meeting is ended, never cancelled |
When a meeting ends, open AI turns are cancelled and recording stops. A transcript the workspace does not keep is removed, and no minutes are drafted. A repeating meeting gets its next occurrence.
#AI turn statuses
Queued, Answered, Failed, Skipped, Interrupted
Each turn is a real work request. Its answer is added to the transcript only when the work succeeds. A failed turn adds a line saying the AI employee did not answer, and the meeting job recovers turns left behind by a restart.
#Minutes statuses
Draft, Approved, Superseded (shown as Replaced)
Minutes versions
flowchart TB Start((Meeting ends or Draft again)) --> Work[AI participant drafts as real work] Edit((A person edits)) --> Draft[Draft] Work -->|Matches the schema| Draft Work -->|Fails or does not match| Event[Reason shown in the meeting, nothing saved] Draft -->|Approve| Approved[Approved] Draft -->|Newer draft or another version approved| Superseded[Replaced] class Start,Edit egkStart class Work egkActive class Draft egkDraft class Event egkError class Approved egkSuccess class Superseded egkTerminal
Approving needs the DvoMeetings Approve action and a place in the meeting as owner, moderator or speaking participant. An approved version never changes. Editing creates a new draft, and the owner and the human moderator are told once for each drafted version.
#Decision statuses
Confirmed, Withdrawn
Decisions
flowchart TB Source((Transcript line, proposal or own words)) -->|A person confirms| Confirmed[Confirmed] Confirmed -->|Withdraw| Withdrawn[Withdrawn, kept in history] class Source egkStart class Confirmed egkSuccess class Withdrawn egkTerminal
A decision exists only when a person confirms it. Nothing the AI suggests is a decision by itself.
#Action item statuses
Draft (shown as To review), Approved, Rejected, TaskCreated
From action item to task
flowchart TB Start((Proposed in the minutes or added by a person)) --> Draft[To review] Draft -->|Edit| Draft Draft -->|Approve, assignee chosen| Approved[Approved] Draft -->|Reject with optional reason| Rejected[Rejected] Approved -->|AI assignee: automatic or Create task| TaskCreated[Task created] TaskCreated --> Task[Task follows its real work] class Start egkStart class Draft egkDraft class Approved egkWarn class Rejected egkTerminal class TaskCreated,Task egkSuccess
| Action | Enabled when | Notes |
|---|---|---|
| Edit | To review |
Title, assignee, priority, due date and deliverable. Restricted work stays marked as restricted |
| Approve | To review |
A person only, and an assignee (AI employee or person) is required |
| Reject | To review |
With an optional reason |
| Create task | Approved, AI assignee |
Needs task Create permission. Automatic when the workspace creates meeting tasks automatically. At most one task per item |
A task for restricted work (financial, external, production or destructive) waits in the Approval Center before any work starts. The owner is told when a meeting task's real work completes.
#Post-action sync
Pages reload the record after every action and refresh live when the work changes, so menus offer only the actions valid for the new status. A stale screen gets a conflict instead of a second decision.