v0.4.4 — multi-host + Living Notes

OpenRig v0.4.4

Summary — Multi-host + Living Notes

OpenRig v0.4.4 lands the multi-host foundation: a shared rig topology
can now span multiple hosts, with a staged spin-up flow, real cross-
host file movement, and a consolidated For-You activity feed that
merges signal across every host in the topology. The VPS product-
factory story hardens for real multi-host operation.

Alongside the multi-host foundation, this release ships the Living
Notes signal layer — a durable, agent-authored notes surface that
threads INTENT → PLAN → DELIVERED down the mission tree, with a
one-structure review contract that reads left-to-right as a single
vertical stack (INTENT above, PLAN in the middle, DELIVERED at the
bottom; delete-not-demote when a plan changes). Composer surfaces make
authoring cheap; the review surface makes reading intent-versus-build
one-glance.

Operator UX picks up rig ps consolidated default (the token-
efficient-defaults family gains progressive disclosure that keeps the
default view glanceable without hiding the fleet), an agent altitude
coordination panel that surfaces multi-agent state at the right
altitude for the operator, and the operationalize-SDLC control
plane which pulls the release / delivery / lifecycle levers into a
single control surface. As-built docs closeout catches everything up.

Migrations, if any, are additive. Existing v0.4.3 databases upgrade by
running rig daemon start on the new daemon.

What Shipped

Multi-host foundation

• Shareable whole-topology staged spin-up — a rig topology can be
  brought up in stages across multiple hosts; the spec + the daemon
  coordinate to reach a green whole-fleet state without requiring a
  single-host bring-up. Prior to this release, a whole-topology spin-
  up assumed a single host.
• VPS product-factory multi-host hardening — the shipped
  openrig-user/openrig-architect operator flows work correctly
  across VPS/self-hosted product-factory scenarios; multi-host
  handshake + registration hardens.
• Multi-host consolidated For-You feed — the For-You feed
  aggregates activity across all registered hosts in the topology, not
  just the local daemon. The stream classifier + real-data fidelity
  from 0.4.3 apply per-host and merge upstream. A real-host feed-
  subscription capture ships as belt-and-suspenders proof (see
  Known Follow-ons).
• rig file cross-host movement — files move across the
  topology's registered hosts via the rig file surface. Real
  registered-host two-host end-to-end round-trip proves the flow on
  top of the VM stand-ins already merged.

Living Notes

• Signal layer — a durable, agent-authored notes surface at
  mission and slice altitude; INTENT / PLAN / DELIVERED entries thread
  down the mission tree with agent authorship + timestamps.
• Composer surfaces — cheap authoring surfaces make Living Notes
  the first-class place agents record decisions, plans, and delivered
  work.
• One-structure review contract (§3.1) — corrective rebuild — the
  Living Notes review surface reads left-to-right as a single
  vertical stack (INTENT above, PLAN + mockup in the middle,
  DELIVERED with paired proof at the bottom); a plan change deletes
  the old plan and writes a new one — never demotes / stacks multiple
  competing plans. The corrective rebuild replaced an earlier
  three-column layout after human review.

Operator UX

• rig ps consolidated default + progressive disclosure — the
  default rig ps now consolidates the fleet's readable rows into a
  single glanceable default; progressive disclosure via --full /
  -A / per-scope filters keeps the rich per-node record retrievable.
  Follows the token-efficient-defaults family established at 0.4.0.
• Agent altitude coordination panel — a coordination surface
  scoped to the right altitude (workspace / mission / slice) so the
  operator sees the actual coordination state without drowning in
  per-seat detail. Composes with the workspace observability tabs
  shipped at 0.4.1.

Doctrine

• Operationalize the SDLC control plane — release / delivery /
  lifecycle levers pull into a single surface. The lanes that shipped
  0.4.1 → 0.4.3 (release-cut squash + bounded-diff, sidecar-operator
  host cutover, curation pass) are now first-class control-plane
  actions rather than lifecycle-tribal-wisdom.
• As-built docs closeout — the as-built documentation family
  (docs/as-built/architecture.md, docs/as-built/cli-reference.md,
  codemaps) is caught up to what shipped through 0.4.4.

Behavior + Compatibility

• Migrations — additive only. Existing v0.4.3 databases upgrade
  by running rig daemon start on the new daemon.
• Multi-host registration — the multi-host handshake is
  backward-compatible with single-host deployments; single-host
  operation is unchanged.
• rig ps default view — the consolidated default is a
  compact readable view; --full returns the v0.4.3 default shape.
• For-You feed — multi-host feed aggregation is opt-in via
  registered-host membership; a single-host topology sees no
  behavior change.

Known Follow-ons

• R2 — iOS-Safari S20 (Living Notes composer) — deferred to
  0.4.5 for iOS Safari verification.
• R4 — S18 symlink footgun — routed to the 0.4.5+ backlog.
• openrig-user stale plugin copy + whoami --all-hosts silent
  host filter — 0.4.5 candidates.
• Wider mission-template prose sweep — post-cut sequencing.
• Belt-and-suspenders real-host proofs — R13-1 (published-npm
  Linux install smoke + daemon-start / /healthz / WebSocket
  handshake), R1 (real registered-host two-host e2e for S13 + S18 on
  top of the merged VM stand-ins), and R3 (S15 real-host feed-
  subscription capture) are sequenced as post-publish lifecycle
  validation lanes. The shipped code was already proven via VM/SSH
  stand-ins per PM rulings; the real-host lanes are defense-in-depth
  belt-and-suspenders proofs, not release gates.

See Also

• CHANGELOG.md — the standard changelog entry for 0.4.4.
• docs/releases/v0.4.3.md — the prior release ("rigs that
  survive").
• docs/releases/v0.4.2.md — the daemon-status hotfix.
• docs/releases/v0.4.1.md — the workspace observability overhaul.