The family's addresses: one household, many hats, mapped

Ask a household "what's your email?" and listen to the negotiation that follows — use his for the school, hers for the doctor, the shared one for the airline except nobody checks it since Pesach. The arrangement grew a decision at a time, each reasonable, the total incoherent. Email architecture is one of those household systems — like the key drawer or the tzedakah pushka — that works beautifully when someone designs it and chaotically when nobody does. The deliberate design takes twenty minutes, and it outlives every phone the family will ever own.

The four-layer map

Layer one: the household address. One shared identity for things addressed to the family as a unit — the shul, the school's parent list, the simcha invitations, the landlord. Both parents read it; either answers. Its virtue is continuity (the school reaches "the Kleins," not whichever parent's inbox is current); its discipline is scope — the moment personal correspondence drifts in, the shared address becomes nobody's responsibility. Institutions in; conversations out.

Layer two: the per-person identities. Each adult's own address for their own life — correspondence, accounts, the work identity separate again. This is where privacy lives (the adult's legitimate quiet applies to mail exactly as to search), and where per-person defense pays: one leaked address burns one compartment, per the architecture-defense model.

Layer three: the errands identity. The household's shared transactional address — checkouts, registrations, receipts. Deliberately unloved: reviewed weekly, archived monthly, mourned never. Every promotional flood it absorbs is a flood the human layers never see.

Layer four: the children's inboxes. First inboxes on the designed model — family-and-school admission, parent visibility scoped by age, per the child-safe architecture; the full onboarding is the child's first email. The map's rule: children appear on the map when they need mail, not when they ask — and need, in practice, arrives with institutions (the school portal, the bochur's yeshiva list), not with friends.

“A family's addresses are its front doors. The map decides which knock rings where — and which door the children answer.”

kolbo.life

Who answers what: the ownership rules

The map fails without ownership; three rules keep it alive:

1. The household address has a duty roster. One parent owns it per week or per category (school = her, shul = him) — owned mail gets answered; co-owned mail gets assumed. The same one-owner clarity that runs the family's banking alerts and coordination anchors.
2. Institutions get exactly one door. The school writes to the household address, period — updated everywhere, the first week. Half the "we never got the notice" incidents in a household's year are institutions writing to a door nobody watches anymore.
3. The map survives transitions. The seminary year, the bochur's dorm, the married daughter — each transition re-draws one corner of the map deliberately (her identity goes with her; the household list updates). Improvised transitions are how the sheva-brachos address ends up receiving the mortgage documents a decade later.

The migration, painlessly

Households arriving from chaos run the standard thirty-day pattern: draw the map, open the missing identities, then let each incoming stream teach you its correction — every misdelivered arrival gets its sender updated on the spot. A month of ten-second corrections migrates the whole postal life; the old addresses forward meanwhile, then retire to receive-only, then die. The archive imports where it belongs — attachments and all, into the document-handling patterns that give the family's papers a permanent home.

Frequently asked questions