Private office system

Dylan Control Center

A private-office operating model built around a Mac Studio control center, a Personal Assistant role as Dylan’s digital extension, and a House Manager role as the estate’s operational extension.

Mac Studio with luminous flowing light trails
Mac Studio

Core idea

A stable control center with role-based execution

Dylan’s Mac Studio becomes the long-term concierge desk and operations brain. The current iPhone is assigned to the Personal Assistant role now, and the next dedicated device to add is the House Manager iPhone.

Control center

Mac Studio

  • Central control center for executive and estate operations
  • Shared calendars, notes, task boards, vendor records, and dashboards
  • Password manager administration and recovery records
  • Messaging orchestration, summaries, reminders, and future AI concierge layer
  • Stable home for continuity even when staff changes
Street event and gallery-like gathering in a mountain town
Two Heads Art Show

Role one

Personal Assistant

  • The currently available iPhone is assigned to this role now
  • This role functions as Dylan’s digital extension
  • Dedicated Apple account, email, and phone number
  • Travel, scheduling, errands, messaging, bookings, logistics, and follow-through

Role definition

Dylan’s digital extension

  • Calendar, scheduling, and priority coordination
  • Travel, reservations, movement, and logistics
  • Email/admin follow-up and communication support
  • Project and business coordination across Dylan’s world
  • Maintaining continuity of what Dylan needs, expects, and is tracking
  • The strongest handoff discipline, because this role sits closest to Dylan’s actual working life

Role definition

House Manager

  • This remains the next dedicated device to add
  • This role functions as the estate’s operational extension
  • Dedicated Apple account, email, and phone number
  • Lighting, locks, cameras, gates, utilities, maintenance, vendors, and readiness
  • Handles the systems and physical execution layer of the estate

Coordination domain

Two Heads

  • Support Dylan-side coordination for Two Heads projects and collection-related work
  • Maintain shared timelines, notes, follow-ups, and project visibility
  • Coordinate with Austyn’s Assistant on overlapping scheduling, logistics, communication, and execution
  • Keep collaboration synchronized without collapsing role boundaries

Coordination domain

Blue Cloud Ranch

  • Coordinate business/admin follow-through tied to the ranch
  • Support planning, communications, tasks, and external follow-up
  • Work in sync with the House Manager when site readiness or property operations are involved

Coordination domain

New Normal

  • Handle communication, scheduling, status tracking, and project coordination
  • Support ongoing film/business tasks without requiring a separate role yet
  • Keep New Normal work connected to Dylan’s broader calendar and priorities

Coordination interface

Personal Assistant ↔ House Manager

  • The Personal Assistant coordinates schedule, guests, travel, events, and priorities
  • The House Manager coordinates property readiness, access, vendors, and on-site execution
  • These roles must stay in sync whenever time, people, and place intersect

Coordination interface

Personal Assistant ↔ Austyn’s Assistant

  • Used where Dylan and Austyn’s worlds overlap through Two Heads and shared project work
  • Supports coordination without blurring ownership
  • Keeps both sides synchronized while respecting separate roles
Future event / estate / project image

System logic

What routes through the Mac Studio vs the role iPhones

  • Best on the Mac Studio: dashboards, shared calendars, notes, docs, summaries, automation, password administration, and long-term continuity
  • Best on the role iPhones: apps that unlock, open, or locally control physical systems, plus SMS/2FA and field communication
  • Email identities can be role-based, but summaries and admin visibility should flow back to the Mac Studio
  • Role phone numbers should be treated as permanent service numbers, not personal numbers

Handoff and continuity

How the system survives staff change

  • Recover the physical role iPhone
  • Change the device passcode
  • Review trusted devices and recovery options
  • Remove the prior human from vault access
  • Rotate sensitive passwords when needed
  • Update the Mac Studio admin record showing who currently holds the role
  • Brief the new human using role handbooks and escalation notes

Practical hardware

What is covered and what is next

  • Dylan Mac Studio control center
  • Personal Assistant iPhone already in hand and assigned
  • 1 iPhone still needed for House Manager role
  • 2 dedicated phone numbers, one per role
  • Custom NAS, external SSD, and UPS for the Mac Studio
  • No separate Business Assistant device yet