Agent Platform: Inference Broker — Python module, not LangGraph

LangGraph only appears on the site as a stack label; introducing it as
a first-class extension concept here only would be inconsistent. Using
"hot-pluggable Python module" instead keeps the vocabulary consistent.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: rmdevpro

open-source/agent-platform.html

@@ -171,7 +171,7 @@ <h2>How they fit.</h2>
       <h2>Coming next.</h2>
       <p>Additional agentic services on the roadmap, designed to extend the platform. Concept-stage or early build, not yet shipping.</p>
       <ul>
-        <li><b>Inference Broker</b> — a single proxy in front of every model call across the ecosystem, local or cloud. Clients invoke a named alias; the alias either points straight at a specific model, or runs through a hot-pluggable LangGraph that can do whatever the author wires it to do. Typical patterns include rate-limit fallback, size-based local-vs-cloud routing, format reshaping between providers (OpenAI → Anthropic), and content-aware dispatch (code authoring to one model, code testing to another) — but because each alias is a real graph, the range is open. Like the Context Broker, its Imperator can metacode new aliases and graph plugins.</li>
+        <li><b>Inference Broker</b> — a single proxy in front of every model call across the ecosystem, local or cloud. Clients invoke a named alias; the alias either points straight at a specific model, or runs through a hot-pluggable Python module that can do whatever the author wires it to do. Typical patterns include rate-limit fallback, size-based local-vs-cloud routing, format reshaping between providers (OpenAI → Anthropic), and content-aware dispatch (code authoring to one model, code testing to another) — but because each alias is real code, the range is open. Like the Context Broker, its Imperator can metacode new aliases and plugins.</li>
         <li><b>Conversation Broker</b> — agent-to-agent messaging on an email-style model: addressed communication, threading, participant history, delivery notification, loop protection. Internal, controlled, no SMTP required.</li>
         <li><b>Agentic File System</b> — intent-based filesystem management. Replaces POSIX permissions with a reconciliation between policy intent and action intent. Every mutation carries a stated reason; policies are expressed in terms of purpose, not just path patterns.</li>
         <li><b>Development Cache</b> — a shared cache for agentic development work.</li>