Author and run rules and calculations

Rules and calculated members are authored and reopened as Python source. Typed SDK primitives construct the compiled definitions; the fixed core validates, stores and executes them.

1. Draft source with explicit typed inputs and full effect scope.
2. Save, validate, Test and activate. Save automatically starts validation. Test uses actual bindings in private state. Activation names the exact reviewed build for a returned definition and creates its source binding atomically.
3. Run the active version under current authority. Inspect actual checkpoints and published results. Editing produces another inactive source version.

Build parameters control source construction. Definition parameters bind a returned rule or member list at Test or evaluation time. Keep these identities separate in the request and result. Samples support technical validation; they do not stand in for actual business inputs.

Python source workflow · Embedded editor workflow