WFGY/ProblemMap/GlobalFixMap/Enterprise_Knowledge_Gov/access_control.md

Access Control — Enterprise Knowledge Governance

🧭 Quick Return to Map

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

• Enterprise_Knowledge_Gov — corporate knowledge management and governance
• 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.

Guardrails and fix patterns to ensure that enterprise knowledge bases are segmented, secured, and retrievable without silent leaks. Use this page when failures look like “permissions bug” but root cause is schema drift, missing contracts, or evaluation blind spots.

---

When to use this page

• Agents or LLMs retrieve snippets that a user role should not see.
• Answers omit key passages even though data is present in the KB.
• Knowledge base permissions collapse after re-index or migration.
• Citation shows content from a restricted section without a trace.
• External connectors expose more fields than expected.

---

Core acceptance targets

• ΔS(question, retrieved) ≤ 0.45, with access role enforced.
• Coverage ≥ 0.70 for the allowed scope, and <0.05 for disallowed scope.
• λ remains convergent across three paraphrases and two seeds.
• All snippets carry explicit role_scope, section_id, and source_hash.

---

Typical access problems → exact fix

Symptom	Likely cause	Open this
Leaked restricted snippet	Missing role tag or weak contract	data-contracts.md, retrieval-traceability.md
Role upgrade not reflected	Cache or index skew	bootstrap-ordering.md, deployment-deadlock.md
Over-blocking (user sees nothing)	Schema mismatch or λ collapse	logic-collapse.md
Citations missing access tag	Parser or contract drift	ocr-parsing-checklist.md, data-contracts.md

---

Fix in 60 seconds

1. Measure ΔS for the retrieved vs allowed anchor.
2. Check role_scope — ensure every snippet has an explicit scope.
3. Rebuild contract — enforce schema: {snippet_id, section_id, role_scope, hash}.
4. Re-index if role tags missing, with explicit normalization.
5. Verify λ stability across paraphrases with access role locked.

---

Copy-paste schema (YAML)

snippet_id: "KB-12345"
section_id: "SEC-42"
role_scope: "finance_analyst"
source_hash: "sha256:..."
text: "..."

Every snippet must carry these fields, and retrieval probes must validate them before citation.

---

Escalate when

• ΔS remains ≥ 0.60 even with contracts enforced.
• Citations show cross-scope bleed.
• Index mismatch recurs after two re-indexes.

Escalation path: rebuild with chunking-checklist.md and validate via eval_rag_precision_recall.md.

---

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.