6.3 KiB
OpenRig v0.5.12 — coherent work, quiet waits, and a normal TUI front door
Status: release candidate. Exact-cut substance review, final release verification and publication remain separate steps.
OpenRig 0.5.12 connects everyday workflow actions to useful progress views, recoverable ownership and a readable TUI. The goal is to let an operator or agent start, understand, adapt and return to work without maintaining status copies or knowing a private recovery recipe.
Record a judgment once
An authorized, evidence-backed proof judgment derives the affected proof, slice, mission and project readiness. Correcting that judgment updates its dependent views while retaining unrelated work and the original evidence. Code, attributed patch-equivalent work and non-code artifacts can carry truthful provenance. A checkbox, uploaded file or closed queue item does not become semantic acceptance, and readiness does not mean publication.
Know which graph is running
Ordinary workflow inspection distinguishes authored scope from the bound
running graph, advisory ordering from executable dependencies, and planning
waves from runtime steps. rig workflow revise previews supported changes
before applying them, preserving completed work and current custody.
Incompatible edits name the decision that needs reconsideration. Operation
identity and rig workflow operation recover an ambiguous creation/revision
result without duplicating its effect. Selected development-method guidance
returns with workflow continuation, including the original story and useful
next action; the daemon does not judge the meaning of agent-authored prose.
Give failures an owner and a recovery path
Exception readiness explains the selected owner before failure and keeps
missing configuration, a genuine no-match and unavailable routing evidence
distinct. Routing uses authored agent identities or registered human fallback.
An unhandled dependency-branch failure records its occurrence, owning task
and wake together, even when another branch remains live. A failed nudge does
not erase the task. After correcting the cause, use rig workflow resume
with --occurrence <failed-qitem-id> to select that failure: its obsolete
exception closes in the redrive transaction, while other unresolved failures
and completed work remain visible.
Wait quietly without losing work
Healthy unchanged waits avoid repeated full-context packets. Overlapping notifications for the same actionable episode share presentation and retain provenance. Changed blockers, missed delivery and stranded work retain bounded recovery or escalation. Ordinary reads expose the current owner, blocker and next useful decision first, with explicit expansion for complete evidence. Unknown activity remains unknown; a reminder is not progress.
Start and return through the same TUI
Bare interactive rig is the normal front door, including first setup,
daemon-down startup and return after a restart. The TUI shows the intended
instance and observed prerequisites, offers daemon startup, and supports
selecting the rigs and seats to return to work. Kernel is recommended first;
unselected rigs keep their histories. Resume preserves the selected seat's
recorded conversation when available. An unavailable resume offers a named
repair or an explicitly confirmed fresh, re-primed conversation; it is never
silently replaced. Launcher and native startup fixes retain useful errors
when a runtime or dependency is unavailable.
Browse general instance settings in CONFIG
CONFIG organizes instance, workspace/context, display/timezone, waiting, snapshot and recovery settings into readable categories with source and override provenance. Advanced settings and full values remain discoverable. Slack and human connections are one child of CONFIG. Opening or refreshing the browser is passive and secret-safe; configured values remain distinct from observed application, connectivity and delivery. Users can return to ordinary scope and work views without opening configuration files.
Operator notes
Root, CLI, daemon and web-UI package versions are 0.5.12. The terminal TUI
retains its independent 0.1.0 version. Node requirements and the ordered
migration head 079_workflow_lifecycle_parallel are unchanged from 0.5.11;
this release adds no database migration.
Use the supported upgrade and continuity procedure when adoption is authorized. Preparing this candidate does not restart a daemon or renew existing seats. Configuration inspection is not an editor, credential migration, automatic repair or a promise that every setting hot-reloads. Editing an authored graph alone does not adopt it into a progressed workflow. The exception repair does not retroactively create tasks for failures already committed by older code; inspect retained occurrences and use the supported recovery route deliberately.
Validation scope and known limitations
The accepted development outcome includes one less-primed, returning/assisted agent journey through two dependent slices: recording and correcting proof, revising the graph, waiting and returning, recovering a real failed handout check, and navigating CONFIG back to work. Focused mechanism reviews and installed controls support that journey. Native startup, resume and wake observations retain their original source cuts and times; they are reused with attribution, not presented as new runs on the version-only candidate. Candidate package and generated-version checks are recorded separately from those development judgments.
- This was not an unfamiliar-human study, an unassisted greenfield usability trial or all-platform verification. Setup and one-time native approvals remain part of the recorded journey.
- The final exception task was consumed through public read/claim/action after its placeholder destination could not receive a nudge. It does not establish native exception delivery or external human receipt.
- Quiet-wait measurements establish the tested workload's attention and recovery behavior, not a global latency guarantee or provider billing-token savings. A retained startup catalog-unavailable control also failed on its unchanged parent; the evidence is not an all-green test-suite claim.
- Whole-package substance review, exact-release verification and publication must still bind this prepared candidate. These notes do not announce an available npm release or authorize runtime adoption.