Skip to content

Latest commit

 

History

History
97 lines (76 loc) · 5.64 KB

File metadata and controls

97 lines (76 loc) · 5.64 KB

Read-Only Mode and Maintenance Window — 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.

Freeze writes quickly and communicate clearly during incidents, migrations, or index rebuilds. Keep retrieval online while protecting data integrity and user trust.

Open these first

Acceptance targets

  • All write endpoints return 423 or 503 with Retry-After
  • No production writes in storage audit during the window
  • Read paths healthy: error budget unaffected
  • Banner or Statuspage posted before and after with exact times
  • ΔS and λ trends flat during the window for read requests

60-second checklist

  1. Flip read-only flag
    Global feature flag read_only=true. Middleware blocks writes, tool calls that mutate state, and ingestion jobs.
  2. Communicate
    Post Statuspage and in-product banner with start and end times. Include contact and rollback plan.
  3. Queue writes
    Buffer allowed write intents to a durable queue with idempotency keys. Drop non-critical writes.
  4. Headers
    Write endpoints respond with Retry-After: <seconds> and a stable error code for clients to respect.
  5. Drains
    Stop background writers, disable compaction and long migrations during the window.

Minimal playbook

  • Scope: enumerate write surfaces including embeddings backfills, vector upserts, tool call side effects, KV mutations.
  • Guard: enforce in API gateway and service layer. Return machine-readable errors.
  • Observe: track blocked write count, queue depth, read latency, ΔS and λ.
  • End: re-enable writes, run a short soak, publish closure notice, then backfill the queued intents.

Common pitfalls → fix

  • A background job keeps writing
    → include job scheduler in the flag check and stop crons.
  • Clients spin on retries
    → add jittered backoff and a max-retry budget. See Retry Backoff.
  • Cached stale banners
    → set short TTL and purge caches on start and end.

Escalate

If read errors or ΔS spikes appear, extend the window and execute a limited Rollback & Fast Recovery.


🔗 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

Layer Page What it’s for
⭐ Proof WFGY Recognition Map External citations, integrations, and ecosystem proof
⚙️ Engine WFGY 1.0 Original PDF tension engine and early logic sketch (legacy reference)
⚙️ Engine WFGY 2.0 Production tension kernel for RAG and agent systems
⚙️ Engine WFGY 3.0 TXT based Singularity tension engine (131 S class set)
🗺️ Map Problem Map 1.0 Flagship 16 problem RAG failure taxonomy and fix map
🗺️ Map Problem Map 2.0 Global Debug Card for RAG and agent pipeline diagnosis
🗺️ Map Problem Map 3.0 Global AI troubleshooting atlas and failure pattern map
🧰 App TXT OS .txt semantic OS with fast bootstrap
🧰 App Blah Blah Blah Abstract and paradox Q&A built on TXT OS
🧰 App Blur Blur Blur Text to image generation with semantic control
🏡 Onboarding Starter Village Guided 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