HouseChalk · What a Room Collects

A · What the kitchen is carrying

Inside the space, under its colors. Four kinds of saved thing, one card shape. The kind is carried by the chip, never by the card.

The Hollis House

Kitchen

On the wall

Sea Salt

Walls

Pewter Green

Cabinets

Not chosen

Counter

Collected

A kitchen with green cabinets and brass handles

The green cabinets with the brass Saved by Nora · 2 April

Picture

Hale Navy, photographed at the shop Saved by you · 11 April

Color HC-154

Deep single-bowl sinks, the undermount ones Saved by you · 19 April

Link

“The bin has to be next to the sink, not across the room. That's the one I will notice every day.” Saved by you · 3 May

Note

Nothing here has to become a decision. Four of these will, and the sink note already has. It's why the bin question is open.

B · Putting something in

Three doors, none preselected, because the room already knows which room it is. A pasted link resolves to a card before it is saved.

Kitchen

Keep something

It goes to the kitchen because that's where you are. You can move it later, and you won't have to name it.

Take a photo

Paste a link

Type a note

Pasted just now

Deep single-bowl sinks, the undermount ones The page it came from, kept with it

Give it a room Kitchen

Say why, if you want Optional. Nothing needs it.

Keep it

Not this one

A file isn't one of the three doors yet

A photo and a link can belong to the kitchen today. A PDF can't: project_documents has no zone_id, and the type list is seven plan-drawing kinds. That's the column mockup 27 needs for a permit.

C · Photographing one

The first door, and the only one where what comes back has no words on it at all. A link brings a title and a source; a note is already a sentence. A photograph arrives blank, and the screen has to be honest about how little it knows.

Kitchen

Just taken

It goes to the kitchen because that's where you are. Everything under it is optional and it keeps perfectly well without any of it.

Give it a room Kitchen

Call it something Optional. It keeps as a photograph otherwise.

Keep it

Take another

How it sits on the board

A photograph You · just now · Kitchen

Named a photograph because that is all anybody knows about it, and the picture is the handle. A link would have brought its own title and a note is its own first line; this one has neither and is not pretending to.

Nothing reads the picture

A photographed paint chip does not become a color, and a photographed tag does not become a price. Mockup 17 does that, deliberately, on the option intake. But that is a decision being priced, and this is a room being reminded. Doing it here would turn saving a thing into starting a job.

D · Typing one

The third door, and the one that needs the least. There is no link to resolve and no picture to wait for — a sentence is already the whole thing, so the screen's only job is to not ask for more.

Kitchen

Type a note

It goes to the kitchen because that's where you are. Nothing else is needed, and nothing will chase you about it.

The bin has to be next to the sink, not under the island. Six years of carrying peelings across the room is most of the reason we are doing this at all.

Give it a room Kitchen

Call it something Optional. The first line does it otherwise.

Keep it

Not this one

How it sits on the board

“The bin has to be next to the sink…” You · just now · Kitchen

The same card a photograph and a link get, with the lines glyph where their picture goes. A note is not a lesser kind of thing to have saved.

A note is not a task. It never appears in Now, nothing counts it, and it will still be sitting here in a year if nobody does anything with it. That is the whole point of somewhere to put a thought down.

E · The one that has no room yet

Saved from outside the app, before there was a room to put it in. Not an inbox, not a second feature — the same row with nothing in zone_id.

The Hollis House

Collected

Three of these haven't been given a room. They stay here until they are, and nothing chases you about it.

No room yet

Alabaster, from the trim aisle Saved by Nora · 6 May

No room SW 7008

“Ask Dave whether the hall can take a wider door before the framing goes up.” Saved by you · 9 May

No room

Where this one belongs

Alabaster, from the trim aisle

Kitchen Primary bath Mudroom Great room Laundry The whole house

Alabaster is a trim color, and trim runs everywhere. The whole house is a real answer here, not a way out of choosing.

F · Everything, across the house

A lens over the same rows, not a seventh tab. Mockup 21 settled this shape: the house has six tabs and any number of ways to look through them.

The Hollis House

Everything collected

31 kept 7 rooms Since March 2026

By room

KitchenFour kept · two became decisions 4

Primary bathNine kept, mostly tile 9

Great roomSix kept · one is the fireplace 6

No room yetTwo colors and a question for Dave 3

All of it, newest first

Alabaster, from the trim aisle Nora · 6 May

No room

“The bin has to be next to the sink…” You · 3 May · Kitchen

Became a decision

Hale Navy, photographed at the shop You · 11 April · Kitchen

HC-154

G · Room actions

The visible three-dot button at the upper right opens the only room-management sheet. Search does not belong on this screen; these two actions do.

The Hollis House

Kitchen

On the wall

Sea Salt

Walls

Pewter Green

Cabinets

Not chosen

Counter

Collected

The green cabinets with the brassSaved by Nora · 2 April

The bin has to be next to the sinkSaved by you · 3 May

Room actions

Rename room

Remove room

H · Naming the room

Renaming changes the room's label, not the things in it. It is a short edit rather than a general settings screen.

The Hollis House

Name this room

This changes how the room appears everywhere. Nothing filed here moves.

Room name

Kitchen

Save name

I · Removing the room

A room is re-addable, so there is no typing ritual. The screen states the fixed result before the one destructive action; it never asks the person to choose a disposition.

The Hollis House

Remove Kitchen

The room goes away. Its record is sorted, not left behind to block the change.

What stays

Four saved things move to Not in a room yetPictures, links, notes and colors stay in the binder.

Files, sheets, product records, care tasks and conversation notes move tooThey are things filed here, not things the room itself said.

What ends with this room

Answers, color placements and questions set aside hereThey are statements about Kitchen, so they are no longer true once Kitchen is gone.

Punch items and room-only spec linksTheir subject is this room, not the house.

A concern only if this was its last roomA concern shared with another room stays there.

What is re-sorted

A decision with no other room moves to Not in a room yetPeople and shared concerns lose only their Kitchen tag.

Remove Kitchen

What this page decides, and what it asks for

Collected things live in the room, and the house view is a lens. The alternative was a seventh binder tab, and three things ruled it out. zone_memories is already keyed to a zone and already carries an image, a url and a body on the same row, so a picture, a link and a note are three values of memory_type rather than three features. _ds/FICTION.md pins six non-room tabs “in drawn order, and the order is pinned”, and records that an earlier revision saying five was the mistake — a seventh reopens a settled decision. And mockup 21 already chose the shape for this: lenses over one set of records, never new places for records to live.
One card, four kinds. There is a single .keep rule and the kind is carried by the chip and the thumbnail. If a link and a note looked like different objects, the page would be arguing the opposite of what it says.
Nothing here is an inbox. Frame E is the same row with nothing in zone_id, shown with the dashed treatment mockup 16 already uses for a surface nobody has assigned. It is not a queue, there is no badge, and nothing chases you to empty it.
Saving is not deciding. Thirty-one things are kept and two have become decisions. The callout in A says so outright, because the failure mode of a collection feature is that it starts to feel like homework.
What is already built. Both capture paths exist: the zone workspace memory sheet with camera (add_memory_sheet.dart) and SelfManagedCaptureCard on the Build tab, which offers note, voice and photo. zone_library.image_url gives every zone a default illustration. What does not exist is the record — no gallery, no chronological view, no retrieval. Frames A, E and F are that record, and they need no new table.
The one column this asks for. A pasted link and a photograph can belong to the kitchen today; an uploaded file cannot. project_documents has no zone_id and knownDocumentTypes is a closed set of seven plan-drawing types, so a permit upload is refused at the handler. Frame B draws only the three doors that work and names the gap in its own callout rather than drawing a door that would write a phantom row.
A color is not the fourth door, and this is where somebody will try to put one. Frame A draws a color keep — a swatch, a Color chip and HC-154 beside it — so the obvious reading of frame B is that a fourth tile is missing. It is not: the missing door here is a file, per the note above, and a color has a chooser of its own on 42-colors-and-the-space.html, one screen further in. The two are drawn differently on purpose. Frame B's doors are .doors .d tiles, three across at 390pt with no room for a fourth; mockup 42's are full-width cards stacked at the card gap, which is the shape that takes four. A color still arrives here, on the board, as one of the four kinds.
Two page-scoped shapes and one chip. .keep, .doors, .shot and .unfiled. Everything else is _ds/hc.css under body class="hc-air" — the swatch strip, the stacked row, the surface chips, the resolution line, the card tints and the nav dock. Names were checked against the sheet: .row, .opt, .fact, .surf and .chip are taken and none of them appears here.
Whose phone this is. Sam is holding it, so Sam is you and Nora is named. Per _ds/FICTION.md, your partner is never a way to name a person on a screen.
Room management has one visible home. Frame A's trailing control is the three-dot Room actions button, replacing the ungrounded search icon. Frame G opens its two-item bottom sheet: rename changes only the label; remove goes to frame I. The sheet labels both actions so the icon does not have to explain itself.
Removing a room has one fixed result. Frame I follows the sorting rule in DB_DIAGRAM.md §1.1: things filed in the room move to Not in a room yet; statements whose subject is the room go; decision, person and concern membership is re-sorted. There is no keep-or-delete choice and no typing step. The confirmation names the newer records that the original three-table sequence omitted, so the implementation cannot silently leave a foreign key behind.