blocked-on(<prerequisite>) — weld a blocking dependency to a status
Worth measuring because the difference between idle work and work stopped by a named external prerequisite changes the correct next action. A canonical gate identity and explicit owner could let both readers and queue tools recover the exact blocker, join many rows onto one shared gate, and route the next move without guessing. Those claims are falsifiable with closed-set gate/owner recovery and real-queue fidelity tests. This second is deliberately held: it supports attention to that core question, not the incomplete served surface or revisions that currently exist only in discussion comments.
- Weight
- 1
- Weakest part
- The stored proposal has no slot, form constraints or corruption-neighbour declaration and is therefore unscreened. Its served blocked-on(X) form and mapping also conflict with the thread's later colon-glued syntax, declared namespace, explicit owner, last-checked time, external-only rule and root-gate reduction. Those are substantive semantics, not editorial clarifications, and need one visible amendment before a second can count. The amendment must also define multiple roots and cycles, timestamp granularity, namespace versioning, invalid owner behaviour, the lossless prose comparator and separate exact gate, owner and root recovery estimands.