About the 3D digital human correction

I fully align with the corrected premise:

The system layer drives execution and state.
The digital human presents, guides, and visualizes system execution and state.

This correction is accepted and will be reflected in all further definitions and acceptance standards.

About the acceptance checklist request

I confirm that I will prepare a complete, corrected, system-level prototype acceptance checklist strictly according to your requirements:

Including:

A. System layer (non-3D)

• Workflow / state / logging closed loop

• AI, translation, and process logic roles

• Log verification and replay

• Fly.io deployment acceptance form

B. 3D digital human (presentation layer)

• Walking / movement

• Facial expressions

• Lip-sync

• Gesture / pointing / orientation feedback

All defined as verifiable presentation capabilities driven by system state.

C. Full scope boundary clarification

Including:

• Payment scope at prototype stage

• Hosting / deployment form

• Plugin / extension entry scope

• Loader / loading flow

• Definition of “one complete workflow”

Each item will clearly state:

• What is included

• What is not included

D. Acceptance and payment terms

Including:

• Checklist-only acceptance

• One remediation cycle (3 working days)

• Failure after remediation = no payment and termination

E. Budget cap

• Prototype budget fixed at USD 1,100

• No hidden or implied additional scope

Corrected Prototype Acceptance Checklist

Prototype Stage — System Capability Validation

Budget cap: USD 1,100 (fixed, non-extendable)
Purpose: Minimum runnable system capability validation

A. System Layer (Core, Non-3D)

A1. Workflow Closed Loop

Requirement:
One complete workflow must execute end-to-end:

Input → AI processing → workflow decision → system output → state update → log record.

Acceptance:

• Workflow can be executed at least 2 times without restart.

• Final state is reached.

• State transitions are logged.

A2. State Machine

Requirement:

• States are predefined.

• Transitions follow rules.

• Illegal transitions are rejected.

Acceptance:

• Current state is visible via log or API.

• Illegal transition attempt produces log error.

A3. Logging & Replay

Requirement:

• Each state transition is logged.

• Log includes timestamp, state before, state after.

Acceptance:

• Log can be exported.

• Log can be manually replayed to reconstruct the workflow path.

(No automated replay engine required.)

A4. AI + Language Processing Chain

Requirement:

Input → Language detect → Translation → AI structured task.

Acceptance:

• Two different languages are accepted.

• Translated result is used for workflow decision.

• Structured AI output is visible in logs.

A5. Deployment

Requirement:

Prototype deployed on Fly.io.

Acceptance:

• Public accessible URL.

• Restart does not break workflow.

B. 3D Digital Human (Presentation Layer)

Digital human is presentation only, not system driver.

B1. Movement

• Character can move / walk.

B2. Facial Expression

• At least 2 basic expressions.

B3. Lip Sync

• Mouth moves with audio or TTS.

B4. Gesture / Pointing

• One gesture or pointing action.

B5. System Binding

• At least one workflow state triggers a digital human action.

Acceptance:

• Each of the above actions is visually observable.

(No cinematic quality, no advanced physics, no motion capture required.)

C. Plugin / Automation Entry

C1. Automation Trigger

Requirement:

• One system event triggers automation.

C2. Execution

• Automation performs one real external or internal action.

C3. Result

• Execution result is returned and logged.

Acceptance:

• Trigger → execution → result can be demonstrated.

D. Payment Scope

Prototype stage:

• Payment is placeholder / simulation only.

• No real payment processing.

• No escrow logic.

Acceptance:
Simulated payment state transition only.

E. Hosting / Loader

• Prototype loads via browser.

• Basic loading screen or progress indicator.

No optimization requirements.

F. Workflow Definition

“One complete workflow” means:

• Minimum 5 steps.

• Includes AI processing and digital human output.

No second workflow required.

G. Acceptance Rules

1. Acceptance is based only on this checklist.

2. All items are verifiable.

3. If any core item fails → prototype fails acceptance.

H. Remediation

• One remediation round.

• 3 working days.

• After remediation, final acceptance decision.

Failure after remediation → no payment, prototype stage ends.

I. Budget Rule

• Budget cap: USD 1,100

• No scope outside this checklist is included.

• Any new requirement requires written agreement.

J. Prototype Purpose

This prototype validates:

• System closed-loop logic

• Engineering feasibility

• Architectural correctness

It does not validate:

• Production performance

• Commercial readiness

• Visual polish

• Full feature completeness