apunkt/plano
1
0
Fork 0
mirror of https://github.com/katanemo/plano.git synced 2026-04-25 00:36:34 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

Improve clarity of routing and orchestration section

Browse source 
Reworded the section on routing and orchestration for clarity and conciseness.
This commit is contained in:
Salman Paracha 2025-08-29 09:50:03 -07:00 • committed by GitHub
parent dd4e6a7497
commit c698f2cba2
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -28,7 +28,7 @@ _Arch is a smart proxy server designed as a modular edge and AI gateway for agen
AI demos are easy to hack. But once you move past a prototype, you’re stuck building and maintaining low-level plumbing code that slows down real innovation. For example:
- **Routing & orchestration.** When routing logic lives in code, you’re stuck in one of two modes: either you write and maintain it yourself, or you inherit whatever a framework bakes in. In both cases, you must keep routing consistent across agents which means pushing code changes everywhere. Slowing down iteration, risks drift between deployments, and makes experimenting with new policies a refactor instead of a config flip.
- **Routing & orchestration.** Put routing in code and you’ve got two choices: maintain it yourself or live with a framework’s baked-in logic. Either way, keeping routing consistent means pushing code changes across all your agents and services, slowing iteration and turning every policy tweak into a refactor instead of a config flip.
- **Model integration churn.** Frameworks wire LLM integrations directly into code abstractions, making it hard to add or swap models without touching application code — meaning you’ll have to do codewide search/replace every time you want to experiment with a new model or version.
- **Observability & governance.** Logging, tracing, and guardrails are baked in as tightly coupled features, so bringing in best-of-breed solutions is painful and often requires digging through the guts of a framework.
- **Prompt engineering overhead**. Input validation, clarifying vague user input, and coercing outputs into the right schema all pile up, turning what should be design work into low-level plumbing work.