Ty_Tech/geolocal-io
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Scribe P1 foundation sync fields into BUSINESS_PLAN

Browse Source
This commit is contained in:
porbot
2026-09-15 17:29:47 +00:00
parent a1d1e12dc5
commit 05f3a88bc3
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/strategy/BUSINESS_PLAN.md
+3
View File
@@ -113,6 +113,8 @@ Foundation bar (brick-and-mortar local) — not reviews, photo perfection, or ra
Checked *on* the Core 3 (and the site). Prerequisite for 2027 work **when flaws exist**; skip invented hygiene if already clean.
**Foundation sync (P1)** across Core 3: NAP + primary category + hours + website URL + short description + service-area/address mode. Phone lives in NAP but must match. P2 (attributes, photos, menus, booking, secondary categories) is genre/known-for gated — not universal min-bar.
### 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.
@@ -171,6 +173,7 @@ If something here conflicts with `CANONICAL_STRATEGY.md`, resolve on purpose in
| 2026-09-15 | Essence: validation gate before tool use (prove you represent the business); plan tier numbers still open |
| 2026-09-15 | Essence: owner vocab Core listings / Core 3; 2017 foundation six-point bar checked on Core 3 + site |
| 2026-09-15 | Essence: two tiers — Discovery foundation → AI readiness (owner names); measure both early, fix foundation first when broken |
| 2026-09-15 | Essence: P1 foundation sync = NAP + category + hours + website + description + service-area mode; P2 genre/known-for gated |
---