WFGY/ProblemMap/GlobalFixMap/OpsDeploy/rollout_readiness_gate.md

9 KiB
Raw Blame History

Rollout Readiness Gate — OpsDeploy

🧭 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.

A pre-ship gate that decides ship or no-ship using measurable targets.
Use this page to wire a single checkpoint in CI or CD that blocks risky changes before they hit users.

What this page is

  • A compact, provider-agnostic checklist that verifies retrieval, reasoning, orchestration, and infra order.
  • Direct jumps to the exact Problem Map fixes.
  • Copy-paste templates you can drop into CI or a workflow runner.

When to use

  • Before any production rollout that changes retrievers, embeddings, chunkers, prompts, model versions, or tool schemas.
  • After index rebuilds, data migrations, or secret rotation.
  • When answers recently started flipping between runs or a canary looks unstable.

Open these first

Acceptance targets for ship

  • ΔS(question, retrieved) ≤ 0.45 on three paraphrases.
  • Coverage of target section ≥ 0.70.
  • λ remains convergent across two seeds.
  • E_resonance stays flat on long windows.
  • No schema drift in citation fields {snippet_id, section_id, source_url, offsets, tokens}.

60-second gate checklist

  1. Warmup and invariants

    • Secrets present. Version lock consistent. INDEX_HASH matches retriever build.
    • Boot order ok. See Bootstrap Ordering.
  2. RAG quality probe

  3. Hallucination fence

  4. Index and metric sanity

  5. Chain stability

  6. Decision

    • Ship if all targets pass on two seeds and three paraphrases.
    • Else block and open the linked fix page.

CI gate template you can paste

# opsdeploy/rollout_readiness_gate.yml
gates:
  warmup_invariants:
    checks:
      - secrets_present: true
      - index_hash_matches: true
      - version_lock: strict
      - boot_order_ok: true  # see Bootstrap Ordering
  rag_quality:
    evals:
      - name: rag_precision_recall
        spec: ProblemMap/eval/eval_rag_precision_recall.md
        min_coverage: 0.70
      - name: semantic_stability
        spec: ProblemMap/eval/eval_semantic_stability.md
        max_delta_s: 0.45
        paraphrases: 3
        seeds: 2
  hallucination_fence:
    schema: ProblemMap/data-contracts.md
    require_citations: true
  index_metric_sanity:
    actions_on_fail:
      - open: ProblemMap/embedding-vs-semantic.md
      - open: ProblemMap/patterns/pattern_query_parsing_split.md
      - open: ProblemMap/patterns/pattern_vectorstore_fragmentation.md
decision:
  on_fail: block_rollout
  on_pass: proceed_to_canary
artifacts:
  - logs/delta_s.json
  - logs/coverage.json
  - logs/lambda_states.json

Escalation map


🔗 Quick-Start Downloads (60 sec)

Tool Link 3-Step Setup
WFGY 1.0 PDF Engine Paper 1 Download · 2 Upload to your LLM · 3 Ask “Answer using WFGY + <your question>”
TXT OS (plain-text OS) TXTOS.txt 1 Download · 2 Paste into any LLM chat · 3 Type “hello world” — OS boots instantly

Explore More

Module Description Link
WFGY Core Canonical framework entry point View
Problem Map Diagnostic map and navigation hub View
Tension Universe Experiments MVP experiment field View
Recognition Where WFGY is referenced or adopted View
AI Guide Anti-hallucination reading protocol for tools View

If this repository helps, starring it improves discovery for other builders.
GitHub Repo stars