Component Responsibilities

English | 中文

Applies to DecisioWorks v1.4.0

Component Responsibilities

DecisioCore modules

• data_layer: reads standardized data, validates relationships, and builds business objects.
• core, actions, registry, and execution: register capabilities, execute standard actions, and orchestrate flows.
• capabilities: exposes planning, scheduling, objectives, rule control, and linkage as callable capabilities.
• objective_system: governs objective terms, directions, weights, scope, and audit evidence.
• marginal_control: expresses operational experience, bottlenecks, consensus, and rules.
• engine_adapters: maps upper-level decisions to model and solver capabilities.
• analysis: provides aggregate metrics, detailed interpretation, and semantic audits.
• planning_system: manages plan deviations, signals, release packages, and feedback linkage.

This separation lets business, decision, model, algorithm, and presentation concerns evolve in the right place.

Layers govern change, not just directories

Each module owns a stable class of concerns: data_layer handles data changes, actions and execution handle workflow changes, the objective system handles management preferences, operational rule control (marginal_control) handles site rules, planning_system handles linkage, and adapters plus GOCK handle model evolution.

This separation makes issues diagnosable, capabilities testable, and partner extensions practical. When a scenario changes, the responsible module can change while other capabilities remain reusable through stable interfaces.

Position in one production-decision cycle

DecisioCore connects DataSets with GOCK and routes results to Web and the next feedback cycle. It is the organizational layer between plans and decisions, adding objectives, rules, actions, interpretation, and feedback around model calls.