You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bind ordered UK Scenario modifiers within each data-load phase #755
The UK Budget dashboard needs receipts for several ordered modifiers before and after data loading. #752 binds the two phases, but each phase still requires a single module-level modifier. Native Scenario addition can combine two such modifiers into an internal closure, which the binder refuses.
Add an explicit ordered execution plan that constructs a native Scenario and binds the execution it supplies:
Accept actual trusted module-level callables in both phases, preserve their order and retain repeated occurrences.
Apply the caller's complete parameter map once before loading data, so a shared policy rollback does not overwrite earlier member changes.
Bind each callable's source, module source, typed defaults and repository revision, together with the adapter and complete phase order. Recheck the live parameters, callables, revisions and native timing before accepting execution receipts.
Validate and recompute a portable plan's identity from data without importing or executing module names carried in that plan. Workers must supply their actual trusted callables and match the complete plan before execution.
Preserve existing valid Scenario, phased Scenario and legacy composition digests. Refuse attempts to flatten an ordered plan through a representation that cannot express its timing.
Cover two noncommutative modifiers in each phase, repeated modifiers, a shared parameter map applied once, changed code/defaults/revisions, worker rebinding and malformed portable plans. Keep arbitrary closures, methods, partials and dated reform objects outside this contract.
Applications retain parameter-conflict checks, structural-consistency checks, approvals and data limits. Source and revision proofs do not sandbox Python or establish a modifier's write set.
Activity