Expand description
Deterministic, budget-aware attack planning.
§Runtime scope
- Build: always/default.
- Execution: Surface B (deterministic decision runtime).
- Default
termivar scan: yes, throughStandardWebDecisionRuntime. - Support: implemented and tested.
See docs/internals/runtime-map.md.
The planner ranks declarative actions but never executes them. It consumes one immutable knowledge snapshot, evaluates action requirements, derives confidence from Bayesian hypotheses, and emits an explainable plan.
Structs§
- Action
Cost - Positive estimated execution cost in planner-defined units.
- Attack
Action - Declarative executable candidate considered by the planner.
- Attack
Plan - Immutable output of one deterministic planning cycle.
- Attack
Planner - Deterministic utility planner for declarative attack actions.
- Benefit
Score - Normalized gain or business-value score in basis points.
- Excluded
Action - Explainable record for a candidate omitted from the plan.
- Hypothesis
Selector - Selects the Bayesian hypothesis that supplies action confidence.
- Plan
Step - One dependency-safe step selected for execution.
- Planning
Context - Inputs shared by every candidate in one planning cycle.
- Risk
Score - Normalized operational risk in non-zero basis points.
- Utility
Breakdown - Explainable inputs and result of one utility calculation.
- Utility
Score - Fixed-point utility used only for deterministic ordering.
Enums§
- Exclusion
Reason - Reason a registered action was not selected.
- Planner
Error - Validation and consistency failures raised by the attack planner.
- Planner
Write - Result of registering an action identity.
- Required
Strength - Required qualitative strength for an action’s confidence source.
- Resolved
Verification Target - Plan-time resolution of the claim an action outcome may transition.
- Verification
Target - What a conclusive outcome may transition, kept distinct from the confidence hypothesis that motivated planning the action.