Work orchestration lifecycle
Select a stage to see its owner, output, and decision boundary.
Intake
Customer and strategist establish objective, inputs, deadline, and destination.
Scope & Assign
Strategist and orchestrator set acceptance criteria and route work to the right roles.
Execute
Digital Employees produce research, drafts, code, configurations, or other assigned outputs.
Validate
Apply evidence checks, relevant tests, and evaluations; unresolved failures require revision or escalation.
Human Review
Strategist and designated reviewers accept, revise, or escalate work.
Customer Approval
Authorized customer decision-maker approves consequential actions or deliverables when required.
Deliver
Finished work is returned through the agreed channel. Deployment is separately authorized.
Conceptual architecture based on documented responsibilities; this diagram does not assert that every component is deployed in production.
Work Orchestration
Work orchestration turns a customer assignment into a reviewed deliverable. The THINK Strategist manages the customer relationship and quality; team orchestrators own their team workflows. The shared THINK Harness supports routing, state, handoffs, blocked work, escalation, and human approval gates.
Lifecycle
| Stage | Responsibility | Output or decision |
|---|---|---|
| Intake | Customer and THINK Strategist | Objective, source material, deadline, delivery destination |
| Scope and assign | THINK Strategist and team orchestrator | Tasks, role assignments, acceptance criteria |
| Execute | Digital Employees and approved tools | Drafts, analysis, code, configurations, or other work |
| Validate | Appropriate team methods and tests | Evidence checks, tests, or documented exceptions |
| Human review | THINK Strategist and designated reviewers | Accept, revise, or escalate |
| Customer approval | Authorized customer decision-maker, where required | Approval, feedback, or requested revision |
| Deliver | THINK Strategist / approved delivery channel | Finished artifact or authorized solution |
Request → Scope → Execute → Validate → Human review → Customer approval when required → Deliver
Ownership and handoffs
| Component | Owns | Does not automatically own |
|---|---|---|
| THINK Strategist | Scope, coordination, exceptions, customer communication, quality review | Unapproved customer business decisions |
| Team orchestrator | Team-specific workflow and role handoffs | All shared policy or provider configuration |
| THINK Harness | Shared orchestration support, context, capability resolution, evaluations | The team-specific workflow itself |
| Digital Employee | Assigned specialized work | Unrestricted tool access or customer commitments |
| Customer approver | Decisions reserved by the engagement | Internal workforce orchestration |
The repository’s THINK-Internal/Harness/orchestration-support/README.md explicitly separates team ownership from shared Harness support.
Exception handling
| Condition | Handling principle |
|---|---|
| Missing inputs | Request clarification; do not silently invent customer facts |
| Tool or source unavailable | Record the blocker and route for approved resolution |
| Conflicting evidence | Flag the discrepancy for review |
| Unauthorized action | Stop the action and seek explicit authorization |
| Failed validation | Revise or escalate before marking work complete |
| Production deployment requested | Verify separately approved change and deployment authority |
These are operating guidance, not a claim that every exception has a deployed automatic handler.
Example: code assignment
A customer requests a repository integration. The strategist confirms requirements, permitted repository access, acceptance criteria, and whether the assignment covers code only, code plus tests, or deployment. The Managed Team implements authorized changes, runs applicable checks, and submits results for human review. Production deployment occurs only with explicit authorization.
Example: capture assignment
A customer requests an opportunity assessment. The team gathers approved sources, develops an assessment, checks evidence, and routes consequential go/no-go judgment to the appropriate human reviewer. The customer receives the reviewed assessment.
Further reading
THINK Harness and Execution · Workforce Skills · Customer Access and Data Controls · Human-Led Team Management · Service Activation