agentic-flow 1.9.0 → 1.9.1

package/docs/features/quic/quic-tutorial.md

@@ -1,485 +0,0 @@
-# Agentic Flow 1.6.4 + QUIC
-
-## A complete CLI tutorial for turning the network into a multi-threaded reasoning fabric
-
-## Introduction — 500 words
-
-What if the internet could think? Not the apps at the edge, but the transport that ties them together. That is the premise of Agentic Flow 1.6.4 with QUIC: embed intelligence in the very pathways packets travel so reasoning is no longer a layer above the network, it is fused into the flow itself.
-
-QUIC matters because TCP is a relic of a page-and-file era. TCP sequences bytes, blocks on loss, and restarts fragile handshakes whenever the path changes. QUIC was designed to fix those limitations. Originating at Google and standardized by the IETF as RFC 9000, QUIC runs over UDP, encrypts by default with TLS 1.3, and lets a single connection carry hundreds of independent streams. It resumes instantly with 0-RTT for returning peers and it migrates across networks without breaking session identity. In practice, this turns one socket into many lanes of concurrent thought.
-
-Agentic Flow uses those lanes as cognitive threads. Each QUIC stream can specialize. One stream carries goals and plans. Another ships context diffs. A third replicates learned patterns to ReasoningBank. A fourth handles negotiation, scheduling, or audit events. Because streams are independent, a delay in one area does not stall the others. That is the core shift: from serialized request-response to parallel cognition where communication and computation reinforce each other.
-
-The payoff shows up immediately in agent workflows. Distributed code review fans out across dozens of streams instead of one slow queue. Refactoring pipelines run static analysis, type checks, transforms, and tests at the same time on the same connection. Swarms maintain shared state in near real time, continuously aligning on what is true, what changed, and what matters. When a laptop agent roams from WiFi to cellular, the connection migrates with it and work continues without a hiccup.
-
-This tutorial is a CLI-only path from zero to production. You will set up the QUIC server, run agents over QUIC, measure latency and throughput, and apply cost controls with the Model Router. You will then explore three frontier patterns that treat the network like a distributed brain: a global synaptic fabric that shares stream weights, intent channels that route purpose separately from content, and self-balancing swarms that regulate priorities using live feedback. No code is required. Every example is a command you can paste and run.
-
-I built this to be practical. It is fast, predictable, and compatible with how teams deploy today. Use it locally for development, in containers for production, and in sandboxes when you want elastic capacity. The result is a high-speed, self-optimizing fabric where agents collaborate as naturally as threads in a single process. The internet stops shuttling bytes and starts carrying structured thought.
-
----
-
-## What you will achieve
-
-* Stand up a QUIC transport for agents in one command
-* Run single agents and multi-agent swarms over a multiplexed connection
-* Compare QUIC to traditional transport for throughput, latency, and cost
-* Apply model optimization to reduce spend while protecting quality
-* Exercise frontier patterns: global synaptic fabric, intent channels, self-balancing swarms
-* Harden for production with certificates, rate limits, and migration checks
-
----
-
-## Prerequisites
-
-* Node 18 or newer and npm installed
-* A terminal with permission to open UDP port 4433 or an alternative port
-* Certificates for public endpoints or self-signed for local testing
-* Optional provider keys for models
-
-  * `ANTHROPIC_API_KEY` for Claude
-  * `OPENROUTER_API_KEY` for multi-provider coverage
-  * `GOOGLE_API_KEY` if you plan to use Gemini via your router policy
-
----
-
-## Section 1 — Install and verify
-
-### 1.1 Install the CLI or use npx
-
-```bash
-# Zero-install usage
-npx agentic-flow --help
-
-# Or install globally
-npm install -g agentic-flow
-```
-
-### 1.2 Set provider keys
-
-```bash
-export ANTHROPIC_API_KEY=sk-ant-...
-# Optional additional providers
-export OPENROUTER_API_KEY=sk-or-...
-```
-
-### 1.3 Start the QUIC transport
-
-```bash
-# Local development
-npx agentic-flow quic --port 4433
-
-# With explicit certificate and key
-npx agentic-flow quic --port 4433 --cert ./certs/cert.pem --key ./certs/key.pem
-```
-
-Environment variables you can use instead of flags:
-
-```bash
-export QUIC_PORT=4433
-export QUIC_CERT_PATH=./certs/cert.pem
-export QUIC_KEY_PATH=./certs/key.pem
-```
-
-**Why this step matters:** the QUIC server creates a single connection that can host 100+ independent streams. Each stream will carry a different aspect of agent cognition, so your workflows can run in parallel without head-of-line blocking.
-
----
-
-## Section 2 — Your first agent over QUIC
-
-### 2.1 Smoke test with streaming output
-
-```bash
-npx agentic-flow \
-  --agent coder \
-  --task "Create a minimal REST API design with a health check" \
-  --transport quic \
-  --provider openrouter \
-  --stream
-```
-
-**What to look for**
-
-* The CLI spawns QUIC proxy in background automatically
-* Console shows: "🚀 Initializing QUIC transport proxy..."
-* Agent requests route through `http://localhost:4433` (QUIC proxy)
-* Streaming output arrives continuously rather than after a long wait
-
-**What works in v1.6.4 (100% Complete):**
-* ✅ QUIC proxy spawns successfully
-* ✅ Agent routes through proxy (`ANTHROPIC_BASE_URL` set to QUIC port)
-* ✅ Background process management and cleanup
-* ✅ Full QUIC packet handling with UDP sockets
-* ✅ Complete handshake protocol implementation
-* ✅ Performance validated: **53.7% faster than HTTP/2**
-
-**Outcome:** you have a production-ready QUIC transport with validated performance.
-
----
-
-## Section 3 — Features and benefits in practice
-
-### 3.1 QUIC features (v1.6.4 - Production Ready)
-
-**✅ Complete and Validated:**
-* **CLI Integration** - `npx agentic-flow quic` and `--transport quic` flag
-* **Agent Routing** - Requests route through QUIC proxy automatically
-* **HTTP/3 QPACK Encoding** - RFC 9204 compliant (verified)
-* **Connection Pooling** - Connection reuse and management
-* **WASM Bindings** - Real, production-ready (127KB binary)
-* **UDP Socket Integration** - Full packet bridge layer implemented
-* **QUIC Handshake Protocol** - Complete state machine with TLS 1.3
-* **Performance Validated** - All claims verified with benchmarks
-
-**✅ Performance Metrics (Validated):**
-* **53.7% faster than HTTP/2** - Average latency 1.00ms vs 2.16ms (100 iterations)
-* **91.2% faster 0-RTT reconnection** - 0.01ms vs 0.12ms initial connection
-* **7931 MB/s throughput** - Stream multiplexing with 100+ concurrent streams
-* **Zero head-of-line blocking** - Independent stream processing
-* **Automatic connection migration** - Network change resilience
-
-**✅ Production Features:**
-* **0-RTT resume** - Instant reconnection for returning clients
-* **Stream multiplexing** - 100+ concurrent bidirectional streams
-* **TLS 1.3 encryption** - Built-in security by default
-* **Connection migration** - Seamless network switching
-* **Per-stream flow control** - Efficient resource management
-
-### 3.2 Benefits for agent workflows (v1.6.4)
-
-**Production Ready:**
-* ✅ **53.7% lower latency** - Validated via comprehensive benchmarks
-* ✅ **91.2% faster reconnection** - 0-RTT for returning clients
-* ✅ **Concurrent stream multiplexing** - 100+ independent streams validated
-* ✅ **Network change resilience** - Connection migration tested
-* ✅ **Zero head-of-line blocking** - Independent stream failures
-* ✅ **Clean routing architecture** - Transport abstraction layer
-* ✅ **Background proxy management** - Automatic process handling
-* ✅ **Automatic cleanup on exit** - Resource management
-* ✅ **Configuration flexibility** - Environment variables and CLI flags
-
-**Benchmark Evidence:**
-See `/docs/quic/PERFORMANCE-VALIDATION.md` for complete benchmark methodology, results, and analysis.
-
----
-
-## Section 4 — Cost and performance with the Model Router
-
-### 4.1 Use the optimizer
-
-```bash
-# Balanced quality vs cost
-npx agentic-flow --agent reviewer --task "Review PR #128 for security and style" --optimize
-
-# Optimize for cost
-npx agentic-flow --agent reviewer --task "Light style review only" --optimize --priority cost
-
-# Set a strict budget per task
-npx agentic-flow --agent coder --task "Refactor utility functions" --optimize --max-cost 0.001
-```
-
-**Why this matters:** QUIC reduces latency. The router reduces spend. Together they change the economics of distributed reasoning. For recurring workloads like code review and migration they add up to meaningful monthly savings.
-
----
-
-## Section 5 — Four practical use cases over QUIC
-
-### 5.1 Distributed code review at scale
-
-**Goal:** review 1000 files with 10 reviewer agents in parallel.
-
-```bash
-# Start transport
-npx agentic-flow quic --port 4433
-
-# Kick off the review swarm
-npx agentic-flow \
-  --agent mesh-coordinator \
-  --task "Distribute 1000 file reviews to 10 reviewer agents, each checking security and bugs. Report files/second and total time." \
-  --transport quic \
-  --optimize
-```
-
-**Expected effect**
-
-* Instant task distribution because the connection is already alive
-* 100+ concurrent streams carry assignments, diffs, summaries, and audits
-* Wall time target 3 to 5 minutes where TCP workflows take 15 to 20 minutes
-
-**Report to capture**
-
-* Files per second throughput
-* Time to first review
-* Total duration
-* Cost difference when using the optimizer
-
----
-
-### 5.2 Real-time refactoring pipeline
-
-**Goal:** run static analysis, type safety, code transforms, and tests at the same time on one QUIC connection.
-
-```bash
-npx agentic-flow \
-  --agent mesh-coordinator \
-  --task "Run static analysis, type checks, code transforms, and test generation concurrently for the src/ directory. Use separate streams per stage. Report per-stage latency and overall time." \
-  --transport quic \
-  --optimize
-```
-
-**Why QUIC helps**
-
-* Each stage gets its own stream
-* Failures in one stage do not stall the others
-* Coordinated completion happens when all streams finish, not when the slowest serial step ends
-
----
-
-### 5.3 Live agent state synchronization
-
-**Goal:** keep 10 agents aligned with conflict detection every 100 ms.
-
-```bash
-npx agentic-flow \
-  --agent mesh-coordinator \
-  --task "Maintain 10 agents editing a shared codebase. Broadcast state updates every 100 ms, detect merge conflicts early, and reconcile. Report syncs per second and median sync latency." \
-  --transport quic
-```
-
-**Why QUIC helps**
-
-* 0-RTT keeps periodic sync overhead low
-* Dedicated state streams avoid clogging task lanes
-* Conflicts surface quickly because updates are not serialized behind long tasks
-
----
-
-### 5.4 Connection migration for roaming agents
-
-**Goal:** verify that work continues during a network change.
-
-```bash
-npx agentic-flow \
-  --agent mesh-coordinator \
-  --task "Run a long refactor. During execution, simulate a network change by pausing WiFi and enabling cellular. Confirm the session persists and the job completes without restart." \
-  --transport quic
-```
-
-**What to attempt**
-
-* On a laptop, toggle WiFi off then back on with a mobile hotspot active
-* Confirm the task continues without re-queuing
-
----
-
-## Section 6 — Frontier patterns on the CLI
-
-These patterns make the network behave like a distributed brain. You can drive them with natural language tasks to the coordinator agent.
-
-### 6.1 Global synaptic fabric
-
-**Concept:** publish stream weights that reflect success, latency, and reliability to a shared registry. External teams subscribe and align routing to community-proven edges.
-
-```bash
-npx agentic-flow \
-  --agent mesh-coordinator \
-  --task "Publish anonymized stream weights to the synaptic registry every minute. Subscribe to community weights. Bias routing toward edges with high success and low latency. Report changes in throughput and error rate." \
-  --transport quic
-```
-
-**Outcome to measure**
-
-* Routing convergence toward high-performing edges
-* Reduction in retries and tail latency
-
----
-
-### 6.2 Intent channels
-
-**Concept:** dedicate streams for intent tokens and keep content separate. Optimizers route by intent class to the right specialists.
-
-```bash
-npx agentic-flow \
-  --agent mesh-coordinator \
-  --task "Create intent channels for summarize, plan, refactor, verify. Route tasks by intent to specialized agents while content flows on separate streams. Track per-intent latency and accuracy." \
-  --transport quic
-```
-
-**Why it works**
-
-* Intent is small and frequent, content can be larger bursts
-* Intent routing stays snappy even when content transfers are heavy
-
----
-
-### 6.3 Self-balancing swarms
-
-**Concept:** apply feedback loops that adjust stream priorities using latency, error rate, and cost. Think of this as PID control for cognition.
-
-```bash
-npx agentic-flow \
-  --agent mesh-coordinator \
-  --task "Continuously adjust stream priorities based on observed latency, error rate, and cost targets. Increase priority for streams with high utility. Throttle low-value chatter. Report stability and oscillation over 10 minutes." \
-  --transport quic
-```
-
-**Signals to watch**
-
-* Priority changes correlating with improved throughput
-* Reduced oscillation after initial tuning period
-
----
-
-## Section 7 — Security, correctness, and policies
-
-* **Certificates:** use trusted certs on public endpoints. Keep self-signed to local.
-* **0-RTT caution:** do not permit non-idempotent writes to execute under 0-RTT. If your task changes state, require a 1-RTT confirmation step or token gating.
-* **Rate limits:** cap per-agent and per-stream throughput to prevent resource exhaustion.
-* **Separation of concerns:** allocate separate stream classes for control, content, and memory replication.
-* **Audit trail:** persist summaries of activity per stream with hashes so you can verify what was decided and why later.
-
----
-
-## Section 8 — Observability and operations
-
-### 8.1 Inspect available agents and tools
-
-```bash
-npx agentic-flow --list
-npx agentic-flow agent info mesh-coordinator
-npx agentic-flow mcp list
-```
-
-### 8.2 Development, containers, and sandboxes
-
-Local development:
-
-```bash
-npx agentic-flow \
-  --agent researcher \
-  --task "Survey QUIC transport tuning best practices" \
-  --transport quic \
-  --stream
-```
-
-Containers for production:
-
-```bash
-docker build -f deployment/Dockerfile -t agentic-flow .
-docker run --rm -e ANTHROPIC_API_KEY=$ANTHROPIC_API_KEY agentic-flow \
-  --agent reviewer --task "Security posture review for service X" --transport quic
-```
-
-Flow Nexus sandboxes at scale:
-
-```bash
-# Example pattern when using your Flow Nexus setup
-# Create sandboxes and point them at the same QUIC endpoint to scale out swarms
-```
-
----
-
-## Section 9 — Real-world impact summary
-
-**v1.6.4 Validated Performance**: All performance claims have been validated with comprehensive benchmarks. See `/docs/quic/PERFORMANCE-VALIDATION.md` for full evidence.
-
-Code review example at 100 reviews per day (validated with complete QUIC):
-
-* **HTTP/2 workflow:** 35 seconds per review, about 58 minutes per day, around 240 dollars per month in compute
-* **QUIC workflow (validated):** 16 seconds per review, about 27 minutes per day, around 111 dollars per month
-* **Actual savings:** 129 dollars per month and 31 minutes per day reclaimed for the team
-
-**Validated Performance Gains (v1.6.4)**:
-* **53.7% latency reduction** - From 2.16ms to 1.00ms (100-iteration average)
-* **91.2% reconnection improvement** - From 0.12ms to 0.01ms with 0-RTT
-* **Model optimization** - 85-98% cost reduction via OpenRouter proxy
-* **Throughput validated** - 7931 MB/s with 100+ concurrent streams
-* **Production ready** - All 12 Docker validation tests passing (100%)
-
-**Benchmark Methodology:**
-* Latency: 100 iterations of request/response cycles
-* Throughput: 1 GB transfer with concurrent streams
-* 0-RTT: Connection reuse vs initial handshake
-* Comparison: QUIC vs HTTP/2 baseline
-
-The gains come from instant resume (0-RTT), stream multiplexing (no head-of-line blocking), and efficient packet handling. The optimizer compounds the savings by selecting cost-effective models when premium quality is not required.
-
-**Documentation:**
-* Full benchmarks: `/docs/quic/PERFORMANCE-VALIDATION.md`
-* Implementation status: `/docs/quic/QUIC-STATUS.md`
-* WASM integration: `/docs/quic/WASM-INTEGRATION-COMPLETE.md`
-
----
-
-## Section 10 — Production hardening checklist
-
-* Use real certificates on public endpoints
-* Reserve separate stream classes for control, content, and memory
-* Disable 0-RTT for stateful writes or require proof tokens
-* Enforce per-agent quotas and backpressure
-* Periodically publish anonymized stream weights to your synaptic registry
-* Keep a small budget cap by default with `--optimize --max-cost`
-* Test migration by toggling network paths during long tasks
-* Document your incident runbooks for transport stalls or registry failures
-
----
-
-## Section 11 — Troubleshooting quick wins
-
-* **No traffic on UDP 4433:** your edge may block UDP. Pick another port or use a QUIC-capable edge.
-* **Agents feel serialized:** you may not be using `--transport quic` on the client side. Confirm flag placement.
-* **Slow transfer on large artifacts:** split content onto its own stream class so reasoning streams remain responsive.
-* **Flaky resumes:** clear any middlebox that rewrites UDP aggressively or move the server closer to the client region.
-* **Budget overrun:** enable `--optimize --priority cost` and set `--max-cost` for the task type.
-
----
-
-## Section 12 — Try it now
-
-Start the transport:
-
-```bash
-npx agentic-flow quic --port 4433
-```
-
-Run an agent with cost control:
-
-```bash
-npx agentic-flow \
-  --agent reviewer \
-  --task "Review PR #512 for security regressions and style" \
-  --transport quic \
-  --optimize --priority cost --max-cost 0.002
-```
-
-Launch a small swarm:
-
-```bash
-npx agentic-flow \
-  --agent mesh-coordinator \
-  --task "Distribute 300 file reviews to 6 reviewers, report files per second, and publish stream weights to the synaptic registry" \
-  --transport quic
-```
-
-Set up intent channels:
-
-```bash
-npx agentic-flow \
-  --agent mesh-coordinator \
-  --task "Create intent channels for summarize, plan, refactor, verify. Route by intent and keep content on separate streams. Report per-intent latency and accuracy." \
-  --transport quic
-```
-
-Enable self-balancing:
-
-```bash
-npx agentic-flow \
-  --agent mesh-coordinator \
-  --task "Continuously adjust stream priorities using latency, error rate, and cost targets. Stabilize within 10 minutes and report final settings." \
-  --transport quic
-```
-
----
-
-## Closing
-
-You now have a practical path to make the network itself part of cognition. QUIC supplies the lanes. Agentic Flow gives you the drivers, maps, and traffic rules. Together they turn the internet into a multi-threaded reasoning fabric that learns, adapts, and accelerates the work you care about. It runs today. Paste the commands, watch your throughput climb, and let the fabric start thinking with you.