Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

ContextForge External Dataplane — Wiki

This wiki captures durable project context and working preferences. Check this index at the start of a task to decide whether deeper context is needed, then follow only the links that are relevant.

Pages

FileWhat it covers
getting-started.mdFull docker stack, local cargo dev, cf-integration — commands and URIs
project.mdWhat the project is, goals, stakeholders, key modules, crate ownership, active work
preferences.mdWorking standards, code style, logging rules, branch naming, AI interaction preferences
architecture.mdCurrent middleware stack order, pipeline shape, module boundaries, state ownership, executor shapes
routing.mdStateless routing model: VirtualHost routing tables, per-request backend lifecycle, method quick reference, header forwarding, plugin hooks
mcp-capability-allocation.mdTentative ContextForge 2.0 target topology, ownership, state model, Phase 1-4 roadmap, and Phase 3 flows
failure-modes.mdHTTP/MCP/routing/backend/plugin failure table — exact HTTP codes and JSON-RPC errors
config.mdKey CLI flags, JWT claims, UserConfig shape, plugin config, telemetry debugging, startup validation, local observability stack
deployment.mdExternal-dataplane deployment checklist, health endpoint caveat, nginx routing, TLS choices, session affinity, Redis availability, image pinning
security.mdTrust boundaries among the control plane, built-in dataplane, and external dataplane; Origin/Host validation; transport security; secrets handling
performance.mdControl-plane Locust load runs, benchmark settings, and built-in-dataplane baseline
testing.mdWorkspace checks, in-repo integration tests, full-stack harness lanes, settings, and control-plane baseline

Quick orientation

  • Repo: contextforge-data-plane — the Rust ContextForge external dataplane.
  • Core invariant: the ContextForge external dataplane is pure routing logic. No IAM, UI, or metrics storage.
  • Protocol target: new external-dataplane behavior targets MCP 2026-07-28 over Streamable HTTP with server/discover and per-request client metadata. The remaining 2025-11-25/initialize paths are temporary compatibility coverage, not an expansion surface. Legacy SSE is outside the external dataplane.
  • Status convention: project, architecture, routing, and operations pages describe the current implementation. The page under Upcoming describes the tentative ContextForge 2.0 target and migration roadmap.
  • Architecture context: architecture.md — read before touching the hot path. Full wiki index above.
  • Validation gate: cargo fmt + cargo clippy + cargo nextest + cargo deny must be clean; CI also runs cargo shear. See preferences.md for by-change-type requirements.
  • System topology: client → nginx → [ContextForge built-in dataplane | ContextForge external dataplane | ContextForge control plane]; external-dataplane config flows from the control plane via dataplane_publisher.py → Redis → external dataplane. See project.md § System topology.