🧭 Quick Return to Map
You are in a sub-page of Governance.
To reorient, go back here:
- Governance — policy enforcement and compliance controls
- WFGY Global Fix Map — main Emergency Room, 300+ structured fixes
- WFGY Problem Map 1.0 — 16 reproducible failure modes
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 governance fix page for when data origin, transformation, and lineage are unclear or unverifiable.
Use this page when retrieval results cannot be traced back to their dataset source, or when provenance breaks across documents, chunks, embeddings, and answers.
- Retrieval output has no clear link back to its document or section.
- Embedding and chunk pipelines overwrite or drop provenance fields.
- Audit trail is incomplete across ingestion, index, and RAG responses.
- Approvals or waivers exist but cannot be joined to data versions.
- Multi-hop pipelines lose lineage across systems (ETL, embedding, vectorstore, orchestration).
- Every retrieved snippet includes
{doc_id, section_id, source_url, offsets, revision}. - Lineage fields survive across document → chunk → embedding → retriever → LLM.
- Audit joins can reconstruct provenance end-to-end with ≥ 0.95 coverage.
- ΔS(question, retrieved) ≤ 0.45 for governed outputs.
- Waivers and overrides include expiry and accountable owner.
-
Lost provenance in chunking
→ chunking-checklist.md
Ensure chunk metadata carriesdoc_id,section_id, and token offsets. -
Vector store overwrites or strips lineage fields
→ vectorstore-fragmentation.md
Enforce schema contracts on ingestion and retrieval layers. -
Answers cannot be tied back to original snippet
→ retrieval-traceability.md
Require cite-then-explain and enforce snippet ID propagation. -
Ambiguous approval or version skew
→ bootstrap-ordering.md,
→ predeploy-collapse.md -
Multi-system lineage gaps (ETL, embedding, RAG orchestration)
→ data-contracts.md
Contract schema ensures interoperability across steps.
- Ingest contracts — Every ETL pipeline attaches
doc_id,revision, andsource_url. - Chunk schema — Ensure token offsets and section boundaries are immutable.
- Embedding schema — Carry
embedding_id,doc_hash, andindex_hash. - Retriever response — Must include
snippet_id+ lineage fields, not just text. - LLM prompt contracts — Require cite-then-explain, forbid unlinked spans.
- Audit trail — Every approval and waiver linked to specific dataset version.
| 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 |
| 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.
