Priority Signal

Priority Signal is not how good your judgment is. It is how strongly one demand rises above the rest before judgment ever gets a vote.

When several things compete, this dial decides whether the field sorts itself into a clear ranking or stays flat. It aims the rest of the executive system: whatever wins salience is what starting fires at, which is why a flat field so often feels like not knowing where to start.

The range

Lower: Competing demands feel equally urgent or equally flat, so choosing is effortful and can tip into scattered effort, endless reprioritizing, or paralysis. The upside of a flat field: no single demand can lock the others out of view, and external ranking tools work unusually well because they supply exactly the piece that is missing.
Higher: One demand foregrounds strongly and the rest fade, which supports decisive action and powerful focus; paired with strong staying power it becomes hyperfocus. The cost is distortion: what feels most urgent may not be what matters most, and significant responsibilities can drop out of the active field entirely.

It depends

Depletion: Fatigue, burnout, and heavy load drain the deliberate, top-down half of this system first. When it fails, you attend to whatever is most stimulating rather than most important. In deep burnout the ranking can flatten entirely, an early warning that arrives before performance visibly drops.
Deadlines: An approaching deadline generates acute urgency chemistry that temporarily supplies the salience importance could not. That is why the night-before surge works, and why it is volatile, stressful, and compounding.
Threat: Anxiety hands the ranking to threat. Threat-tagged demands take top priority regardless of actual consequence.
Context pile-up: When several roles are active at once, their priorities contradict and the ranking fails. The fix is fewer active contexts, not a better task list.

Baseline is how cleanly your field separates under ordinary conditions; today is that architecture plus whatever state it is running in.

What it is not

Not starting: Priority Signal decides what rises to the top; the initiation threshold decides whether you can launch once it has risen. You can know exactly what matters and still not start, or start easily on whatever happens to feel salient.
Not threat radar: Threat-safety salience is a specific protective orientation toward possible danger. Priority Signal is the general ranking function across every kind of demand. Threat can hijack the ranking, but they are different dials.

I can prioritize clearly. My priorities just don't match what others expect.
the reaction we design for