diff --git a/README.md b/README.md
index a701e0c..6db8363 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
Regenerate there; do not hand-edit the banner or badge URLs. -->
-[](https://github.com/lentago/shared-workflows/actions) [](https://github.com/lentago/shared-workflows/blob/main/LICENSE) [](https://deepwiki.com/lentago/shared-workflows) [](https://scorecard.dev/viewer/?uri=github.com/lentago/shared-workflows)
+[](https://github.com/lentago/shared-workflows/actions) [](https://github.com/lentago/shared-workflows/blob/main/LICENSE) [](https://scorecard.dev/viewer/?uri=github.com/lentago/shared-workflows)
  
@@ -22,22 +22,6 @@ the enterprise rhyme is a central pipeline library.
**Architecture decisions:** [`docs/adr/`](docs/adr/) records the reasoning behind this repo's structural choices — canonical policy placement, the `@main`→semver-tag migration, the advisory review gate, backwards-compatible contracts.
-## 📚 Ask this codebase (DeepWiki)
-
-
-
-> [DeepWiki](https://deepwiki.com/lentago/shared-workflows) maintains an AI-generated wiki over this
-> repository — architecture pages, diagrams, and a Q&A box grounded in the actual code. Every
-> public Lentago Labs repo is indexed ([deepwiki.com/lentago](https://deepwiki.com/lentago));
-> it is the fastest way to orient before reading source. It is AI-generated: trust it to orient
-> you, verify against the code before you act on it.
-
-**Good first questions:**
-
-- How does the `claude-responder.yml` workflow route between opus, sonnet, and haiku models, and who can trigger it?
-- What does `docs-check.yml` do differently from a simple link-checker, and why must callers omit the `paths:` filter?
-- Why is the Claude PR review in `claude-review.yml` advisory/non-blocking instead of a required status check?
-
## 🧭 What this repo demonstrates
Every row is a pattern you can lift into your own CI, with a link to where it
@@ -426,5 +410,4 @@ rules into `claude-review.yml`'s prompt as machine-checked review criteria.
> 🌱 **Lentago Labs** is a pro-bono operations practice for organizations that
> run on volunteers, donations, and one overworked tech person. Everything here
> is free to take, and we practice what we publish: our own estate runs this
-> way, in the open. Start at the [org profile](https://github.com/lentago), and
-> read this repo on [DeepWiki](https://deepwiki.com/lentago/shared-workflows).
+> way, in the open. Start at the [org profile](https://github.com/lentago).