What was chosen, and where it got to

Every route ends inside a record that already has a door — a room, a decision, the last mile, project settings. That is the test NAV_AND_COMMIT_RULINGS.md Ruling 1 sets: a tab declares what the product is about, and saved things and where my refrigerator is are questions about a house, not two more things the product is about.

Saying where they go and then not drawing them is the honest shape: they are real parts of the design, they are not selections, and a page that sketched them badly would be read as having settled them.

The one row that reaches frame 12. It is the row page 17 is already opened from; nothing about it changes except what is behind it.

The row that reaches frame 15, and the only place in the product where a settled choice is opened. There is no selections list to browse, because a selection is a fact about a decision.

Options, the settled selection and its four members all hang off one decision, so all three are reached from it. The alternative — a place that lists every selection in the house — is the project-management surface Ruling 1 declined, and it would answer a question nobody standing in a kitchen asks.

One of them has not been ordered is what makes the row worth tapping. A row that said only The Hollis package would be a label, and the late refrigerator would stay invisible until somebody went looking.

Not a badge and not a count. One thing not ordered is a sentence, and it is the only new text on this screen.

The handoff row is already here and already says what it is for. Adding a second row for orders would split one record — what was chosen and where it got to — across two places, and the reader would have to know which half they wanted before tapping.

A count in a pill says a number and no meaning. One thing not ordered says what the number is about, which is the difference between a nudge and a notification.

The title and the picture came off the page on their own. Both are copied and kept; a year from now the link may be dead and this card will be exactly as it is.

The deck holds four room photographs and no product photography, so frames 5, 6 and 13 borrow the kitchen. The shape is the claim being made here — media, then title, then source — not this particular image.

The first draft of this page drew a pasted link as a row of text, which is how a board of things somebody liked becomes a list of filenames. The reference pattern is consistent across every app that keeps links: image first, title second, domain third, and the URL itself usually not shown at all.

Everything on this card is stored when it is saved. A preview fetched at read time makes the board depend on somebody else's server staying up, and the one thing a binder has to do is still be there.

This is the keep door. The option door is frame 13 and it has a price on it. 17: folding them into one flow would put a price field in front of somebody who is only saving a picture, which is exactly where people stop capturing.

44's own closing line, made structural: nothing here has to become a decision — and the sink note already has. It's why the bin question is open.

A gray placeholder rectangle where an image would go says this failed to load, which is untrue of a note — nothing is missing. But a white note on a near-white page gives the words no object to sit in. The kit's KeepFace answers both with an inversion: ink ground, paper text, so it flips with the appearance rather than being a color or a tint.

The sentence was set at --text-xl and carried quotation marks. --text-lg is the block-title step and is always bold, so a homeowner's sentence set at or above it reads as a heading — --text-md at regular weight is the rule. And quotation marks belong to CoachBubble, where a named person is being quoted; the product does not quote somebody's own sentence back at them.

The words are verbatim, the same rule replies.body and a substitution's reason already follow. The product does not summarize somebody's sentence back at them.

Opened this question is a third relationship, and it is the deck's own example. It is not became an option and it is not a room — which is why the decision list carries a reason line rather than a status.

Placed, with no surface named. That is the ordinary case rather than an edge one, and page 16 already rules it: a color can be in a room before anybody has said whether it is the wall.

HC-154 sits on a chip because this screen resolved the paint. The room board deliberately does not draw it: the code lives on paint_colors.code behind an optional join, and a color somebody typed by hand has nothing to join on. One chip is the honest answer there; two are honest here.

The swatch is the subject and takes the media slot the picture takes, at the same size. A hex string in a monospaced row would be the product describing a color to somebody who is looking at it.

A placement is its own relation with its own table, so it takes the pin glyph rather than the question mark. Filing it under decisions would claim somebody decided this, and nobody has.

The room it was saved in is ticked and can be un-ticked. It is where you were standing, not a claim that it belongs there forever.

44 frame B is one room on purpose — it goes to the kitchen because that's where you are. A second room is a later, deliberate act, so it is a sheet off the keep rather than a field on the capture form nobody wanted.

This sheet cannot put the keep on a decision and does not offer to. That is frame 13, and it has a price field, which is exactly why the two acts are not one sheet with a second section.

No file these, no count on another screen, and no badge. A keep with no room is a finished act; the room is an optional later fact.

One kept color is a single swatch at 4:5 — the taller ratio, because a color has no detail to read and a squat one reads as a bar. Two or more on one wall combine into a palette. FICTION.md pins exactly two non-settled colors, Hale Navy and Alabaster, and page 16's argument is the pair of them claiming the same kitchen wall, so on this house they are always a palette and never a lone tile. The single-swatch tile is therefore drawn at full size in frame 8 and nowhere on a wall — the same face at a different scale. Drawing it here would have meant inventing a third color, which is the one thing that file forbids.

An earlier pass drew this list as rows while the room board was tiles, which said the same thing twice in two grammars. Nothing about having no room makes a keep more like a ledger entry.

There is no file these call to action and no count nagging on another screen. A keep with no room is a finished act; the room is an optional later fact, which is why this list is browsable rather than a chore.

Unfiled still means no room at all, so the partial index the count reads is exactly the one that exists. Making rooms plural did not move this screen, and that is a deliberate constraint on the schema rather than a lucky outcome.

The two new rows lead, because on a job with a connected builder they are the two that will actually be used.

17's rule holds through both new rows: the screen was opened from the appliance package and the eyebrow says so, so nothing here asks which decision this is for.

Drawn only when a list is assigned to this decision. When none is, the screen is 17 plus Something you kept — not a disabled row, because 47 frame 2 already ruled against a button that sits dead for the life of a project.

The picture and the page come across. Nothing else does, because nothing else was ever asked for.

One tap from the board, and it still crosses that field. What it does not do is put the field on the board.

Promotion copies; it does not move. A keep that vanished off the board when somebody priced it would punish the person who did the right thing, and the board would get quieter the more the house decided.

Three rows, one kind of number. Every price came off Dave's list, so the provenance line says the same thing three times rather than distinguishing three things that are not different.

Opened from the row above it. The eleven weeks is visible before anybody chooses — a package total hides the one number that decides when the kitchen finishes.

The deck already distinguishes you typed this, check it against the tag and it came off a quote. A builder's list price is a fourth, and recording it as one of the other three would be the exact lie 17 says gets somebody hurt.

A homeowner choosing a package is choosing four appliances, and the one that governs the schedule is the refrigerator. Showing members only after settlement would make the package total the whole basis of the decision.

Revision 4 was copied onto this project when it was assigned. Dave editing his list does not reach back into this decision — frame 20 is what happens instead.

A choice is one act; what it turns into is four, and each of the four can be somebody's job. Nothing here is a specification — the finish, the fuel and the panel are answers, and they live where answers live.

Dave's list moves, links die and options get edited. A settled decision that reads any of those live can change what it says a year after nobody touched it. This is the same snapshot the schema already takes of a resolution's answers, applied to the thing chosen.

Ruled in Q256: the role comes from whether an accepted builder is connected, and the seat is not guessed. This job has more than one builder seat, so naming one would put a durable obligation in a person's name for no reason.

49 owns the questions the choice leaves unanswered. This card says what; that page says which finish, which fuel, which panel. Folding them would make the snapshot mutable, because answers keep arriving after a decision settles.

Four states, one list, and the amber is spent once. The package total said $14,800 and never said this.

45 frame A: the settled specification and every later record stay together. Ordered, delivered and installed are three more later records of exactly that kind.

Every order-tracking pattern worth copying does this: the summary is one line per thing, and the rail only appears when you open one. Four rails stacked would make the page about the journey rather than about which thing is late.

Each row reads the last event on that item. A status column would be a second answer that goes stale the moment somebody records a correction — the ruling lead_times already carries.

The last node carries the substitution rather than replacing what was chosen. Both facts survive, which is what the record is for.

.spine is page 41's, in shared CSS since the time axis was drawn: a filled node for what happened, a ring for where you are, and a rail that stretches to hold whatever sits beside it. Procurement needed exactly that and needed nothing new.

The chosen-against-installed pair is 45 frame A's, unchanged. Editing the selection to say BS would erase the fact that somebody chose AS and a decision was made without them.

A wrong date is corrected by a further node saying what it corrects. That is why the sheet has no edit affordance and why the rail can be trusted.

Three states and one answer, so these are options rather than tick rows — the deck's single-select shape, filled rather than ticked.

Each save is a node on frame 17's rail, not an edit. A wrong date is corrected by a further record that says what it corrects — the shape 45 frame A already gives a substitution, where only the effective record offers another change or correction.

Recording an arrival asserts the recorder's own work and is safe offline: two people recording the same delivery both wrote something true. Changing who owes a row changes what somebody else is on the hook for, and that is a server-guarded write — frame 19 says so on its own screen.

Chosen is not offered because settling already wrote it. A screen that let somebody re-choose here would be a second way to settle a decision, in a form with no options on it.

Naming somebody changes what another person owes, so it goes up now rather than waiting for signal.

An earlier draft drew this on 45's .spec, which is a RUN of label-and-value pairs and needs a run to make sense of its 34% label column. One pair in it gives a two-word label a third of the screen and wraps the answer to three lines. A single current fact is a sentence with a heading, and the heading is the screen's own title.

There is more than one accepted builder seat on this job, so a default that picked one would be picking a person out of a set with no reason to prefer any member — and the snapshot is immutable, so it would assert that obligation in their name permanently.

The builder · nobody named yet is a real and expected state. Drawing the first builder on the project instead would be the product inventing an answer.

Custom, semi-custom and spec change nothing on this sheet. Connection decides, per Q254.

48 already built a source becomes a durable review before it becomes a choice, with successor reviews that never rewrite the finished one, per-decision candidates and a guarded adoption. A builder's list is a second kind of source into the same pipeline, which is why this frame is a copy of one that exists rather than a new screen.

48 frames 3 and 4 are an extractor working on a PDF and failing. A published revision needs no reading, so a list review opens at ready and those two states cannot occur.

Project settings already carries a reconcile row pointing at this route. A list review adds a second row in the same family, not a second place to look.

Where Dave builds revision 5. It is the first genuinely cross-job builder screen in the product — every builder route today is scoped to one house — and it belongs on its own page rather than as a nineteenth frame here. docs/STATE.md has carried it as deferred since before this feature was proposed.

Sam suggesting an appliance Dave did not offer, when Dave has opened that decision to it. The policy is one row on 50's existing group and exception cards, and the review is on the builder's decision screen. Neither is a selection, and both wait on that page.

Every app that keeps things browses them as a grid of pictures, and the binder's kept-rows lens already calls itself a lens over the same rows, not a seventh tab — so a board is a second renderer on a screen that exists. Frame 6 is what makes multi-attachment readable, and it is the part that has to come first. A grid with nothing to open is a screensaver.

The design kit ships Unstarted for exactly this — empty because nobody has started yet, one action, a hairline and no fill — and its own example is keep-shaped: “Nothing saved for the mudroom yet. Photos, quotes and tearsheets you save land here.” It is a real state of every wall on this page and it is owed, not designed away.

The package, its four members, their prices and Dave's two revisions were authored for this page and written into _ds/FICTION.md first, per that file's own rule. Every other name, date and figure on these frames was already pinned. That block should be read as a proposal.