Scribe layers beyond NAP and why owners care

Base Core 3, provider extras, provider stacks (Apple vs Google).
2026-09-15 19:26:53 +00:00
parent 12901e5d5d
commit f752e8d0ae
5 changed files with 66 additions and 0 deletions
@@ -124,6 +124,16 @@ Three layers (not one giant schema): **A** universal Discovery foundation → **

 Deep example packs: [`docs/product/genre-packs/salon.md`](../product/genre-packs/salon.md), [`docs/product/genre-packs/bakery.md`](../product/genre-packs/bakery.md). Index: [`docs/product/genre-packs.md`](../product/genre-packs.md).

+### Layers beyond NAP (working direction — essence)
+
+See [`LAYERS-BEYOND-NAP.md`](./LAYERS-BEYOND-NAP.md).
+
+1. **Shared listing basics (Core 3)** — category, hours, website, description, service-area mode  
+2. **Provider listing extras** — GBP services/posts/actions/attrs; Apple Good to Know / hours types; Bing thinner  
+3. **Provider stacks** — Apple Stack (brand → Maps+Wallet/Pay, Showcases, Actions); Google = rich but fragmented listing + adjacent products  
+
+**Why owners care:** NAP = findable; extras = know what you do; stacks/actions = chosen and acted on.
+
 ### Validation gate (working direction — essence)

 Anyone using GeoLocal tools must pass a **business-representation check** first (e.g. prove control of a contact channel tied to that business). Mechanism details and free/silver/gold allotments stay open until COGS is real — only the gate itself is directional essence so far.
@@ -0,0 +1,51 @@
+# Layers beyond NAP — why owners should care
+
+**Status:** working essence (2026-09-15 session) — not locked  
+**Audience:** GeoLocal POR / owner-language planning
+
+---
+
+## NAP is the floor
+
+**NAP** = Name, Address, Phone. Matching identity across Core listings is the floor. Without it, Maps and assistants can’t reliably find the business.
+
+---
+
+## Three layers above NAP
+
+### 1. Shared listing basics (Core 3)
+
+Category, hours, website, short description, service-area/address mode — same *job* on **GBP**, **Apple Business Connect**, and **Bing Places**: what you are, when you’re open, how to reach you.
+
+Field SoT: [`../product/genre-packs/core3-field-map.md`](../product/genre-packs/core3-field-map.md).
+
+### 2. Provider listing extras
+
+Platform-specific depth beyond the shared basics, e.g.:
+
+- **GBP:** services (`serviceItems`), products, posts, Place Actions, category-dynamic attributes, photos  
+- **Apple:** Good to Know, richer hours types (normal / service / temporary), About, Actions (as offered)  
+- **Bing:** thinner extras  
+
+This moves the owner from “they can find me” → “they know what I do.”
+
+### 3. Provider brand / capability stacks
+
+Specialized capability above listing extras:
+
+- **Apple Stack (clearest unified OS):** Brand (logo, Style Guide) → place card that carries logo/cover into **Maps and Wallet/Pay**, Showcases, approved Actions, Insights  
+- **Google:** rich but **fragmented** — GBP listing extras + adjacent products (Brand profile, Merchant Center, Pay/Wallet console branding). Not one Apple-shaped brand OS  
+
+Sources: [`../product/genre-packs/SOURCES.md`](../product/genre-packs/SOURCES.md).
+
+---
+
+## Why business owners should care
+
+| Layer | Owner outcome |
+| :--- | :--- |
+| NAP | Findable — assistants and Maps can match you |
+| Shared basics + extras | Understandable — what you do, when, how to reach |
+| Stacks (esp. Apple Actions / Google Place Actions) | **Chosen and acted on** — directions, call, book, order |
+
+Discovery foundation → AI readiness is this ladder: exist → know what you do → recommend / act. NAP alone is not enough for “most recommended bakery for muffins.”
@@ -1,3 +1,5 @@
 # strategy

 Start with `BUSINESS_PLAN.md`.
+
+- [`LAYERS-BEYOND-NAP.md`](./LAYERS-BEYOND-NAP.md) — base / extras / stacks; why owners care