Composable, MCP-native toolkits for audio, video, and text processing. Build pipelines. Not monoliths.
The governance meta-repository for the reverberage ecosystem.
The hub is three things:
- Governance platform — the single source of truth for the satellite protocol, architecture decisions, and roadmap
- Orchestration platform — AI-assisted development tooling (Spec-Driven Development pipeline, agents, skills, judgment-day review)
- Satellite protocol — the contract every reverberage satellite follows: build, package, naming, and MCP conventions
This is not a runtime project. The hub contains no application code. Satellites are separate, independently installable Python packages.
Each satellite is an independent pip install-able Python package — usable alone or composed into pipelines.
| Satellite | Package | Status |
|---|---|---|
| transcriber | rvrb-transcriber |
 |
| verify | rvrb-verify |
|
| transform | rvrb-transform |
|
See the roadmap for planned satellites.
Satellites compose via Unix pipelines — each writes to stdout, text-consuming satellites read from stdin.
# Transcribe a meeting, verify the claims in the transcript
rvrb-transcriber meeting.mp3 | rvrb-verify
# Full audit trail: transcribe → JSON → verify with a specific model
rvrb-transcriber audio.mp3 | rvrb-verify --model qwen3.7-plus
# Three-satellite chain: transcribe → verify → transform
rvrb-transcriber meeting.mp3 | rvrb-verify | rvrb-transform "format as meeting minutes"
# Transform with JSON output
rvrb-transform "summarize" "The quick brown fox jumps over the lazy dog" --jsonFor programmatic composition, see the Satellite Protocol v2
(MediaInput/MediaOutput API).
- Each satellite does one thing. Audio in, text out. Claim in, verdict out.
- Each satellite is independently usable — no monolith, no framework lock-in.
- Each satellite can connect to any MCP-compatible agentic system.
- The hub exists to make satellites easy to build, consistent to use, and fast to compose.
- Read the Satellite Protocol
- Scaffold a new satellite:
/new-satellite <name> - Run the SDD pipeline for changes:
/sdd-new <change description> - See CONTRIBUTING.md for full details
| Doc | Description |
|---|---|
| Satellite Protocol | Build, package, and naming conventions |
| Satellite Protocol v2 | Media I/O types, provider contract, engine spec |
| Architecture | Hub/satellite model and composition patterns |
| Roadmap | Shipped satellites and planned priorities |
Apache-2.0 © Juan Manuel Daza