☢️ Ralph is now one supervisor and one mutating agent. ☢️

radioactive-ralph radioactive-ralph radioactive-ralph
/
  • Get started
  • Guides
    • Supervisor and client
    • TUI
    • Desktop GUI
    • Plan format
    • Safety floors
    • Architecture
    • Recording
    • Replaying
    • When to re-record
    • Where cassettes live
    • Writing a new test with a cassette
    • Design
    • Launch Plan — radioactive-ralph
    • Demo — Ralph in Action
  • Runbooks
    • 1a. Homebrew (macOS, Linux, WSL2 + Linuxbrew)
    • 1b. Scoop (Windows)
    • 1c. curl installer (macOS, Linux, WSL2)
    • 2. Verify your environment
    • 3. Start the supervisor
    • 4. Register a project
    • 5. Run the client
    • When something goes wrong
    • Claude (Anthropic)
    • Codex (OpenAI)
    • OpenCode
    • Verify end-to-end
    • service install vs. running –supervisor directly
    • 1. Install as an OS service
    • 2. Status, list, uninstall
    • 3. Logs
    • 4. Stale state recovery
    • When something goes wrong
    • Stale heartbeat
    • Dead socket or pipe
    • Provider CLI missing or unauthenticated
    • Service-install errors
    • Worker stuck / no progress
    • When everything else fails
    • macOS (launchd)
    • Linux (systemd –user)
    • Windows
    • WSL2
    • Docker / containers
  • Launch
    • Release Checklist
  • Design
    • Provider contract
    • Declarative provider bindings
    • Config virtual layers
    • Orchestrator-verified completion and A2A
  • Reference
    • Architecture
    • State
    • Testing — radioactive-ralph
  • Organization
    • radioactive_ralph
    • a2a
    • agent
    • agentdetect
    • doctor
    • genesis
    • gui
    • ipc
    • onboard
    • orch
    • plan
    • provider
    • claudesession
    • cassette
    • replayer
    • fakeclaude
    • rlog
    • service
    • statusbucket
    • store
    • schema
    • supervisor
    • tui
    • vconfig
    • xdg
  1. radioactive-ralph /
  2. Design
View as Markdown Open in ChatGPT Open in Claude

Design#

Contract-level documentation for the parts of the runtime that callers depend on.

Page

Contract

Provider contract

Capability records, stateful vs. stateless, resolution and validation

Declarative provider bindings

Config-only provider onboarding for compatible CLI framings

Config virtual layers

USER/PROJECTS layering, changes vs. overrides, conflict diffing

Orchestrator-verified completion and A2A

Why a worker never marks its own work done, and the A2A vocabulary that carries evidence

Previous
Release Checklist
Next
Provider contract

2026, Jon Bogaty

Made with Sphinx and Shibuya theme.