0 Fork 0

mirror of https://github.com/mvschwarz/openrig.git synced 2026-11-07 05:56:21 -10:00

Files

T

Multi-host + Living Notes.

Multi-host foundation: shareable whole-topology staged spin-up brings
a rig topology up across multiple hosts in stages; VPS product-factory
multi-host hardening ships with rig host verbs (add / list / doctor,
capped at three; one built-in product-factory-vps posture, three-
valued per item); the transport posture is documented (ssh for pane
ops, http-bearer for daemon REST, no cross-transport fallback); the
For-You feed aggregates activity across every registered host; and
rig file moves files across the topology's registered hosts.

Living Notes: durable INTENT / PLAN / DELIVERED signal layer at
mission and slice altitude with agent authorship + timestamps; cheap
composer surfaces make it the first-class place agents record
decisions, plans, and delivered work; the one-structure review
contract 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 or stacks multiple competing plans.

Operationalize the SDLC control plane: conventions SSOT ships in
source at docs/reference/sdlc-conventions.md (Living Notes UI section
names, proof-contract format + plannedRef mockup pairing, staged-
approval locks, C1 proof header + closed sets, three role contracts,
curation rule, elastic-middle doctrine, advisory fail-open audit
posture); rig scope slice create scaffolds the convention sections +
proof + PROOF.md + an IMPLEMENTATION-PRD.md skeleton for every
template kind; rig scope audit + rig workspace doctor gain sdlc-
convention advisories (records-and-advises, gates on HIGH only); the
mission-slice-sop skill ships in canonical source with byte-parity
guard; rig proof / rig scope slice create / rig scope slice approve
help + cli-reference teach the SDLC flow.

BREAKING: rig ps default flips to consolidated all-active-rigs
compact projection (the v0.4.0 current-rig-only default is retired -
it hid running rigs from the operator's field of view). --json is
scope-not-shape (still a bare array with existing per-entry keys;
scope widens to all non-archived rigs including stopped ones; one-line
migration for the old fleet firehose: rig ps --nodes -A --full).
-A / --all-rigs keeps exactly ONE meaning (the --nodes fleet widener;
bare -A is a structured teaching error). --nodes names its scope
everywhere (session default local-only; --host <id> --nodes requires
--rig or -A; multi-host fan-out is rollup-only by default; the
explicit ladder --all-hosts --nodes -A --full fans out per-node with
hostId-stamped projected rows). --all-hosts / --hosts --json emits the
shared AggregatedPayload (items + hosts with closed-enum statuses:
ok | unreachable | unsupported-transport | auth-failed).

Operator UX: agent altitude coordination panel scopes multi-agent
state to the right altitude (workspace / mission / slice) so the
coordination surface reads without per-seat drowning; composes with
the workspace observability tabs from 0.4.1. Docs closeout catches
docs/as-built/architecture.md, docs/as-built/cli-reference.md, and
the codemaps up to shipped state.

Migrations: additive only. Existing v0.4.3 databases upgrade by
running rig daemon start.

Behavior change (rig ps default view): the compact all-active-rigs
projection replaces the current-rig-only default. If your call sites
relied on the v0.4.3 default shape, add --full for the rich per-node
projection or --rig <name> for the prior scope.

Public-safety scrub applied inline to packages/ui/twin/corrective/
fixtures-corrective.ts (one demo-fixture role identifier neutralized
to the demo-namespace baseline established at 0.4.1).

See CHANGELOG.md and docs/releases/v0.4.4.md.

2026-07-06 01:20:09 -07:00

6.2 KiB

Raw Blame History

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.

6.2 KiB Raw Blame History