Needs you
1 Resolve billing dispute Approval required · 3/4 tasks Formal delivery 2/3
Awaken Workforce · work, responsibility, and acceptance
Early preview Early access by requestCommission a result. Keep work moving until it is accepted.
Use one workspace to commission an outcome, see where people must intervene, follow Agent and human work, and close only when the declared deliverables are ready for review.
For process owners, operations teams, automation architects, and anyone accountable for a result that cannot end with an Agent response alone.
Current product workspace · controlled example content, not customer activity
Awaken Workforce / Customer operations
Active Workspace
Customer operations
Intervene where acceptance, evidence, or execution needs you.
- 01 Commission
- 02 Decompose
- 03 Execute
- 04 Accept
AI workforce
Outcome command
In progress
1 Onboard enterprise customer Agent WorkUnit running · 2/5 tasks Formal delivery 1/3
Blocked
1 Restore supplier account Waiting for ERP confirmation · 1/3 tasks Formal delivery 0/2
Acceptance boundary
Formal deliverables
Account correction Accepted
Refund receipt Accepted
Ledger confirmation Awaiting
Formal delivery is incomplete Acceptance remains unavailable until every declared deliverable is present.
Acceptance unavailable Modeled on the committed Workspace, Project, Chats, Canvases, Outcomes, and Outcome Review surfaces at source revision b75e0ff9. Chats projects Awaken conversation state; Canvases projects Objects resources. Example records are illustrative and are not customer results.
One visible delivery path
From commissioned outcome to a decision backed by deliverables.
The product follows the same four stages shown in Workspace Home. Issues and WorkUnits preserve accountability underneath; Needs you collects decisions and exceptions; Outcome Review keeps delivery evidence separate from technical run output.
01 Commission
Define the result, owner, acceptance boundary, and exact Workflow binding.
02 Decompose
Turn the result into an accountable Issue graph with visible dependencies.
03 Execute
Agents, people, and automations complete WorkUnits and return typed evidence.
04 Accept
Review the declared deliverables and record the business decision on the root Outcome.
A completed Agent Run settles one execution attempt. It does not close an Issue whose declared completion conditions or external acceptance facts are still missing.
Three products, one accountable path
Workforce: coordinate the work. Objects: ground it in business facts. Agents: execute it.
The console brings the three products into one delivery experience without merging their records or responsibilities.
01 · Commission and accept
Awaken Workforce
Owns Outcome, Issue, Workflow, responsibility, Attention, formal deliverables, and the final business decision.
Outcome · Issue · Workflow · Attention · Acceptance
02 · Ground and verify
Awaken Objects
Owns the typed objects, relationships, allowed actions, external observations, provenance, and exact business revisions used by the work.
ResourceType · Resource · Relation · Action · Observation
03 · Execute and recover
Awaken Agents
Owns Agent publication, Session, Run, tools, Worker, Sandbox, committed execution history, and technical recovery.
Agent · Session · Run · Worker · Sandbox
Workforce commissions → Objects grounds context and actions → Agents executes → evidence returns → Workforce accepts
Runs and Agent Center are Agents capabilities projected into the composed console. Resources are Objects capabilities. Their presence does not transfer ownership to Workforce.
Jobs that fit
Start where work crosses a boundary and somebody still has to follow up.
These are example shapes, not prebuilt industry solutions. Each one requires the Pack, Connector, or verifier that owns its business facts.
Customer operations
Resolve a case across support, billing, and approval
The Issue stays open while Agents gather context and prepare actions; the customer or business system supplies the accepted resolution.
Software delivery
Implement, review, and confirm one bounded change
A repository and CI can return the exact revision and check result required before the work is accepted.
Operational exception
Recover a recurring process that stopped between systems
Routine retries continue under policy; missing authority or an unresolved decision reaches a named person as Attention.
What Workforce owns beyond Agent execution
Keep the work understandable between runs.
An Agent can plan and act. Workforce keeps the surrounding job intact: who owns it, which revision applies, what the next step needs, why progress stopped, and which result the owning system accepted.
What Workforce owns beyond Agent execution
Without a work layer
With Workforce
Know what is still open
Without a work layer
A run or chat ends, and the team reconstructs the remaining work from messages and logs.
With Workforce
One Issue keeps the owner, process state, attempts, outputs, approvals, Attention, and completion facts together.
Recorded as: Issue · WorkflowRevision · WorkUnit · Assignment
State what done means
Without a work layer
Prompts and node code reinterpret readiness, outputs, policy, and completion on every path.
With Workforce
Named hand-offs, guards, approvals, and typed Resources make declared checks executable. A Connector or verifier supplies external truth.
Recorded as: ResourceType · Ruling · Requirement · Transition
Send exceptions to the right person
Without a work layer
People watch routine progress and search transcripts to learn why work stopped.
With Workforce
Routine cases advance automatically. Approval and Attention return ambiguity, policy exceptions, and consequential actions with a recorded reason.
Recorded as: Ruling · Approval · AttentionSignal · scheduling projection
Bring one recurring job all the way to an accepted result.
See the complete outcome loop first. Apply for a focused validation when the job needs real system connections, exceptions, and acceptance facts.