TASK CONTRACT
ENGINEERING GOAL
Assess design risk under the specified load case
01Task boundary02Engineering context03Capability scope04Authorization rules05Acceptance criteria06Delivery requirements
PRODUCT 03 | MOZI ENGINEERING TASK AGENT
BETAFrom engineering goalsto completed tasks
MOZI keeps planning, coordination, and checks centered on a clear engineering goal, so progress stays understandable and the final result remains reviewable
01 | PRODUCT DEFINITION
One engineering goal. One task thread that keeps moving
The task contract defines the boundary. The thread keeps goals, plans, and status aligned while specialist agents and engineering capabilities join as needed; human checkpoints and result evidence stay on the same thread
MOZI | PRIMARY TASK THREAD
Keeps goals, plans, permissions, and status aligned
CURRENT STEPRisk assessment
PLAN VERSIONPLAN V03
CURRENT OWNERAnalysis Agent
PROGRESS04/06
SPECIALIST AGENTS
Context AgentCOMPLETEAnalysis AgentRUNNINGEvidence AgentQUEUED
ENGINEERING CAPABILITIES
GEWUIN USELUBANSTANDBYEnterprise AssetsLOADED
HUMAN APPROVAL | CHECKPOINT 04/06
Task ownerapproves the checkpointAPPROVEDRESULTS AND EVIDENCE
Deliver the conclusion, rationale, and full execution record together
- Result summaryGENERATED
- Decision basisREVIEWABLE
- Call historyARCHIVED
Parallel work can branch off while the primary task thread stays clear
02 | EXECUTION RECORD
Every step is tracked. Every checkpoint is approved. Every result is backed by evidence
Follow one engineering task from goal capture and planning through checkpoint approval, capability calls, and the archived resultTASK ID | MZ-BETA-017
Assess the risk of the current design under the specified load case and provide reviewable evidence01GOAL CAPTURED
Engineering goal and deliverables captured
02PLAN V03
Reviewable execution plan created
03CHECKPOINT APPROVED
Task boundary and capability path approved
04DECISION COMPLETE
Design risk assessment completed
05CALL COMPLETE
Engineering results reviewed
06ARCHIVED
Results, evidence, and call history archived
03 | PRODUCT HANDOFF
From trusted conclusions to trusted capabilities to accountable execution
GEWU captures a Trusted Engineering Utility. LUBAN builds and runs it as a Trusted Engineering App. When a task needs persistent planning, coordination, and checkpoints, MOZI carries it forward.
ONE ENGINEERING CAPABILITY | THREE PRODUCT ENTRIES
ENGINEERING CONTEXT STAYS INTACT
Validate conclusions and capture a Trusted Engineering Utility
Preserve the inputs, workflow, operating boundary, and engineering evidence
STANDARD ARTIFACT
Trusted Engineering Utility
Input boundary | validation rules | evidence chain
Package the capability as a Trusted Engineering App
Carry the Trusted Engineering Utility forward, then package, validate, and publish it
STANDARD ARTIFACT
Trusted Engineering App
Task contract | method version | acceptance criteria
Keep the task moving and preserve an accountable execution record
Maintain the task thread while coordinating engineering capabilities and human checkpoints
STANDARD ARTIFACT
Task Result & Execution Record
Goal & plan | human checkpoints | result & evidence
GEWU makes conclusions trustworthy. LUBAN makes capabilities trustworthy. MOZI makes complex-task execution controlled and auditable.
Accountable execution is grounded in an explicit goal, a governed plan, trusted capabilities, human checkpoints, and continuous evidence.
START WITH ONE TASK
Move your engineering task forward with MOZI
Bring one clearly bounded engineering task. We’ll work with you to confirm the task contract and beta scopeApply for MOZI BetaA strong first beta task has
01Clear goals and deliverables02Relevant context available03A verifiable outcome