Actions Recipes and Execution Reference

English | 简体中文

Applies to DecisioWorks v1.4.0

Actions, recipes, and execution reference

A standard action states what to do, a capability handler implements it, and a recipe selects capabilities, parameters, and order for a scenario.

Standard actions

Action	Key input	Key output	Status
data_acquisition	source, source type, validation configuration	business_data, data-interface specification metadata	Implemented
constraint_parsing	Business data, engine_type	Prepared production engine and structured constraints	Implemented
objective_construction	Objective terms, directions, weights	Objective system, original and governed weights	Implemented
solution_generation	Production engine, solver parameters	Planning result and candidates	Implemented
solution_selection	Candidate solutions	best_solution	Implemented
solution_evaluation	Planning result, business data	production_analysis	Implemented
execution_dispatch	Optional standalone result file	Dispatch record	Implemented; skipped when not configured
impact_analysis	Planning report, rules or agreed operational decisions	Impact report, biases, and signals	Implemented
local_adjustment	Explicit rules and adjustment items	Solver-independent local constraints	Implemented
disturbance_detection	Events or state changes	Disturbance list	Planned
collaborative_reconstruction	Local decisions	Coordinated candidates	Planned

Actions marked Planned do not yet have callable implementations. Use implemented, registered actions when writing an executable recipe.

Top-level recipe fields

Field	Purpose	What to check
recipe_version	Recipe structure version	Manage separately from the product release version
name/purpose	Stable identifier and business purpose	Use a recognizable name and describe the business task clearly
register	Register capability functions	Dotted import paths must exist and resolve to callable functions
pipeline	Standard-action sequence	Actions must be registered and resolvable
context.inputs	Data, production, objective, and rule configuration	Use paths relative to the distribution directory
expected_outputs	Acceptance statements for people and Agents	Executable tests must still assert the expected behavior
safety	Persistence and runtime guidance	These declarations do not replace safety controls in code

Where to write in DecisionContext

• Store original requests and configuration in inputs.
• Store reusable intermediate material in derived.
• Store structured rules in constraints.
• Store candidates and the selected result in solutions and best_solution.
• Store runtime, audit, and diagnostic information in metadata and history.

Execution modes

Pipeline supports linear planning and scheduling flows. DAG supports parallel branches with explicit dependencies. FSM supports state-driven responses with bounded iteration. Action failures should return a controlled failed result rather than let an unhandled exception interrupt the entire chain.

Persistence rules

Structural data comes from the standard interface. execution_dispatch can write only an explicitly configured standalone JSON result file. Do not use data.db as the dispatch output target.