Skip to content

fix: DC4 — add Architecture section #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ProtocolWarden merged 1 commit into from
May 8, 2026
Merged

fix: DC4 — add Architecture section #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,10 @@ ExecutorRuntime).

---

## Architecture

SwitchBoard is a thin policy boundary: requests come in, a lane is selected from `config/policy.yaml`, and an `ExecutionRequest` envelope routes downstream to the chosen runner. The lane catalog is fixed (see **Execution Lanes** below); cost/quality tradeoffs are config edits, not code changes. Configuration loads from `config/policy.yaml` + environment overlays — see the **Configuration** and **API** sections later for the full surface.

## Execution Lanes

| Lane | Runner | Auth | Cost |
Expand Down
Loading