Shadow Traffic Mirroring

March 6, 2026 · View on GitHub

🧭 Quick Return to Map

You are in a sub-page of OpsDeploy.
To reorient, go back here:

Think of this page as a desk within a ward.
If you need the full triage and all prescriptions, return to the Emergency Room lobby.

Safely mirror real production requests to a new model or service without affecting users. Use this page to validate output drift, latency, rate limits, and side-effect isolation before any canary or switchover.

Open these first

Acceptance targets

  • ΔS(prod_answer, shadow_answer) ≤ 0.45 on three paraphrases
  • λ remains convergent across two seeds
  • P99 added latency from mirroring ≤ 5 percent of end-to-end
  • Zero side effects from shadow path: writes blocked or redirected
  • Sampling accuracy within ±2 percent of configured shadow ratio

60-second checklist

  1. Mirror only reads
    Route the same request payload to the shadow service. Strip tokens and secrets not required for read paths. Block tool calls and any writes.
  2. Tag and store
    Append shadow_id, req_hash, model_rev, index_hash. Persist both prod and shadow outputs with ΔS and λ.
  3. Throttles
    Apply a hard cap on mirror QPS. Respect provider limits. Enable backpressure guards.
  4. Drift gates
    Alert when mean ΔS exceeds 0.45 or when λ flips on harmless paraphrases.

Minimal playbook

  • Ingress: duplicate the request at the edge or gateway. Never await the shadow response on the user path.
  • Sanitize: remove side-effect headers, redact PII fields that the shadow does not need.
  • Observe: log ΔS, λ_state, shadow_latency_ms, HTTP codes, rate-limit headers.
  • Compare: evaluate citation alignment with Retrieval Traceability and snippet schema from Data Contracts.
  • Decide: graduate to canary if drift stays within target for 24 hours and error budget is untouched.

Common pitfalls → fix

Escalate

Promote to Staged Canary when drift and error rates meet targets for a full diurnal cycle and shadow P95 latency increase is under 3 percent.


🔗 Quick-Start Downloads (60 sec)

ToolLink3-Step Setup
WFGY 1.0 PDFEngine Paper1️⃣ Download · 2️⃣ Upload to your LLM · 3️⃣ Ask “Answer using WFGY + <your question>”
TXT OS (plain-text OS)TXTOS.txt1️⃣ Download · 2️⃣ Paste into any LLM chat · 3️⃣ Type “hello world” — OS boots instantly

Explore More

LayerPageWhat it’s for
⭐ ProofWFGY Recognition MapExternal citations, integrations, and ecosystem proof
⚙️ EngineWFGY 1.0Original PDF tension engine and early logic sketch (legacy reference)
⚙️ EngineWFGY 2.0Production tension kernel for RAG and agent systems
⚙️ EngineWFGY 3.0TXT based Singularity tension engine (131 S class set)
🗺️ MapProblem Map 1.0Flagship 16 problem RAG failure taxonomy and fix map
🗺️ MapProblem Map 2.0Global Debug Card for RAG and agent pipeline diagnosis
🗺️ MapProblem Map 3.0Global AI troubleshooting atlas and failure pattern map
🧰 AppTXT OS.txt semantic OS with fast bootstrap
🧰 AppBlah Blah BlahAbstract and paradox Q&A built on TXT OS
🧰 AppBlur Blur BlurText to image generation with semantic control
🏡 OnboardingStarter VillageGuided entry point for new users

If this repository helped, starring it improves discovery so more builders can find the docs and tools.
GitHub Repo stars