Back to corpus
architecturetechnical paper candidatescore 42
04 — Architecture Forge
**Track 4 of 4 in the leisure-goal synthesis.** **Subject:** Phone-as-cockpit, mesh-as-engine. The operating-system spine. **Anchor commit:** Pebble HEAD `3803b76` (V0.8 P5 Wave 4 iPad split-view shipped 2026-05-11).
Full HTML reader
Read the full artifact
Extracted abstract or opening context
**Track 4 of 4 in the leisure-goal synthesis.** **Subject:** Phone-as-cockpit, mesh-as-engine. The operating-system spine. **Anchor commit:** Pebble HEAD `3803b76` (V0.8 P5 Wave 4 iPad split-view shipped 2026-05-11).
> **Leisure** is the state where the home Macs hold the project memory, the home Macs do the work, and the iPhone is the cockpit. The phone never *runs* the system; the phone *governs* it. Confirmations are cheap, intervention is rare, and the system has a fallback for every degraded path so partial-mesh is the *normal* operating state, not the exception.
The formula has one binding constraint: **every reachable mesh capability must be addressable from the phone, or it is a bug, not a phase-1 limitation.**
These are the only legitimate shapes work can take in the leisure OS. Mixing two archetypes inside a single endpoint is forbidden (the Crucible architecture spine already enforces this for Pebble V0.8). Every new feature must declare its archetype before it gets built.
| # | Archetype | Plane | Failure mode | Concrete examples | |---|---|---|---|---| | 1 | **ControlOp** | Control | Throw loudly, never silently retry | Pebble send-prompt; aura-gateway `/inject`; codex-gateway `/codex/inject`; restart-service; switch-chat | | 2 | **DataStream** | Data | Silent retry, banner only when stale | Pane snapshot polling; `/panes/<tty>/response`; mesh_pane_state reads; iMessage-like delivery dots | | 3 | **CaptainSummary** | Bridge | Always falls back to gateway heuristic | `/captain/ask` `Where are we?`; rate-limit status; next-prompt drafts; `[CTRL]/[DATA]/[STATE]/[COMPACT]/[CONTEXT-RESET]` prefix language | | 4 | **SensorStream** | Data | Drop frames on backpressure | KARL trajectories; cognitive-twin events; Femto/MediaPipe pose at LUMA :9703; ntfy idle-detection state machine on mac4 | | 5 | **AutopilotAgent** | Bridge | Pause on first failure, never silent loop | Captain `draft N+1` → Codex auto-queue; Pulse sessions; ops:autopilot sleep-loop; mac4 idle-watcher → ntfy | | 6 | **WidgetGlance** | Projection | Read-only, schema-checked, ≤120 char previews | Pebble Home Screen widget reading `<sharedContainer>/projection/latest.json`; MeshHealth tile (planned) | | 7 | **VoiceDictation** | Control | Always editable before send | Pebble Whisper composer; cue-prompt drafts; future Siri Shortcuts via AppIntent |
Promotion decision
What has to happen next
Promote into a technical note or architecture paper with implementation anchors.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.