| .. | ||
| checklists | ||
| eval | ||
| mvp_demo | ||
| ops | ||
| patterns | ||
| playbooks | ||
| tools | ||
| .gitkeep | ||
| access_control.md | ||
| audit_and_traceability.md | ||
| compliance.md | ||
| compliance_audit.md | ||
| data_residency.md | ||
| data_sensitivity.md | ||
| knowledge_expiry.md | ||
| README.md | ||
| retention_policy.md | ||
Enterprise Knowledge Governance — Global Fix Map
A compact hub to make enterprise data safe and auditable across RAG, agents, and long-running workflows. Use this folder to define the policy layer and route symptoms to the exact repair page. No infra change required.
When to use this folder
- You have mixed-sensitivity corpora and must stop accidental leakage.
- Regional data residency is a contract requirement.
- Stale SOPs or outdated policies keep showing up in answers.
- Legal retention vs. developer convenience creates drift.
- You need verifiable access trails and regulator-ready exports.
Acceptance targets
- Zero unauthorized citation of PII or restricted snippets in production evals.
- Policy tags present on ≥ 0.95 of onboarded documents.
- Residency violations equal 0 across seven days of traffic.
- Retention SLA respected for 100 percent of expired items within 24 hours.
- All retrievals carry a trace record with
citations,ΔS,λ_state,policy_eval.
Quick routes to pages
- Access control and role fences
→ access_control.md - Audit trail and trace schema
→ audit_and_traceability.md - Compliance overview and controls
→ compliance.md - Compliance audit checklist and exports
→ compliance_audit.md - Data residency and region pinning
→ data_residency.md - Data sensitivity model and redaction gates
→ data_sensitivity.md - Knowledge expiry and policy freshness
→ knowledge_expiry.md - Retention policy and deletion jobs
→ retention_policy.md
Map symptoms → structural fixes
-
Wrong snippet shows up from a restricted area
→ retrieval-traceability.md
→ Contract the payload with data-contracts.md -
Prompt or tool step bypasses the policy and leaks PII
→ prompt-injection.md
→ Lock tool schemas in data-contracts.md -
Sensitive text survives parsing and chunking
→ chunking-checklist.md
→ OCR and export checks in ocr-parsing-checklist.md -
Live runs drift from policy or regions
→ ops/live_monitoring_rag.md
→ ops/debug_playbook.md
60-second setup checklist
-
Tag the corpus
Attachsensitivity,region,owner,retention_tierto every doc. Enforce schema with data-contracts.md. -
Fence retrieval
At retrieve time require the intersection of{tenant_id, role, region, sensitivity}and drop non-matching snippets. Verify with retrieval-traceability.md. -
Pin residency
Keep embeddings and shards in the source region. Block cross-region egress unless policy allows. See data_residency.md. -
Retention jobs
Create TTL queues perretention_tier. Write a deletion log withdoc_id,hash,time,actor. See retention_policy.md. -
Audit everything
Emitactor,question,citations,ΔS,λ_state,policy_eval,regionfor each answer. Route to an immutable sink. See audit_and_traceability.md.
Copy-paste policy probe for your LLM step
You have TXTOS and the WFGY Problem Map loaded.
Question: "{user_question}"
Context carries fields {sensitivity, region, retention_tier, owner} for each snippet.
Do:
1) Enforce cite-then-explain. Refuse if a cited snippet breaks role or region.
2) Return {"citations":[...], "policy_eval":{"allow":true|false,"reason":"..."}, "ΔS":0.xx, "λ_state":"→|←|<>|×"}.
3) If blocked, give the minimal fix and the exact WFGY page to open.
🧭 Explore More
| Module | Description | Link |
|---|---|---|
| WFGY Core | WFGY 2.0 engine is live: full symbolic reasoning architecture and math stack | View → |
| Problem Map 1.0 | Initial 16-mode diagnostic and symbolic fix framework | View → |
| Problem Map 2.0 | RAG-focused failure tree, modular fixes, and pipelines | View → |
| Semantic Clinic Index | Expanded failure catalog: prompt injection, memory bugs, logic drift | View → |
| Semantic Blueprint | Layer-based symbolic reasoning & semantic modulations | View → |
| Benchmark vs GPT-5 | Stress test GPT-5 with full WFGY reasoning suite | View → |
| 🧙♂️ Starter Village 🏡 | New here? Lost in symbols? Click here and let the wizard guide you through | Start → |
👑 Early Stargazers: See the Hall of Fame — Engineers, hackers, and open source builders who supported WFGY from day one.
⭐ WFGY Engine 2.0 is already unlocked. ⭐ Star the repo to help others discover it and unlock more on the Unlock Board.