← Case Studies/Case #004/C4-005
C4-005DecidedSystem ArchitectureDerived2026-04-05

Assign Distinct Roles to Distinct Machines — No Unified Pattern

The environment has distinct endpoint classes: office-bound automation node, portable secure work node, and personal control surfaces. Each retains its own role, power policy, and interaction pattern. Forcing one machine pattern onto all creates wrong defaults on at least one class. Role specialization is not overhead — it is the architecture.

Freshness
Active

Active. Reverify if one machine class disappears, becomes managed differently, or takes on materially new responsibilities.

Dependencies
← C4-001: Keep Sensitive Compute Local — Remote the Operator, Not the Data← C4-002: Separate Control Surfaces from Execution Surfaces← C4-003: Use a Private Overlay Network — Not Publicly Exposed Remote Services← C4-004: Preserve the Method — Do Not Publish the Client's Concrete Deployment

Used by

→ C4-006: Maintain a Portable Secure Work Node as the Primary Remote Execution Surface→ C4-007: Keep the Office Automation Node Awake Only When Automation Is Active→ C4-008: Prefer Command-First Mobile Interaction — Reserve Full Remote Desktop for Escalation→ C4-009: Build a Command System with Progressive Promotion — Repeated Actions Earn Their Shortcut→ C4-010: Put Admission Control in Front of Heavy Local Inference→ C4-012: Set Power Policy by Machine Role — Not a Single Global Preference→ C4-013: The Portable Work Node Must Support Both Remote and Local Use Without Reconfiguration Debt→ C4-016: Publish the Reasoning Chain — Obfuscate the Deployment
#machine-roles#role-architecture#device-specialization#endpoint-classes

Capture

The environment contains multiple endpoint classes with different strengths, constraints, and intended uses:

These classes want different power policies, interaction patterns, and security configurations. Forcing one pattern onto all of them creates friction in at least one class at all times.

Why

Stable office-bound automation, portable secure execution, and mobile command-and-control each require different defaults. A machine optimized for one role performs poorly as another.

The office node benefits from staying awake during automation windows, connected to peripherals, and stable. Making it also function as a remote execution target for sensitive work would mix its ambient automation role with a more sensitive security posture — creating ambiguity about which workloads belong where.

The portable node benefits from being the reliable remote execution anchor — reachable, consistent, and guarded. Making it also absorb all local automation would strain its mobility and power constraints.

Personal devices benefit from being treated as pure control surfaces — light, mobile, no sensitive state. Asking them to also execute sensitive work breaks the trust model.

Role specialization is not overhead. It is the architecture.

Why-Not

Why not make every machine interchangeable? Interchangeability erases useful specialization and leads to the wrong defaults on at least one device class permanently. A machine configured to serve multiple contradictory roles cannot be optimally configured for any of them. The result is a blended policy that serves no single role well.

Why not consolidate everything onto one endpoint? Consolidation increases blast radius. If the single endpoint is compromised, degraded, or unavailable, all work stops. It also makes the security model harder to reason about — a single device that handles ambient automation, sensitive execution, and remote access has a more complex and harder-to-harden attack surface than three devices with specialized roles.

Assumptions

Commit

Decision: Use a role-based architecture. The office-bound node handles ambient automation and multi-display work. The portable work node serves as the secure remote execution surface. Personal devices operate as control surfaces only. Each class retains its distinct role, power policy, and interaction pattern.

Confidence: High. This decision operationalizes C4-001 and C4-002 into the concrete machine inventory.

Timestamp

2026-04-05

← C4-004C4-006 →