The two of us

Day one has nothing and must not be filled. This has everything and must not be dumped. There is no catch-up feed, no here is what you missed, and no count of the decisions made without her — the binder is right there and she can read every one of them if she wants to.

She is not late. She was not asked yet, and the product was built for exactly that. Every sentence on this screen is doing that work — Sam has been at this a while rather than catch up on nine months.

A seat that holds no tags still sees the house, still sees Now, and simply has nothing sorted to it. The one band that survives is nobody has this — which is the band that depends on nothing at all.

Two people holding the same tag is the design. Both of you means this one genuinely wants two opinions, and it is why island electrical — Kitchen and Electrical — leads both seats' Now rather than being assigned to one of them by a tie-break.

The label she picked, the label on the chip and the label in the sentence are the same word in all three places. The alternative is real and was caught in review: she ticks Finishes, inside and gets a chip reading style.

He sees what she holds and cannot edit it. Ask is the whole affordance, and it is enough — a product that let one partner silently reassign the other's part of the house would have picked a side in an argument it has no business being in.

Take one over and hand one over are the same act read from two ends, and splitting them into two entry points would have made taking feel like the normal one and giving feel like an admission. They sit under two headings on one screen and the button says the same word for both.

The refusal under what this does not do is the hard part. An unanswered ask is the natural place to put a badge, a count or a reminder on the other person's screen — and this page's whole refusal is that no surface shows what the other seat has or has not got to. So the ask reaches her once, the way anything else does, and then it waits without accruing.

A tag swap between two people who live together is never really about the tag. You have done every finish in the house so far and I keep guessing is the whole message; the chips are how the app records what was agreed afterward.

The old route hid this page until another owner had already joined, which hid the action that creates them. One owner is a real household state. The same route expands into the responsibility comparison on frame 2 when Nora accepts.

An invitation is durable enough to show and not real enough to receive responsibility. There is no placeholder Nora in the active list, no pre-ticked Kitchen, and no suggestion that she joined before she did.

The architecture is uncapped, because a good reason to add another owner must not require rebuilding this screen. Two for now is launch positioning, not a hidden client or server constraint; the Add action remains part of the household.

Every invite screen in every product has a role picker beside the address. This one cannot have one: the page has spent three frames arguing there is no permission model between two people who live in the same house, and a dropdown reading Owner / Member would invent one in the place a reader is most likely to believe it.

The invite row stores an email, delivery sends an email link, and claim verifies the signed-in person's email. The old email or phone label drew a second identity path no contract implemented, so the screen now names the path that exists.

It is genuinely tempting: the inviter knows the house and could save them a step. But what gets sorted to a seat is the one thing that seat has to own, and pre-ticking Kitchen for them is how a product tells somebody what their part of the house is. Frame 1 is where that question gets asked, and it gets asked of them.

An invitation with a clock on it is a clock on a conversation between two people who live together. The row on frame 4 will say invited, not joined for as long as that is true, and that is the whole of the follow-up the product does.

There is no permission model between two people who live in the same house, and a remove button that only one of them has would have been one. The screen does not police the decision; it states the consequence and lets a person make it, which is the same posture every other destructive screen in this deck takes.

Deleting a person from most products loses their work. Here it loses nothing and re-sorts two decisions into nobody has this — the one band that depends on no seat at all. That is worth naming on the screen, because it is the thing that will actually be noticed a week later.

Deleting the house asks you to type its name because two years are gone for good. A seat comes back with its tags, so the same ceremony here would be borrowed gravity. The ghost button is the whole weight, and the difference between the two screens is the point.

Access ends, but the seat keeps its identity and tags behind the active list. Re-inviting Nora restores that same seat rather than manufacturing a new person and asking her to reconstruct her part of the house.

The alternative was to gray the button out and let the subscription holder be unremovable, and that is a permission model with a friendlier face — it makes one seat permanent and the other conditional. Rung 2 says the cost out loud and leaves the decision where it was. The safe way out is to keep the seat while the current payer initiates the transfer.

NH in the dock and he in the copy. Written from the seat, so yours on Sam's phone is Sam's on hers — and the argument that the second seat is a peer is worth very little until the deck has drawn her holding the same button he has.

Same treatment as the deletion screen on mockup 15, for the same reason: it interrupts and it is not an error tone. There is still no red rung here. The seriousness is carried by the sentence about read-only, never by a color that would make every other screen look calm by comparison.

The shared cta-outline variant is reused here and on ordinary cancellation. It stays visibly actionable after the consequence is stated without giving a destructive commit the filled primary weight.

Nora signed CO-2 is sendable — it changed the house and the money, and scope is shared. Nora opened this is not, and neither is Nora has not looked at it. The test is whether the event would still be in the binder a year later: a signature would, an opening would not.

You have not opened this and it closes Thursday. Same underlying fact, addressed to the person it is about, which is the difference between a reminder and a monitoring tool.

Because somebody will propose it. A read receipt turns a calm binder into surveillance between two people who live together, and an unread badge makes forty-six records shout — and both look like reasonable product decisions right up until they ship.

No command id, delivery status or technical closure language. The result answers the two questions the action creates: what moved, and what stayed.

The server keeps and retries it. Saying on its way is enough; a provider outage must not turn a finished household action into a second button or leave Nora's access active.

They are unheld for sorting now and still attached to Nora's closed seat for restoration later. That is one fact viewed at two times, not two copies for a cleanup job to reconcile.

The screen can promise Nora stayed only after the server confirms the transaction did not commit. A connection disappearing after send is the next frame, not this one.

The local seat is not deleted to make the action feel fast. Removing Nora before the server agrees would tell Sam she is gone while she can still open the house.

This is the destructive-write version of the deck's existing confirmation state: a missing response says nothing about whether the transaction committed.

A retry cannot close an already closed seat again, create a second removal event or send a duplicate email. The household change and its one durable notice share an idempotent result.

Frame 3's annotation says the ask reaches her once, the way anything else does, and then it waits without accruing. Waiting without accruing means it cannot live anywhere that counts things: not the dock, not Now, not a list of things pending. What is left is the screen whose subject it is. She holds three tags; one of them has a question attached; the question is under the tags. Nothing else on her phone knows it exists.

No is a complete and unremarkable answer to being asked for something that is yours, and a filled Yes beside a ghost No would say otherwise. Frame 3 already draws the ask as a proposal that takes effect on nobody's screen until she agrees; drawing the agreement as the primary act would undo that on the one screen where it matters.

tag_swap_requests gained an optional sentence for exactly this, and it is the only part of the card that is his voice. Everything else states the consequence in ours: six decisions, and nothing settled moves. A swap that silently changed who was asked about a decision already made would be the expensive misreading here.

Z9 shipped a version of this on the seat's own ask screen, reached from frame 2's Ask, and that was an invention rather than the deck's. This frame proposed the placement above instead, and Q163 ruled it canonical on 2026-09-04: a surface nobody may announce has to be on the screen she already opens for the subject, and Z9's screen is the door you open to make an ask, not to find one. It keeps withdraw and loses the accept and decline — not both, because two reachable copies of one ask would need a rule for which is canonical when she answers on one and opens the other. And it does not expire: an ask she never opens is still there unchanged in four months, which is the cost of refusing to let it accrue, and Z5's withdraw is the exit — the proposer knows it is stale and she never has to.

Frame 5 put no clock on an invitation, on purpose. The other half of that is this screen: an invitation sent to the wrong address, or one that is no longer wanted, would otherwise sit on frame 4 until somebody accepted it.

No are you sure, because the consequence fits on the screen and is undone by sending another. The card is shorter than frame 6's because an invitation holds nothing: no tags, no settled decisions, and no notice to send, since Nora has not joined anything she could be told she left.

Whoever could have sent it can cancel it, which on a homeowner's house is every owner seat. It is the same rule as 24-people frame 7, where a builder cancels an invitation that is out; there it can also change the answer to whose house is this, which is never asked here.