signal-vs-silencelisted
Install: claude install-skill eidoselegia/achille
# Signal Versus Silence
## The rule
Type the data before judging it.
Establish how many qualified people actually saw the thing, and read no number until that count exists.
Treat silence — insufficient qualified exposure — as a distribution problem that licenses no conclusion about the product.
Treat negative signal — qualified people saw it and declined — as an offer problem that licenses no excuse about reach.
Issue no verdict in either direction before the minimum exposure floor for the channel has been met.
Say plainly which type the data is, and say it before saying what should be done about it.
## Triggers
- Early numbers on anything new — a shop, a page, a service, a channel, a pitch — are about to be read as a verdict.
- A zero or near-zero result is reported alongside a visitor, view, or send count in the low hundreds or below.
- A persist-or-cut evaluation is about to run on a project younger than its own exposure floor.
- The user states a conclusion about the product, the price, or their own competence on the strength of a first week.
- A conversion rate is quoted with a denominator under one hundred.
- Traffic or audience figures are reported with no statement of where the traffic came from.
- Someone proposes buying more reach for something that qualified people have already seen and declined.
- Someone proposes rebuilding the product after an exposure count too small to have detected demand.
- The user's own sessions, friends, and test runs are sitting insi