diff --git a/docs/SELF_SERVE_AI_DISCOVERABILITY_CONCEPT.md b/docs/SELF_SERVE_AI_DISCOVERABILITY_CONCEPT.md
index a64be3e..aab7bfb 100644
--- a/docs/SELF_SERVE_AI_DISCOVERABILITY_CONCEPT.md
+++ b/docs/SELF_SERVE_AI_DISCOVERABILITY_CONCEPT.md
@@ -87,6 +87,30 @@ Business verification is the tax. Every platform re-verifies **independently**.
 
 A white-label correction service that **holds verified status per platform** — and files on the owner’s behalf without re-uploading a lease five times — is what makes corrections **stick**. That held, multi-platform verified status is the **moat**: the audit finds the drift; the ticket files the fix; the held verification is why the fix does not get stomped again tomorrow.
 
+#### 3. Two lanes, then a ranked remediation stack
+
+Umbrella aggregators and end-user platforms are **not** the same job. Architecture needs **two lanes**:
+
+- **Lane A — umbrella submissions.** Write once into Data Axle, Localeze / TransUnion, and Foursquare’s place graph so long-tail directories, libraries, and many nav / GPS consumers stop regenerating stale NAP.
+- **Lane B — per-platform tickets.** Claim or suggest-edit on Google, Apple, Bing, Yelp, and other surfaces that keep their **own** databases and often prefer verified owner data over a feed.
+
+Umbrella-only leaves the Core 3 and Yelp wrong. Platform-only leaves the black box regenerating from Layer 1 feeds. Both lanes mint the same ticket shape (field, wrong value, right value, GBP or claimed truth as proof). Rank below is **most → least important** for small-business local discoverability and for how hard a miss should hit the Presence / audit score. This is what we have to architect — not a shipped checklist.
+
+1. **Google Business Profile** — Claim hub and richest Core 3 surface; usually the strongest owner-facing source of truth. Owner claims the listing and fixes NAP (and categories) in the GBP dashboard; we treat that claim as proof on other tickets.
+2. **Apple Business Connect** — Second Core 3 leg; place cards on Apple Maps and related Apple surfaces. Owner claims and corrects NAP / hours / categories in Business Connect (or via a partner that writes that API).
+3. **Bing Places** — Third Core 3 leg; feeds Bing local and Copilot-adjacent experiences. Owner claims in Bing Places and files corrections through Bing Places feedback / update flows with the same field / wrong / right / proof ticket.
+4. **Foursquare Places** — Umbrella **and** its own POI graph (Lane A + B). Prefer Placemaker `POST /places/{id}/suggest/edit`, or white-label the same path via Managed Users when we file on the owner’s behalf.
+5. **Yelp** — Strong consumer destination and historical source into maps / directories. Lane B: suggest-an-edit form with field, wrong value, right value, and GBP as proof.
+6. **Data Axle Local Listings** — Primary umbrella into many publishers (Lane A). Claim / submit via Data Axle Local Listings or Local Listings Premium so corrections propagate instead of hand-fixing every long-tail directory.
+7. **Localeze / TransUnion Digital Business Profile** — Second umbrella into 80–100+ publishers (Lane A). Claim once, verify the profile, then watch propagation rather than chasing each downstream site.
+8. **YP / Thryv** — Yellow-pages stack that is both source and sink for long-tail directories. Claim and correct through YP / Thryv listing management when the audit shows drift there.
+9. **Tripadvisor** — Vertical travel / food graph that assistants and maps sometimes cite. Claim and correct via Tripadvisor’s business tools when the genre makes that surface matter.
+10. **Facebook / Meta** — Own Pages graph; weak as a classic NAP aggregator. Claim the Page and fix info / address / hours there; usually lower weight than Core 3 + umbrellas for Presence.
+11. **MapQuest / HERE / in-car nav / long-tail directories** — Heavy aggregator consumers with weak owner claim surfaces. Prefer Lane A umbrella tickets; open a direct ticket only when a real correction form exists and the audit still shows a miss after umbrellas settle.
+12. **Dun & Bradstreet** — B2B firmographics, not consumer local discovery. Low priority unless a specific B2B recommendability path needs it.
+13. **CityGrid** — Legacy network. Only open a ticket if the audit actually surfaces a CityGrid-fed copy still stomping the claim.
+14. **Yext / Uberall / BrightLocal (and similar)** — Pipes, not aggregators. If the client already pays one, route corrections through that pipe into Lanes A and B instead of inventing a parallel write; do not treat the pipe as a Presence destination of its own.
+
 Longer term, the Northstar — the destination we aim at but do not build first — is an **industry graph**: a shared, structured map of local businesses that many products and assistants could use. That is not version one. Version one earns the right to that graph by helping owners see how AI sees them today and fix what is broken, with their consent.
 
 ---