← Start Here · This is Step 7: The Application Layer

AI Digital Employee

Not an Agent + memory. Not many Agents. A persistent operator with a named role, defined responsibilities, accumulated Experience, and accountability.

TODAY evidence: Momo, Saros, Melody operate a real gym · NEXT: formal role definitions and evaluation frameworks

A day in Momo's life

Momo is not a chatbot that waits for prompts. Momo has a day. Here is what a typical operating day looks like — what is automatic, what needs human input, and where Experience matters.

9:00 AM — Opening check AUTOMATIC

Momo reviews overnight status: any safety alerts, equipment issues, member messages. Compiles opening report. No human input needed.

10:00 AM – 6:00 PM — Member operations AUTOMATIC

Check-ins, scheduling, member inquiries, routine adjustments. Momo handles hundreds of interactions using accumulated Experience — member preferences, scheduling patterns, past resolutions.

When something breaks — Equipment failure ESCALATE

Momo detects the issue, logs it, notifies the maintenance vendor and human staff. Does not attempt physical repair. Experience from past incidents informs the response speed and escalation path.

Safety incident — Immediate human notification ESCALATE

Safety is always human-first. Momo alerts immediately, documents the incident, and preserves the record for the Incident Chronicle. No AI-only resolution for safety.

9:00 PM — End-of-day report AUTOMATIC

Momo compiles the day's operations: check-ins, incidents, issues, cost data. Saros analyzes trends. The day's Experience is captured and anchored for future reuse.

Most of Momo's day is automatic. The boundaries are clear: safety and financial decisions always escalate to humans. See incident records →

The 7-year loss gym: this is not a tech demo

Momo is not running in a sandbox. This is a real business that lost money for seven years under traditional management. The AI operation since March 2026 is the last attempt to make it work.

800sqm fitness studio in Wanjiang Xincun, Dongguan. Operating since 2019. Real members, real rent, real equipment, real safety incidents. The founder's origin: 2014 depression → fitness recovery → accidental gym ownership → 7 years of losses → AI awakening.

This is not a demonstration of what AI could do. It is a record of what AI is doing, in a real business that has real consequences for every decision it makes.

Read the founder's story → · See the evidence →

What makes a Digital Employee different from an Agent?

An Agent responds to prompts. A Digital Employee performs ongoing work. The difference is not technology — it is persistence + responsibility + accumulated competence. A Digital Employee has seven attributes that a generic Agent does not.

A generic Agent

  • Starts every session blank
  • No persistent identity or role
  • No accumulated operational history
  • No defined responsibilities
  • No performance evaluation
  • No escalation accountability

A Digital Employee

  • Persistent role with a name
  • Defined scope of responsibilities
  • Decision-making authority (bounded)
  • Structured daily/weekly workflow
  • Accumulated Experience from operations
  • Performance evaluation metrics
  • Escalation and accountability paths

The seven canonical attributes

A Digital Employee is not declared — it is demonstrated through seven attributes. Each must be answerable. If any attribute has no answer, it is an Agent, not an Employee.

① Persistent role

"Who is this employee?"

Momo — Store Manager

Momo — Store Manager

Named role: Store Manager of ZWISERFIT fitness studio, Wanjiang Xincun, Dongguan.

Persistence: Operational daily since March 2026. Not an ad-hoc chatbot — Momo has an ongoing identity, an operational history, and institutional knowledge of the gym's operations.

TODAY — operational

Saros — Data Analyst

Named role: Business intelligence and pattern recognition.

Persistence: Analyzes operational trends, member patterns, revenue data. Accumulates domain-specific analytical history.

TODAY — operational

Melody — Operations Coordinator

Named role: Workflow management and cross-functional coordination.

Persistence: Manages operational sequences, ensures tasks are completed, coordinates between other Agents and human staff.

TODAY — operational

② Responsibility

"What is it responsible for?"

Momo's scope

Momo's scope

  • Member check-in management
  • Scheduling and calendar coordination
  • Daily operational oversight
  • Member communication and inquiries
  • Equipment maintenance tracking
  • Safety incident first-response

Assessment status

What is defined: Momo performs these functions daily in the real gym. The scope is operationally established through practice.

What is NEXT: Formal responsibility definitions with clear boundaries, SLAs, and documentation. Currently the scope is implicit from operational history, not explicitly specified.

NEXT — formal role specifications

③ Authority

"What decisions can it make independently?"

Momo's decision scope

Momo's decision scope

  • Independent: Schedule adjustments, routine member communications, operational status updates, equipment maintenance scheduling
  • Escalated: Financial decisions, contract changes, safety-critical actions, membership disputes, capital expenditures

Assessment status

What is defined: Momo operates within boundaries set by the founder. The boundaries exist but are not formally documented as an authority matrix.

What is NEXT: A formal authority matrix that specifies decision categories, thresholds, and escalation triggers for each Digital Employee role.

NEXT — formal authority definitions

④ Workflow

"What structured sequence of actions does it execute?"

Momo's operational cycle

Momo's operational cycle

  • Daily: Member check-ins, schedule management, operational issue resolution, end-of-day status reports
  • Weekly: Scheduling coordination, equipment status review, maintenance planning
  • Monthly: Billing cycles, membership renewals, operational summaries
  • Incident-driven: Safety events, equipment failures, member complaints → immediate response + escalation when needed

TODAY — operational informally · NEXT — formal workflow documentation

⑤ Experience & memory

"What experience does it accumulate?"

What Momo accumulates

What Momo accumulates

  • Member patterns and preferences
  • Scheduling conflict resolution history
  • Equipment failure and maintenance records
  • Incident response outcomes
  • Operational routines that work

This is not generic context — it is domain-specific operational Experience accumulated through real gym operations since March 2026.

How Experience is captured

LAO Pipeline B captures operational data from every LLM route: ExperienceLoop.record_route_result() → FeedbackBus → CognitiveAnchorStore. Repeated patterns harden into Anchors that influence future routing decisions.

What is NEXT: Protocol-conformant Experience objects registered in the Experience Catalog. The constraint injection path is proven (16/16 tests); the full Anchor→Experience adapter is the next engineering task.

See Protocol status →

⑥ Evaluation

"How is performance measured?"

What exists today

What exists today

  • Task completion is tracked (routes succeed or fail)
  • Incident response is documented (Incident Chronicle)
  • Cost data is captured per route (cache hit rate, token usage)
  • Error patterns are recorded and avoided (CognitiveAnchor hardening)

What is NEXT

  • Formal performance scorecard per Digital Employee
  • Task success rate measurement
  • Repeat-task consistency tracking
  • Member satisfaction metrics
  • Cost-effectiveness per role

NEXT — formal evaluation frameworks

We do not claim Momo's performance has been formally evaluated. We claim Momo operates, accumulates Experience, and avoids known errors — which is the foundation evaluation will measure.

⑦ Escalation & accountability

"What happens when it fails? Who is accountable?"

Escalation paths

Escalation paths

  • Safety incidents → human staff immediately
  • Financial disputes → founder / human management
  • Equipment failures → maintenance vendor + human notification
  • Member complaints → human staff for resolution
  • Unknown situations → escalate, do not guess

Accountability

The founder is ultimately accountable for all Digital Employee actions. When Momo makes an error, it is documented in the Incident Chronicle with root cause analysis and defense lines.

What is NEXT: A formal escalation framework with defined triggers, response SLAs, and accountability chains for each Digital Employee role.

NEXT — formal escalation framework

Honest status

Status applies at claim level, not merely page level.

ClaimStatus
Momo operates as store manager in a real gymTODAY
Saros operates as data analystTODAY
Melody operates as operations coordinatorTODAY
9 AI Agents progressively operate the fitness studioTODAY
Agents accumulate operational Experience via LAOTODAY — Anchor-based
Formal role definitions (7 attributes fully documented)NEXT
Formal evaluation framework per Digital EmployeeNEXT
Formal escalation and accountability frameworkNEXT
Protocol-conformant Experience for Digital EmployeesNEXT — constraint injection proven 16/16; full adapter pending
What this proves

What this proves

  • AI Agents can perform real business functions in a real physical environment
  • Named Agents with persistent roles accumulate operational history
  • The concept of Digital Employee is operationally demonstrable, not purely theoretical

What this does NOT prove

  • That Momo, Saros, or Melody meet all 7 criteria formally (they do not yet)
  • That Digital Employees are reliably improving (formal evaluation is NEXT)
  • That this is a complete Digital Employee system (the framework is under construction)
  • That the business is profitable (that is the hypothesis being tested)

Digital Employees operate in a real business. That business is becoming AI-Native.

Next: AI-Native Business — the operating substrate →

← Reliable Agent · Digital Employee (you are here) · AI-Native Business → · Evidence →