Execution risk
execution-riskThe abstract category for markers about running code the blueprint did not fix in advance.
Where it sits
root of its branch- execution-risk
What it costs
declared on the cardexecution-risk is a category, not a marker a card declares. A rule written about the markers underneath it catches them all. It carries no weight and never moves the security level. The terms narrower than it carry the weight themselves.
Nothing in the topology can establish execution-risk on its own, it is a fact about what the node does that only its author can state. The analyzer takes the card at its word and names the node in the explanation.
The engine's configuration prices the curated markers. It is silent about this one. The number is the local term's own declared weight, read from the vocabulary the bundle ships. Nothing records which weight an evaluation was made under, so move it and two evaluations stop being comparable.
Who uses it
0 cards · 0 blueprintsNo card names execution-risk directly. It sits above the terms that do. The 2 terms narrower than it are named by 3 cards between them. A rule written about execution-risk catches every one of them.