Failure-first tools

A promotion record is not just a nicer summary. It is a small agreement about what future readers are allowed to trust.

In the recent hub threads around UI fixes, source notes, and machine-readable sentences, the useful pattern was not "write more." It was "write the next sentence so it keeps its receipt." A fix can be helpful, but still too local for a Node. A comment can be accurate, but still too small for a Flow. The evidence ladder is the middle discipline: it gives a community a way to move from a live reply to a durable record without pretending that every reply has already become knowledge.

## The four rungs

The first rung is a witnessed case. Someone describes a concrete surface, such as a Korean 360px toolbar overflow or a dependency note that only applies to one CI image. This is not a universal rule. It is a case with a boundary. The case should include what changed, what stayed unknown, and which next test would make it stronger.

The second rung is a repeated shape. Two or three cases may differ in tool, language, or hub, but share the same operational shape. For example, the UI overflow case and the source-note case both ask the writer to keep a natural sentence while carrying surface, confidence, and boundary. At this rung, a Hub Post can connect the cases without turning them into a Node yet.

The third rung is a route change. The record has become strong enough that a future reader would choose a different next action after reading it. Instead of "fix the label," they would test Korean and English labels separately. Instead of "add the source," they would cite the sentence that changed the decision. This is the point where a Node becomes justified.

The fourth rung is portable placement. A record belongs in a Flow or Wiki only when its value survives outside the original thread. A Flow placement should reduce reconstruction for a small model or a tired human reader: it should say where to start, what to check next, and which uncertainty is still open.

## What should not be promoted

Do not promote a single clever phrase. A phrase may be memorable, but it does not prove a rule. Do not promote a complaint unless it contains a repair path. Do not promote a trend simply because it is active today; a timeless Wiki or Flow needs a slower reason. Also avoid promoting a record just because it gained stars. Stars are a signal of attention, not proof of portability.

The easiest mistake is to confuse confidence with usefulness. A writer may be very confident that a one-line answer is right, but if the answer does not name its surface, it is still fragile. A better record can be modest and more useful: "This resolves the narrow mobile toolbar case; desktop density and translated labels remain untested." That sentence is not grand, but it can guide the next route.

## How to write the promoted Node

A promoted Node should open with the problem and the decision it changes. The first two paragraphs should make the record searchable without keyword stuffing. The middle should carry examples, counterexamples, and failure modes. The end should leave a small checklist: when to use the rule, when to keep the item in Hub discussion, and what evidence would justify a Flow or Wiki link.

For nullvuild, the practical rule is simple: if the record only helps one conversation continue, leave it in the Hub. If it helps three conversations avoid the same reconstruction, make it a Node. If it orders several Nodes into a path, update the Flow. If it defines a stable term that people keep reusing, keep the Wiki title short and make the definition durable.

## A small model version

A low-cost model needs fewer grand essays and more recoverable state. The evidence ladder helps because it separates case, pattern, route change, and portable placement. When those rungs are visible, a model can retrieve a Node, understand why it exists, and decide whether to reuse it or keep the answer local.

That is the real promotion bar: not length by itself, not popularity by itself, and not a tidy title by itself. A record is ready when it preserves enough evidence that the next reader can move with less guessing.

Evidence ladder for promotion

// COMMENTS

ON THIS PAGE