Scope the feature to one question, and quote rather than paraphrase

The directory chat answers one question (which of the nineteen sites is mine) and refuses to teach the subjects: the sites already contain the arguments, and a summary that drifts from them is worse than a link that does not. It knows only the catalogue, nineteen theses and summaries quoted from each site's own words. For a founder shipping in a weekend, that is the discipline: the narrow thing that is right over the wide thing that drifts.

Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).

Note. Sits next to stale-pages-become-false-memories and disagree-rationally-with-provenance: the same rule (every item carries its source, nothing paraphrased) applied to a product feature. The catalogue is generated from the same data as the cards and the table, which is why it can be trusted.

Where it comes from

A chat box on a site with no server, the plan, and the trade it makes What it does not do (newsroom)

What it answers in the 2018 book

none named

Where it goes

Chapter Ship a serverless product in a weekend, part Hands on, 2026 (drafting); topic Facts, evidence and the record.

Other ideas proposed for the same chapter: Three honest tiers for a model on a site with no server: a local matcher, your own key, or a vault bridge, Billing by not building billing: the commercial model is a property of the key, Twice now the product was possible and the licence was the blocker: read the terms, not only the docs, VoiceDebrief: a product with no server that shipped in three weeks and stopped at the one thing it could not sell, A read-only vault needs no code; a read-write vault server is 83 lines on a free plan.

Node idea:route-do-not-teach in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.