Documentation Map

English | 简体中文

Applies to DecisioWorks v1.4.0

Documentation map: start with the task

This Wiki is organized around reader tasks rather than repository folders.

Reading mode	Audience	Question answered	Start here
Tutorial	First-time users and trainers	How do I complete an observable scenario run?	Scenario Learning Guide
How-to guide	Delivery, consulting, and data teams	How do I prepare data, configure rules, and compare alternatives?	Quick Start, ERP/MES Data Mapping
Reference	Developers and integration partners	What do fields, actions, recipes, states, and errors mean?	Developer Guide Index
Explanation	Decision makers, architects, and partners	Why use a layered toolkit instead of a closed project system?	Design Principles and Differentiation

Three shortest routes

For guided study, use the Learning Center. Choose a task-based path through eight topics, work through 24 lessons, and retain the four worksheets as records of your decisions.

Manufacturers: scenarios and pain points → typical value entry scenarios → value validation → stamping case → Web cockpit.

Delivery and consulting partners: production-decision data assets → standardized data interface → readiness checks → objectives and rules → results and feedback.

Developers: architecture → component responsibilities → data-object reference → actions and recipes → runtime status and errors.

Evidence levels

Engineering definitions come from the current source and configuration. Dataset sizes come from read-only inspection of the reference samples. Solver outcomes are stated only when a retained formal validation record exists. If the current environment cannot reproduce a run, the limitation is stated explicitly.