Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

History / integration guides ralph loop

Revisions

  • Reframe wiki: drop tier 7 from Ralph; rename Fleet Deployment to Consumer-Mode Deployment Two coordinated reframings of the integration documentation: 1. Drop "Tier 7" from the Ralph Loop page. The progressive tier ladder (1-6) is meant to be additive — each tier builds on the previous. Ralph doesn't fit that: it builds on Tier 4 (plugin) only and operates orthogonally to Tiers 5 and 6. Calling it Tier 7 implied a strict superset that doesn't exist. - Page title: "Tier 7: Autonomous Drain — Ralph Loop" → "Autonomous Drain — Ralph Loop" - Prerequisites no longer carry tier numbers - Integration-Guides.md split into two sections: * "Progressive Tiers" (1-6, the additive ladder) * "Specialized Patterns" (Ralph Loop, alternate operational mode) - Layering note rewritten to explain Ralph as alternate mode rather than next tier 2. Reframe "Fleet Deployment" as "Consumer-Mode Deployment". The doc covers Task Orchestrator's claim-mode consumer pattern, which scales from a single Ralph loop to a multi-tenant fleet. Framing it as fleet-only made it look inapplicable to single- actor deployments — but the same identity-verification, claim- ownership, and observability concerns apply at every scale. - Page title: "Fleet Deployment Guide" → "Consumer-Mode Deployment" - URL preserved as fleet-deployment for link stability (40+ codebase references plus external links). Note at top of page documents this. - Intro rewritten to explain the two patterns (orchestrator vs consumer) and the scale-agnostic primitives - New "Scope and Audience" section maps deployment scale to which sections to read (single Ralph → small team → fleet) - Section intros and bodies broadened: "agents" → "workers" where the noun applied to any consumer; "fleet" reserved for sections explicitly addressing multi-worker scale (Capacity Planning, etc.) - "Operating a Live Fleet" → "Operating a Live Deployment" with single-Ralph guidance interpolated - Cross-references updated in Home.md, _Sidebar.md, api-reference.md, workflow-guide.md, and the Ralph guide itself — display text reads "Consumer-Mode Deployment" but URL remains fleet-deployment - workflow-guide.md "agent implementers" callout updated to acknowledge Ralph as the bundled-plugin exception to the "default mode only" framing Codebase docs (current/docs/fleet-deployment.md, README, etc.) are intentionally not touched in this commit. They are paired project docs and can be reframed in a separate pass aligned with a release cadence if desired.

    @jpicklyk jpicklyk committed May 4, 2026
  • Add Tier 7: Autonomous Drain (Ralph Loop) integration guide Documents the Ralph-style queue drain pattern shipped in plugin PR #169 — the first claim-mode skill in the public plugin. Covers: - The four-artifact architecture (script driver, launcher skill, iteration prompt, dedicated output style) - Filter/bounds/model configuration with all CLI flags - Per-iteration lifecycle (claim → /schema-workflow → commit → RALPH_OUTCOME marker) - Outcomes and dual-axis circuit breakers (gate-failure + consecutive-error budgets) - Worktree lifecycle: pid+timestamp temp naming, post-iteration rename to UUID-based names, smart cleanup with --base-ref - Composition with /loop and with note schemas - When Ralph fits vs orchestrator mode (Tier 5) - Operational notes: bypassPermissions risk-bounding, signal forwarding, exit codes - Troubleshooting and design notes Also updates Integration-Guides.md (overview tier table + which- guide-is-right-for-me + layering note) and _Sidebar.md. Cross-references fleet-deployment.md since Ralph is the canonical client of the claim-mode contract.

    @jpicklyk jpicklyk committed May 4, 2026

AltStyle によって変換されたページ (->オリジナル) /