AWP / DIGITAL EMPLOYEE LIFECYCLE

From employee creation
to auditable execution.

The AWP user journey is a 15-step controlled lifecycle. A Digital Employee is configured, connected to knowledge and tools, authorised, engaged through a workspace, then evaluated and audited.

15 defined stepsProvider & tool validationEvidence-first investigationEnd-to-end audit
THE 15-STEP USER JOURNEY

Prepare the employee.
Prove the capability. Govern the work.

Each step has an end-user objective, a named AWP module, expected inputs and a defined outcome. The sequence below preserves the supplied journey and module terminology.

01

Create Employee

Digital Employee Factory
INPUT

Employee name, archetype, domain, role and initial purpose

OUTCOME

Digital Employee created and available for downstream modules

02

Define

Employee Blueprint
INPUT

Role, objectives, responsibilities, skills, operating boundaries and escalation rules

OUTCOME

Employee blueprint establishes what the Digital Employee is expected to do

03

Select MCP

MCP Provider Selection
INPUT

Available providers, provider purpose and data boundary

OUTCOME

Selected MCP provider is carried through the workflow

04

Knowledge

Knowledge Binding
INPUT

Knowledge source, scope and applicable domain/process information

OUTCOME

Knowledge context is bound to the selected Digital Employee

05

Target Process Context

Target Process Context
INPUT

Process variable/target, tag, business description and process context

OUTCOME

Target resolves to a known industrial variable with name, description and meaning

06

Health

MCP Provider Health
INPUT

Selected MCP provider

OUTCOME

Provider connectivity and readiness are confirmed

07

Discover

MCP Tool Discovery
INPUT

Selected provider

OUTCOME

Available capabilities and tools are discovered with descriptions and operating modes

08

Test

MCP Tool Test
INPUT

Selected tool, required arguments and target variable

OUTCOME

Real MCP invocation is executed and the tool response verified

09

Authorise

Employee Capabilities
INPUT

Employee, MCP tools, permissions and policies

OUTCOME

Authorised tool and capability set established for the employee

10

Ask

Digital Employee Workspace
INPUT

Natural-language business or engineering request

OUTCOME

Request captured against the selected employee, provider, knowledge and target

11

Execute

Live Investigation
INPUT

User request, employee, target and authorised capabilities

OUTCOME

Employee understands → plans → AWP authorises → MCP executes → evidence is generated → answer is produced

12

Evidence

Evidence Explorer
INPUT

Investigation/run ID

OUTCOME

Evidence objects, MCP calls, sources, results, confidence and provenance displayed

13

Trace

Investigation Trace
INPUT

Investigation/run ID

OUTCOME

Decision trajectory: objective → plan → authorisation → tools → evidence → conclusion

14

Evaluate

Evaluation
INPUT

Completed investigation/run

OUTCOME

Task completion, tool selection, policy compliance, trajectory completeness, evidence grounding and overall score

15

Audit

Audit Governance
INPUT

Run ID, employee, tool invocations and policy decisions

OUTCOME

Durable audit trail showing who, what, when, tool, policy, evidence and run outcome

INVESTIGATION FUNCTIONAL STACK

One request. A controlled
evidence-producing workflow.

01User request
02Understand intent and resolve target
03Generate plan and select tools
04Check employee permissions and policy
05Call authorised MCP tools
06Store evidence and provenance
07Analyse evidence and identify limitations
08Present findings and next steps
The Digital Employee does not bypass the permission layer. AWP validates employee capabilities and policy before authorised tool execution. Evidence and tool metadata are captured for review.