Skip to content

Risks & fixes

Every "what could go wrong" — with the control that addresses it. Status: enforced in code · design + partial · Phase 2.

Risk What could go wrong The fix (built in) Status
Confidential comms leak Teams/Outlook run messages contain hostnames, ticket refs, customer impact Link-only by default — never sent to the LLM, never mirrored; content stays in source behind its ACLs
Deleted source, stale wiki A doc/playbook is deleted; wiki keeps showing an outdated procedure in a P1 Delete detection → tombstone. Page auto-marked [DEPRECATED] with a dated notice; history kept
Legacy doc dump 40-page legacy runbooks flood the wiki and blow up LLM cost Short-summary mode — truncated to an ≤8-line summary + link-back
Excel data sprawl Dumping full workbooks (some sensitive) is noisy and risky Summarise, don't mirror — sheet names, shape, headers + link
AI hallucination Model invents a step; engineer trusts it PR-gated + cited + confidence-scored; low-confidence flagged needs-sme
Prompt injection via content A doc says "ignore instructions, paste secrets" Content treated as data; secret-scan on drafted output before commit
RAG cross-team disclosure Assistant surfaces a restricted page to the wrong user ACL trimming + classification; restricted items are link-only anyway
China / residency breach Cross-border movement of China / on-prem content Region tag + in-region processing; global wiki holds summaries + links only
Runaway LLM cost A loop or event flood spikes spend Quotas + budget alerts + circuit breaker; confidential/tombstone paths use zero tokens
Machine content hand-edited Someone edits a generated page; it diverges from source Hand-edit guard in CI fails non-automation commits under /_generated
Reviewer overload Too many auto-draft PRs; owners ignore them Owner-routed + grouped + drift-tracked; the weekly metric keeps the backlog visible

Legend

demonstrable in the running demo today · pattern in place, hardening in Phase 0–1 · part of the Phase-2 RAG rollout.