Runtime scripting reproduction checklist

Documentation status: guide — see Maturity and evidence.

A developer should be able to reproduce the scripting behavior of the declarative guide from this site without depending on implementation-specific class names.

Verify that your example can:

• evaluate primitive, arithmetic, comparison, and boolean expressions;
• assign local variables and an explicit Result;
• work with lists, ranges, conditions, loops, and named functions when appropriate;
• access injected runtime surfaces (Self, Sender, ObjectsContainer, PageControler, DataSetsManager);
• resolve DataSets and current view context by declared names;
• implement a declared action without moving its contract into the script;
• react to local events without automatically escalating them;
• start a declared process for cross-object or asynchronous coordination;
• create and persist a conceptual object through the runtime container/object contract;
• preserve useful source examples while using only ABI-facing names for public classes.

If an exact runtime member is not confirmed for the current module, document the pattern as guide/architecture rather than inventing a reference signature.