Skip to content

v0.5.3 — the context release

Choose a tag to compare

View all tags
@mvschwarz mvschwarz released this 26 Aug 02:55
· 2507 commits to main since this release
v0.5.3
e6add8b

OpenRig v0.5.3

Summary — "The context release"

v0.5.3 puts context on rails. Pull exact sections of shipped skills and library entries by address instead of reading whole files. Discover context by asking, not by guessing paths. Refocus resolves refs automatically. Handovers write a durable, superseded-chain seat recap that lands in every restore packet. Composition is by reference, so there is no second copy to drift.

v0.5.3 contains v0.5.2 in full. One lineage, no divergence.

No new migrations. Migration head stays at 071 (matches v0.5.2). Nothing to apply on a v0.5.2→v0.5.3 upgrade. No CLI-command or flag removals or renames from v0.5.2.

What Shipped

Address grammar for context: rig context get (headline)

Pull the exact bytes of one section:

rig context get <pack-ref>/<file>#<H2-slug>[/<H3-slug>]

The /<file> component is required even in a one-file pack. Refs are canonical full paths (e.g. skills/<namespace>/<name>). A bogus slug fails loud and lists the addressable sections. rig context list enumerates every shipped entry's ref and name; rig context show inspects one. Cross-source access (seat: / mission: atoms) is an authoring affordance — declared in pack manifests and granted via rig context profile --rig/--seat/--mission during composition — not an ad-hoc argument to get.

openrig-skills router — ask → ref → load

The router teaches the three-step: ask your question, get a ref, load by ref. Use it when you don't know which skill or context applies, or nothing is projected after a cold boot.

Durable seat recap — rig context recap-write

Handover time, compaction boundary, or any moment your successor would otherwise re-derive your state from scrollback: rig context recap-write maintains a seat-scoped RECAP.md beside LEARNED with a collision-safe superseded chain. Restore packets now carry an authored-recap pointer.

Refocus resolves refs automatically

The refocus hook resolves library refs automatically (ref beats file), fails loud but non-blocking, and delivers pointers. This is the shipped channel for pointing running seats at new content.

Bounded expertise packs on demand

rig context get serves expertise packs by path-like ref, e.g. skills/process/context-engineering. The old context-pack: colon form was removed and the CLI says so.

Caveat that pack: it is titled "Traditional Context Engineering — 2024-2025 Snapshot" for a reason — provisional, historical, non-normative by founder ruling. Current OpenRig skills, explicit user rulings, and measured practice outrank it on any conflict.

STOP doing (was correct under 0.5.2, is wrong now)

  1. STOP copying library content into seat or mission files to compose context. Compose by ref: addressing means there is no second copy to drift. Nothing catches the copy automatically; it is still a defect by rule.
  2. STOP treating a MODEL DIVERGENCE proclamation as alias noise. The canonicalize-then-compare fix ended the pinned=fable / effective=claude-fable-5 false-positive class, and the monitor now isolates per-seat throws. A proclamation on this runtime is a real escalation — act on it.
  3. STOP reading "founder-gated" in tool errors as an authorization wall. The overstated wording is retired from the scripts; those guards demand explicit paths (e.g. OPENRIG_SKILL_CANON_ROOT), not permission. The real founder boundary is exactly: pushes and PRs. Local commits and ordinary apply work never need founder word.
  4. STOP hand-placing evidence or trusting a placeholder PRD as the proof contract. rig proof add pairs evidence to the contract, and a pristine scaffold PRD can never silently become that contract: the authored SPEC serves with a named advisory (contractSource in the echo tells you which source bound).

Landed but not yet drivable

Eval CASES ship (14 selection/loading cases), but no runnable grading pass exists today. --provider rig is the live proof-contract door and is NOT YET DRIVEN — it says so itself and redirects to fake (the wiring is the convergence-test driver work in flight). --provider fake replays only transcripts supplied via --transcripts <map.json> and errors every case without one. When the live door is driven, the next release promotes this to a capability.

Behavior + Compatibility

  • Migrations — none in this release. Migration head stays at 071 (matches v0.5.2). Nothing to apply on a v0.5.2→v0.5.3 upgrade.
  • API surface preserved — no CLI-command or flag removals or renames from v0.5.2.
  • v0.5.3 contains v0.5.2 — one lineage, no divergence.

Known Limitations (5.4 backlog)

  • Reply-hint self-qualify — carried from 5.2; reply-hints on some cross-host messages address themselves via machine-ID rather than registered host name. Substitute the registered host name from rig host list. Fix in 5.4.
  • Eval grading pass — CASES ship; no runnable grading pass yet. Driven --provider rig lands in 5.4.
  • rig send --verify does not detect staged-unsent for multi-line sends toward Claude seats — carried from 5.2 backlog.
  • Claude transcripts thin under fullscreen upsell — carried from 5.2 backlog.
  • Plus internal debt items ledgered for maintenance.

See Also

Assets 2
Loading