Unbounded loop
unbounded-loopThe node sits in a cycle with no iteration cap and no exit condition.
Where it sits
stands alone- unbounded-loop
No term is narrower than unbounded-loop.
What it costs
declared or inferredA blueprint starts at a clean 4, loses the weight of every marker present, and the result is clamped into 1–4. unbounded-loop is charged once for the whole blueprint no matter how many nodes carry it. The explanation still lists every node that established it.
unbounded-loop is one of the three markers the analyzer derives from the graph itself. It can fire on a blueprint whose cards never mention it. A card that declares it and a graph that implies it are the same marker, charged once. The finding records which way round it was established.
The number lives in the engine's configuration and not in this vocabulary. A recalibration touches one file, so every blueprint is charged the same way. Nothing records which calibration an evaluation was made under, so move a weight and two evaluations stop being comparable.
Who uses it
0 cards · 0 blueprintsNo card in the registry names unbounded-loop yet. None names anything narrower. A term with no takers is not a broken term.