CONCEPT Cited by 1 source
Model-agnostic orchestration¶
The design principle of treating LLMs as interchangeable components within an orchestration pipeline rather than building tightly around a single model. The harness — not the model — is the durable artifact.
Definition¶
A model-agnostic orchestration layer: 1. Decouples pipeline logic from any specific model's API surface or behavioral quirks. 2. Allows models to be frequently interchanged and cross-tested — using one model for initial discovery and an entirely different one for validation. 3. Absorbs downstream provider volatility (temperature changes, caching policy, inference-effort budgets) without pipeline breakage.
The key insight: "developers who've built tightly around a single model have already experienced what happens when that model is no longer available or gets superseded by a more capable one" (Source: sources/2026-06-18-cloudflare-build-your-own-vulnerability-harness).
Seen in¶
- systems/cloudflare-vulnerability-discovery-harness / systems/cloudflare-vulnerability-validation-system — VDH uses one model, VVS uses a completely different model for adversarial cross-checking.
Related¶
- concepts/stateless-agent-compute — the complementary principle (model holds no state between invocations)
- patterns/model-as-interchangeable-component — the pattern form of this concept