Repository navigation
Deployment inputs: one bundle for cost model, accuracy model and capabilities — after #511 #525
Description
Goal
#509 (Goal; "3. Plan selection") says the deployment supplies an empirical cost model, an empirical accuracy model and its execution capabilities, and selection rejects candidates needing a missing capability. The input structure is a TODO in #509.
Blocked on
Implementation of #511 (unified operator graph). Do not start before #511 is implemented.
Current state (main @107ab28d)
| Input | Defined | Supplied | Default |
|---|---|---|---|
PlanningModels{cost,accuracy,evidence} |
asap-aware-mapping/src/pass/mod.rs:46-90 |
OptimizationInput.models / planner UserInput.models |
builtin() |
SummaryMaintenanceLifecycleCapabilities (lifecycle flags) |
summary_maintenance_lifecycle.rs:60 |
plain value in LifecycleInput.capabilities, next to the clock and horizon |
ALL |
SummaryMaintenanceCapabilities (update/merge/delete) |
summary_maintenance_lifecycle.rs:81 |
CostModel::summary_maintenance_capabilities |
all false |
ValueOperationCapabilities |
cost_model.rs:96 |
three CostModel hooks (value_operation_capabilities → supports_value_operation → value_operation_support_evidence) |
ALL |
summary_support_evidence |
cost_model.rs:882 |
CostModel hook |
None |
Notes:
SummaryMaintenanceCapabilitiesis planner knowledge. Its docs say it describes what the summary algorithm can do, not what the deployment can do.- ASAPQuery-backend still pins Planner rev
f46cbf6c. It overridesvalue_operation_capabilitieswith the old field names andsummary_maintenance_capabilities, and buildsSummaryMaintenanceLifecycleCapabilitiesdirectly. Changes here only reach it when it bumps the pin.
Proposed (one concern per PR)
- Move
capabilities: SummaryMaintenanceLifecycleCapabilitiesfromLifecycleInputintoPlanningModels, withwith_capabilities();builtin()usesALL.PlanningModelsthen becomes the single deployment-input bundle, andLifecycleInputkeeps only the clock and horizon. No new struct. About 40 lines. Test:MajorPasswith continuous-only capabilities rejects the other lifecycles withUnsupportedByRuntime. - Later: derive
SummaryMaintenanceCapabilitiesfrom the physical kernels instead of aCostModelhook. - Later: collapse the three value-operation capability hooks into one.
Open questions
- Rename
PlanningModels(e.g.DeploymentInputs)? Recommended: no for now. - How docs: define unified operators and SQL/PromQL scalar boundaries #511's operator capabilities map onto these inputs.
Activity
zzylol commentedon Oct 15, 2026
Status: covered by the upcoming deployment-inputs work (deployment inputs, capabilities and calibration). Not closing yet.
On main,
PlanningModels { cost, accuracy, evidence }(crates/asap-aware-mapping/src/pass/mod.rs) is the deployment-input bundle. Stage 3 readsaccuracyandevidence. Capabilities and a cost calibration are not inputs yet: Stage 3 prices with a fixedillustrative_calibration(), and its module doc says deployment capabilities are not checked yet. The lifecycle capability types this issue lists were removed with the lifecycle model (#667).