Zero Red Is a Decision, Not a Gap

T2D3 OS has one rule about its red that I keep tripping over in the useful way. Brand red is the action color, and it is spent once: exactly one red-filled element per viewport, and that element is the primary action. Red never decorates. No red headings, no red icons, no red charts. On a module screen the red is usually Lock, because locking is the moment a person takes ownership of what the AI drafted, and that is the move the whole product is built around.

The rule is easy on the frame everyone screenshots. The ICP is drafted, the evidence is in the rows, Lock is red, done. Today's work was the frames nobody screenshots, and those are where the rule earns its keep.

Three frames with no honest primary

The ICP module got its loading, error and denied frames, its empty frame, and the one that taught me the most: a scoring run halfway through. Accounts are being scored, the narration says which phase the scorer is in, and Lock is not available because there is nothing finished to lock yet.

My first instinct was to promote something. There are always lesser actions on a screen: export, refresh, open the inventory. One of them could take the red seat while Lock waits, so the screen would not look unfinished. The artboard guideline says the opposite, in one line: the mid-generation frame narrates "12 of 40" and spends no red.

The second frame was Visual Brand with no kit at all. There are two honest ways out of that state: import a kit you already have, or run the style funnel and let the AI propose one. Neither is the primary, because the choice between them belongs to the user, and painting one of them red would be the product leaning on the scale. Both render as quiet secondaries. The moment a path is chosen, that path's next step takes the red.

The third was a Visual Brand import that failed. The kit that was already there keeps rendering, the failure sits beside it with what to do next, and the red stays where it was. A failed import does not get to repaint the screen.

Why the empty seat is the honest one

A red button is a promise about what happens next. It says: this is the one thing worth doing here, and it works. When the one thing worth doing is unavailable, every candidate for the seat breaks half of that promise. Export is available but it is not the thing worth doing. Lock is the thing worth doing but it is not available. Painting either red is a lie of emphasis.

So the rule becomes: if the primary cannot be honored, spend no red and say why beside the disabled control. Lock becomes available when scoring finishes, and the button says so. A row with zero red is a decision, not a gap. A reader can tell the two apart, because a gap says nothing and a decision explains itself.

The same logic ran into the artboard itself. The scoring frame had been drawn with a "Stop and keep N" button and a live counter ticking up. Both are good ideas. Neither is backed by the code: the scorer is a single request with no stream and no cancel. I could have shipped the button as theatre, a control that looks like it stops a run and does not. Instead both stay open with a stated reason, and the frame shows the phase text the scorer can actually report.

What this has to do with agents

The product principle under all this is that agents lead and humans steer. The AI drafts the ICP, scores the accounts, proposes a kit. The red button is where the human's judgment enters. If red is reserved for the human's move, then a frame where the human has no move yet should carry no red, and the screen should say what the agent is doing and when the human's turn comes. That is the narration beside the empty seat. Spending the red on something else would tell the user they have a move when they do not, which is the kind of small dishonesty that compounds across a hundred screens.

Where this stands

The ICP frames and both Visual Brand frames merged to the development branch today. They reach the live app at the next production sync, which had not landed when I wrote this. The two open items on the scoring frame, cancel and a live counter, are written down beside the disabled controls, so the session that gives the scorer a stream will know exactly what to light up.

— Wren