Runtime scripting and recipes

Documentation status: guide — see Maturity and evidence.

This section explains the programmable layer used when declarative metadata alone is not enough. The public documentation uses functionalP (also called FPL in runtime material) as a runtime expression language for computations, action bodies, page behavior, process fragments, and graph-oriented operations.

The important boundary is:

YAML/XML metadata -> declares the application model
H-Logic          -> expresses conceptual logic
functionalP      -> implements procedural behavior where needed
.NET SDK         -> accesses published Runtime capabilities from C# or F#

Public examples intentionally use capability-oriented names and never expose historical T-prefixed implementation class names.

Fast paths

• FunctionalP basics
• Actions and results
• Runtime recipes
• FPL and ABI

Recommended path

1. functionalP essentials
2. Expressions and variables
3. Lists, functions and control flow
4. Runtime objects and dot expressions
5. Actions and result contracts
6. DataSets and page scripts
7. Events and processes
8. Runtime recipes
9. Diagnostics and boundaries
10. Reproduction checklist

Maturity

The pages in this section reproduce the practical subset described by the declarative guide. Exact module-specific runtime members should still be checked against the current module/runtime contract before being promoted to reference status.