September 26, 2026

Every signal says whether firing is good news

Admin

Milestones and monitors have been one engine for a while — one form, one page, told apart only by whether the thing can un-happen. What the two doors were also doing, silently, was asserting valence: everything under Milestones was treated as good news and everything under Monitors as a problem.

That was wrong in both directions, and both diagonals are now authorable:

• A good monitor. "Trial is actively converting", "power-user streak holding" — a condition that opens and resolves, and that you want your list full of. Previously it had to be written through a door whose own field label read "What counts as a problem".
• A problem milestone. "Hit the hard seat cap" latches once and never un-latches, so it has always been a milestone — but its rate was being folded into the stage's progress number and drawn as an achievement.

The editor now asks Is firing good news? as its second question, under the name. The door you came through sets the default — a milestone starts as progress, a monitor as a problem — and you can change it on either.

A problem signal no longer flatters a stage's progress rate

Admin

Three things read the new setting, and the first is a fix rather than a coat of paint:

• The stage's own progress rate — the roll-up that counts a profile once however many milestones it qualifies for, along with its net moves — counts progress milestones only. A problem milestone keeps its own row and its own rate; it just no longer votes on whether the stage is going well. If you had authored one, this number changes.
• A profile's open problems card now asks two questions instead of one: is there an open episode, and is it a bad one. A good condition that is currently open is deliberately not listed there.
• The rows read in the right direction. A problem milestone shows affected of eligible rather than reached of eligible and draws its rate in red; a good monitor draws its open count in green. Only the surprising case is badged, so the lists stay scannable.

Existing signals are unchanged: every monitor was set to a problem and every milestone to progress, which is exactly what the two lists were already claiming on their behalf.

One New signal button

Admin

A stage page now has a New signal button in its header. It asks which of the two kinds you mean — described by what the numbers are, a rate over a denominator or a count of what is open — and then opens the same editor either list's footer opens.

The two lists are still separate, and deliberately so: a milestone's number is a rate and a monitor's is a stock, and one table cannot carry both without a column that means different things line to line. What was missing was a way in that named the choice, rather than leaving it to be discovered by scrolling to whichever list you happened to want.

Also

Admin

The Monitors section's copy no longer tells you that you want your monitors empty — that is true of a problem and false of a good one, and it is now a property of the signal rather than of the list it sits in.