Agentic Devops Solar Ralph
No description available
Ask AI about Agentic Devops Solar Ralph
Powered by Claude Β· Grounded in docs
I know everything about Agentic Devops Solar Ralph. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
SOLAR-Ralph
Agentic AI should finish tasks autonomously. Most of the time, it doesn't.
Agents declare success too early. They start work with missing context and fail mid-way. They implement in the wrong direction for hours before you notice. They self-certify their own output. They lose all state when the session ends. And changing one agent breaks everything else.
SOLAR-Ralph is an installable harness for VS Code + GitHub Copilot that solves each of these with a structured five-layer protocol. One install command. No custom runtime. No vendor lock-in.
Why SOLAR-Ralph
| Pain Point | SOLAR Solution |
|---|---|
| Agent declares the task done before it actually is | Ralph Loop β declarative exit condition + adversarial gate required before TASK_COMPLETE is written |
| Agent starts implementing with missing context and fails mid-way | Material Gate β MATERIAL_INSUFFICIENT signal stops the governor before any specialist is delegated |
| Wrong direction: hours of code before you realize the agent misunderstood | Design Gate β user-approved plan must exist before any implementation agent runs |
| Can't trust AI output without independent verification | Adversarial Bystander β a non-author agent verifies at every write stage; bystander is a principle, not a named role |
| Session ends and the agent loses all progress | Ledger β sparse five-section restart-safe state anchor in .github/.ai_ledger.md; governor reads it cold |
| Swapping one agent breaks the whole team | Registry β every agent is a YAML block in AGENTS.md; swap by updating one entry |
The SOLAR Framework
| Layer | Role | Implementation | What It Does |
|---|---|---|---|
| S | Specialist | .github/agents/*.agent.md | Isolated domain experts dispatched in parallel; one failure does not block others |
| O | Orchestrator | .github/AGENTS.md | Pure event-driven governor; reads ledger stage, dispatches the right specialist |
| L | Ledger | .github/.ai_ledger.md | Restart-safe state anchor; five sections, Materials are links only |
| A | Adversarial | Review Auditors + Stop hook | Non-author verification before any write lands; bystander principle |
| R | Recursive | Ralph Loop + Stop hook | Bounded iteration with a declarative exit condition and iteration cap |
Quick Start
1. Install: Open solar-install.prompt.md in VS Code agent mode and follow the prompts.
2. Run your first task: Open #solar.prompt.md in Copilot Chat agent mode.
π Full setup guide
What Gets Installed
.github/agents/β 7 agents: Governor, Data Collector, Design Planning Architect, Implementation Specialist, Test Specialist, Docs Curator, Review Auditor.github/skills/β 7 skills: data-collection, design-planning, implementation, testing, doc-sync, review, recursive-remediation.github/hooks/β 2 hooks:post-tool-use(adversarial VERIFY signal) +stop(completion gate).github/prompts/β 2 prompts:solar.prompt.md(task entry) +solar-registry-update.prompt.md.github/AGENTS.mdβ Orchestration manifest: agent registry, skill index, hook config, ledger template.github/.ai_ledger.mdβ Persistent restart-safe state (Objective / Work Queue / Loop State / Materials / Decisions Log).github/solar.config.jsonβ 5 behavior flags:adversarial,learning,logging,human_approval,parallel_dispatch.github/solar-system/β Adversarial checklist, lifecycle protocols, handoff schemas
Everything is swappable. Add a specialist by dropping a new .agent.md file; attach a different skill to an existing agent the same way. No wiring changes anywhere else β run #solar-registry-update.prompt.md and the governor syncs the registry automatically.
