← Case Studies/Case #004/C4-013
C4-013DecidedOperations & SafeguardsDerived2026-04-05

The Portable Work Node Must Support Both Remote and Local Use Without Reconfiguration Debt

The portable work node is not purely headless. It may be opened and used directly at the office, then returned to remote-optimized operation later. Mode transitions carry minimal cost by design. A device that works only when closed or only when open creates operational drag. Dual-mode is the correct baseline.

Freshness
Active

Active. Reverify if one operating mode becomes negligible.

Dependencies
← C4-005: Assign Distinct Roles to Distinct Machines — No Unified Pattern← C4-010: Put Admission Control in Front of Heavy Local Inference

Used by

→ C4-014: Treat Tablet-Class Devices as Auxiliary Surfaces — Not Trust-Boundary Shortcuts→ C4-016: Publish the Reasoning Chain — Obfuscate the Deployment
#dual-mode#portable-node#local-use#remote-use#reconfiguration

Capture

The portable work node is not purely headless. It may be opened and used directly at the office — locally, with its own display, keyboard, and peripherals — then closed and returned to remote-optimized operation later.

Both modes are real. Neither is a special case.

Why

A design that works only when the machine is closed or only when it is open creates operational drag at every mode transition.

If the machine must be manually reconfigured to switch from remote-optimized to local-use mode, the operator will accumulate a tax on every transition. Over time, this tax becomes significant — and it creates the temptation to leave the machine in one mode permanently, which suboptimizes the other.

The correct design requires zero manual reconfiguration at mode transitions. The machine is available locally when the operator is present. It is available remotely when the operator is away. The transition is automatic or trivially simple, not a procedure.

This also means the admission control and power management decisions (C4-010, C4-012) must work correctly in both modes — not only when the machine is being operated remotely, and not only when the operator is sitting in front of it.

Why-Not

Why not optimize only for remote headless use? The operator sometimes benefits from direct local use — richer display, full keyboard, faster network, access to physical peripherals. Treating local use as unsupported degrades a real and valuable mode of operation for no benefit.

Why not optimize only for local desk use? Remote continuity is a core requirement. An endpoint that only works well when the operator is physically present does not support the travel and remote work patterns this architecture was designed to enable.

Commit

Decision: Design the portable work node for dual-mode operation: remote-first when the operator is away, locally usable when present, with minimal or zero transition cost between the two states. Neither mode is treated as exceptional.

Confidence: High.

Timestamp

2026-04-05

← C4-012C4-014 →