The page nobody else publishes
Every one of these was considered and refused, and the reason was written down at the moment it was refused.
a declined feature with a reason is more persuasive than ten shipped ones
None of this was written for the page
None of these reasons was written for this page. Each was recorded at the moment the thing was refused, which is why they are specific enough to argue with.
Two things are not on this page because the tree records no decision for them, and one of them is the obvious one to expect. They are the operator to write in his own words, not this site to write for him.
Fourteen, with the reason each time
In order of weight. The reasons are quoted, because a reason rewritten is a reason weakened.
01Cloud AI, at alldeclined
Public AI endpoints are disabled… so archived member text cannot be sent to a public service by a configuration typo
02A consent row for the bot itselfdeclined
A row in it that nobody chose would make every reading of that table false… The saving was one CASE expression; the cost was the meaning of the one table this product rests on.
03A thinking or reasoning dialdeclined
Enabling thinking would silently replace three conversational answers in five with a canned one.
04The repetition penalty that should workdeclined
unmoved at every value, and the case that was FINE gets worse as the penalty rises. That is not a dose to tune.
05Letting her state her own law numbersdeclined
a page is printed by the application under her words
06Numbering the withheld lawsdeclined
can read each one's SUBJECT off its neighbours, which is disclosure.never-narrow defeated by arithmetic
07Per-bot exceptions to the constitutional lawsdeclined
Five bots with five different outermost limits means nobody can say what any of them will refuse
08Deleting a lawdeclined
A HARD delete… would erase the record of it ever having existed, which is the one thing the Book is for
09PDF ingestion for the knowledge basedeclined
A silent quality cliff: a badly extracted PDF produces chunks that look like text and retrieve like noise
10A looks-like-it-wants-current-information search heuristicdeclined
The cost of a false positive here is an outbound request, a bill, and untrusted text entering the prompt… widening it is a decision for somebody who is watching the bill
11Fetching web pages to make citations strongerdeclined
A provider offering page bodies would be offering a much larger injection surface
12LLM-extracted knowledge storagedeclined
did not beat naive retrieval on accuracy at all
13One budget for music and advertising spotsdeclined
a requested track and an unbidden advert are different things to a member, and one budget lets a busy music day silently buy advertising quiet
14German billion amountsdeclined
It means 10¹² while English 'billion' means 10⁹, and guessing would be a factor-of-1000 error about money
Smaller refusals, each one cited
Shorter, and no less recorded. Several of them are the reason a whole class of thing is handled the way it is.
- Raising the nginx timeout instead of moving work to a job
- a route that needs a raised proxy timeout is a route doing work that belongs in a job
- A fallback copy of the laws in code
- a second source drifts, which is the failure the whole move exists to end
- Passing unscored results through when the embedder is down
- an outage is exactly when nobody is watching
- The lexical-overlap check
- passes the exact failure it was built for
- A blocklist on the marketing host
- it fails open over time… An allowlist fails closed
- Wake phrases, substring name matching, and acting on one high-confidence message
- a false positive publishes someone who never asked, which is the one failure this product cannot have
- A migration silently resolving a name conflict
- it decides which of two disagreeing sources wins at a moment nobody is watching. So the boot refuses, naming both values
- Splitting the decision log by season, or a topic map over it
- a stale map is worse than none because it looks authoritative
- A repository-wide em-dash sweep
- would rewrite roughly half a megabyte of documentation to satisfy a typographic preference no member will ever encounter
- A widened answer window after music lists
- bounded by the card's own expiry rather than by a new setting
- The scriptable encrypted-backup mode that gives up its post-quantum property
- the worst of both outcomes, so it was rejected
- Blanking display names in the retention sweep
- who said something is the skeleton; what they said is the content