DUNIN7 · Loomworks · Companion Design · Mockup
The level above an engagement: the Operator's list of engagements, each showing its state, with Personal broken out as its own zone and cross-cutting views (needs you, recent) as lenses one tab or one voice-command away. Engagement-list-primary; the lenses are derived views, not the home. Addressing per the engagement-identity decision record. Illustration, not specification.
Three zones, organized by visibility. Your space (Personal, visibility='personal'), your engagements (ordinary work), shared (the Loomworks commons, visibility='automatic'). Administrative (E0001) is instance plumbing and deliberately does not appear — only show what's relevant.
Personal is an engagement. It has an E#### (E0030), opens into the same four-room surface as any engagement, and "remember about me" is committing to it. It is broken out as its own zone because it functions as your cross-cutting space — but structurally it is a visibility='personal' engagement, not a separate object.
Addressing (per the identity record): each row shows the per-Operator number (your 7, 14, 0 for Personal — your own handles) and the shared E####. Voice addresses by name. The UUID is the invisible cross-boundary identity, never shown. Numbers are yours; another member's home shows the same engagements with their own numbers.
Status. Design illustration with real Loomworks data shapes — not a specification. Zone treatment, Personal-as-zone vs. pinned-row, and lens transitions are CR-level decisions against real components.