READ — asking the web surface a question

Raised by the read endpoints lemonfiber ui serves, about which read a request named and the query string it arrived with. A read that cannot be answered as it was asked is refused, because answering a different question in its place would read like the answer to this one. READ-3 answers 404, and every other one 400. See the envelope.

Code	Severity	Exit	What it means	What to do
READ-1	error	1	The read you asked for takes no parameter by that name. It is refused rather than ignored, because ignoring it would answer a wider question than the one that was asked, and a wider answer reads like the answer.	Ask again, naming only what this read takes. The message lists them.
READ-2	error	1	A parameter that names one thing was given more than once. Which of them was meant is not something this can work out, and answering for one of them would drop the others without saying so.	Ask again, naming it once.
READ-3	error	1	There is no read by that name. Every read this surface answers is named in the contract, and this name is not one of them.	Ask for one of the reads the contract names. The envelope sets them out.
READ-4	error	1	A trace was asked for and named nothing to follow.	Ask again, naming what to follow.
READ-5	error	1	The season to narrow a trace to is not a number.	Ask again with the season as a number.
READ-6	error	1	A setting was asked for by an empty name. Naming no setting asks for every one; an empty name would match none of them, and come back as no such setting about a setting nobody named.	Name the setting, or leave it off to read every one.
READ-7	error	1	A household member was asked for by an empty name. Naming nobody asks about the whole household; an empty name would match nobody, and read as nobody having asked for anything.	Name the member, or leave it off to read the whole household.
READ-8	error	1	A shelf was asked for and nobody was named whose it is. There is no everybody to fall back to: a shelf is what one account may watch, and no two accounts need hold the same one.	Ask again, naming whose shelf to read.
READ-9	error	1	How many holdings to answer with is not a whole number above nought. A shelf of no holdings is a request for an answer that says nothing.	Ask again with a whole number, or leave it off.
READ-10	error	1	More holdings were asked for than one read answers with. It is refused rather than cut down, because a shorter answer wearing the shape of the whole one reads as the whole shelf.	Ask again for fewer.
READ-11	error	1	A diagnosis was narrowed to a group of checks, or a check, that is not one. Reading the word as the nearest one would answer something that was not asked.	Name a group of checks, or one check by the name a finding gives it.
READ-12	error	1	A removal was named that is none of the four there are: stop, services, configuration or media. Reading the word as the nearest one would answer something that was not asked.	Name one of the four, or none to read the one that removes nothing.
READ-13	error	1	Moving forward was asked about and neither stack nor self was named. Neither is the smaller case of the other — one moves your services, the other this program — so answering with either would answer the wrong question.	Ask again, naming stack or self.
READ-14	error	1	How many log lines to begin with is not a number, or is more than one read begins with. The message names the ceiling.	Ask again with a number no larger than the message names.
READ-15	error	1	Whether to keep reading is neither true nor false.	Ask again with true or false, or leave it off.
READ-16	error	1	A household read named a member and asked for the household's defaults as well. Those are two different answers, and one reply cannot be both.	Ask again for one of them: a member, or the household's defaults.

What each severity and each exit means is on every error by code, beside every other family.