SDAI Rewrite + EGP-DS Market Bring-Online — End-to-End Implementation Plan

DD: DD-SDAI-EGP-DS-Market-Rewrite · 2026-05-18 · Owner: ExCom+ Unified (Betty + Gemma + Vesta + Willemena) · Status: Marc-ratify-pending · Classification: EGP Confidential

1. Executive Summary

EGP-DS (EGP Directory Services) is the four-continent multi-market hub-and-spoke directory network spanning Americas, Europe, Asia-Pacific, and Middle East and Africa. The SDAI app (Site Directory AI / SDAI Market Site customization engine, per Jira EDSR-180, EDSR-181, EDSR-197, EDSR-198) is the codegen and config layer that customizes each Market Site from a single versioned template.

Goal: bring the rewritten SDAI app online and stand up the first three EGP-DS Market Sites (Washington DC EST pilot, Chicago CST, Calgary MST per EDSR-101, EDSR-102, EDSR-103). Pilot domain confirmed in ENDS-1: directory.northernvirginia.va.us.enroutegrowthplatform.io. Public portal should additionally surface at directory.enroute.global.

2. What's Already Completed

Sourced from Jira (EDSR + EDSML + ENDS + EGPDS projects).

Discovery gap: Deep filesystem grep across tools/ and workflows/ was blocked this session (Bash denied). A follow-on subagent must complete the SDAI-related code-asset inventory before Sprint 1 starts. See Appendix B.

Jira spine: EDSR-155 Initiative "EGP-DS Market Launch Factory v1 {Market}" scoped (2026-02-16) covering content/pages, DNS/email/webmaster, schema/SEO, EGP.SEO Web Studio hub/site codegen, ORCA BrowserAct rollout, LZ_LP/MDM_LP Drive drops for PowerBI, JSM, CS SOPs, FinOps attribution, Trust Center, SDAI customization, QA via Xray.
Pilot markets locked:
- EDSR-101 Washington DC Capital Business Directory (1st EST, Priority Highest)
- EDSR-102 Chicago Industry and Trade Directory (1st CST)
- EDSR-103 Calgary Enterprise Hub Directory (1st MST)
SDAI epics already drafted: EDSR-180 (Customize each Market Site via SDAI App), EDSR-181 (SDAI runbook + Xray MVP), EDSR-197 (SDAI customization template), EDSR-198 (SDAI runbook + Xray MVP tests).
Adjacent rails scoped: EDSR-152/153/154 (Domain Configuration), EDSR-156 (taxonomy + wave governance), EDSR-157 (content + conversion), EDSR-158 (market infrastructure), EDSR-167 (Stripe + CS SOPs), EDSR-170 (page set), EDSR-175 (social engine), EDSR-200 (GetLensly audit pack), EDSR-201 (cost tagging).
NOVA pilot runbook initiative: ENDS-1 Launch Directory.NOVA.US.VA.EGP.io Runbook.
EDSML-1: Market Launch Factory mirror task (annisa.aulya assigned).
Canon already locked: 4-continent naming standard; clickable HTTPS URLs (not local paths); HTML companion required for every .md.

Not yet evidenced (gap log): prior SDAI repo location, test results from any prior SDAI version, Stripe SKUs for Get-Listed flow, Cloudflare account-level naming for the directory.* zone.

3. Where We Left Off

Jira spine fully scoped 2026-02-16 by annisa.aulya; nothing transitioned from To-Do since.
Original SDAI app (pre-rewrite) hit customization-per-market friction; Marc directed a rewrite (this DD).
No Market Site is live in production; ENDS-1 NOVA URL stub registered but not serving.
Q1 2026 froze on four infrastructure decisions (platform, Stripe hooks, ORCA feed, portal domain). This plan unblocks all four and queues Sprint 1.

4. Jira Space Details

Project	Key	Type	Purpose	URL
EGP Directory Services Roadmap	EDSR	Software (classic)	Primary engineering backlog	browse/EDSR
EGP Directory Services Market Launch	EDSML	Business (next-gen)	Per-market launch task tracker	browse/EDSML
EGP Directory Services	EGPDS	Business (next-gen)	Executive shell (ExCom+ rollups)	browse/EGPDS
EGP NOVA Directory Services	ENDS	Software (classic)	NOVA-specific pilot runbook + ops	browse/ENDS

Routing for this DD: engineering + SDAI rewrite stories → EDSR; per-market launch checklists → EDSML; ExCom+ weekly rollup → EGPDS; NOVA-only ops → ENDS.

Confluence companion: SWAT space EGPSWAT (per Marc-locked 2026-05-16 routing canon; this DD is SWAT-scope, not CS).

5. Domain and Portal

Recommended primary public portal: directory.enroute.global.

market.enroute.global reads as marketplace (transactional), EGP-DS leads with discovery.
egp-ds.enroute.global leaks internal product code (memory canon violation).
ENDS-1 long path is a per-market subdomain, not the portal root.

Per-market pattern: directory.{city}.{state-or-region}.{country}.enroute.global with 301 alias from legacy enroutegrowthplatform.io path.

Continent-tier homes:

directory.enroute.global/americas
directory.enroute.global/europe
directory.enroute.global/asia-pacific
directory.enroute.global/middle-east-africa

6. Runbook

Pre-flight gate (Day 0)

Marc ratifies this plan.
PanCom confirms naming canon compliance.
Vesta files the three Sprint-1 Jira stories (Section 10).

Sprint 1 (Days 1 to 5) — SDAI Rewrite Foundation

Cloudflare Pages project sdai-app linked to GitHub repo egp-sdai-app.
Workers backend sdai-api with D1 binding for market config registry.
Port EDSR-197 customization template into JSON-schema, version v0.1.
R2 bucket egp-sdai-artifacts for screenshots, sitemaps, audit reports.
Stripe test-mode webhook lands at sdai-api/webhooks/stripe-checkout-complete and provisions new market-tenant row in D1.

Sprint 2 (Days 6 to 10) — First Market End-to-End

Render DC market site (EDSR-101) from SDAI config v0.1 to directory.dc.us.enroute.global.
Schema.org LocalBusiness + ItemList JSON-LD baked into every page.
ORCA BrowserAct feeds first 200 DC listings into LZ_LP Drive bucket; promoted to MDM_LP after Vesta validates schema.
Search Console + GA4 + Plausible verified.
JSM portal at support.directory.enroute.global linked to EDSML.

Sprint 3 (Days 11 to 15) — Wave-1 + Hardening

Render Chicago (EDSR-102) and Calgary (EDSR-103) from same template.
Xray MVP suite (EDSR-198) runs against all three markets.
Stripe live-mode flip on Get-Listed (basic + featured + premium per EDSR-167).
Trust Center at directory.enroute.global/trust.
Cost-tagging (EDSR-201) wired to PowerBI FinOps dashboard.

Sprint 4 (Days 16 to 18) — Launch + Marketing

PR + social cadence (EDSR-175) fires for DC.
CS SOPs for inbound listing requests live; quotas seeded.
Marc demo + ExCom+ go-live signoff.
Wave-2 markets unblocked.

7. SWOT

Strengths	Weaknesses
Jira spine already exists Cloudflare, Workers, R2, D1 all in production ORCA listing pipeline operational 4-continent naming Marc-locked	Prior SDAI codebase not yet inventoried No Market Site in PROD; zero baseline Stripe SKUs not created Phone routing (EDSR-158) undecided
Opportunities	Threats
4-continent footprint = defensible moat ORCA + GetLensly = paid upsell day one Schema-rich = canonical AI-citation source (GEO) ~1-day marginal cost per new market once template locked	Google manual action if listings are thin Stripe Connect compliance at scale Domain-reputation risk on enroute.global Cloudflare vendor lock-in (mitigated by portable JSON-schema)

8. Five Solution Paths

Path	Stack	Pros	Cons	Days
A	Next.js + Vercel	Best DX; SSG + ISR; large hiring pool	New vendor; egress costs at scale; second observability stack	22 to 28
B (RECOMMENDED)	Cloudflare Pages + Workers + D1	Matches existing infra; edge-global; single observability; 4-continent edge match	D1 maturity for huge datasets (mitigated); Next adapters needed	18
C	GHL Custom Pages	Zero new infra; CS trained	Whitelabel canon conflict; cannot deliver schema-rich GEO surface; rate limits choke at scale	14 (low ceiling)
D	Headless CMS (Payload/Strapi) + CF Pages	Best editor UX; clean API; future-proof	Adds CMS db/host/auth/upgrade ops; template lives in two places	26 to 30
E	Hybrid (CMS + Workers + Stripe)	Best separation of concerns	Largest surface area; two SOTs; only worth it at 50+ markets	32 to 38

9. Top Three Risks

Listing-content thinness (Search Console manual action). Mitigation: Vesta similarity-score lint before publish; min 350 unique words per listing; no cross-market duplicate paragraphs.
Stripe Get-Listed misroutes funds at multi-market scale. Mitigation: per-market Stripe Connect sub-account; Marc-locked dual-confirmation on Sprint 3 live-flip; daily reconciliation.
SDAI template drift erodes the "1-day per market" promise. Mitigation: strict JSON-schema; CI lint refuses publish on invalid config; quarterly template-version migration tooling.

10. Immediate-Next-Step Jira Stories (Sprint 1)

To be filed by Vesta against EDSR within 24 hours of Marc ratification:

EDSR-NEW1 (Story, parent EDSR-180): "SDAI rewrite — Cloudflare Pages + Workers + D1 scaffold." AC: repo created, Pages deployed, Workers reachable at api.directory.enroute.global, D1 binding MARKETS live.
EDSR-NEW2 (Story, parent EDSR-197): "SDAI customization template v0.1 — JSON-schema lock." AC: schema published, validation CLI passes for DC/Chicago/Calgary fixtures; PanCom signs off on naming canon.
EDSR-NEW3 (Story, parent EDSR-181): "Xray MVP test pack — content, CTAs, schema, analytics, sitemap." AC: 5 test plans imported, smoke-pass on fixture site, runbook published to SWAT Confluence.

Plus one launch task in EDSML:

EDSML-NEW1 (Task, parent EDSML-1): "Wave-1 launch checklist — DC, Chicago, Calgary." AC: per-market checklist mirroring EDSR-101/102/103 ACs; CS/Ops/FinOps signoff slots; Marc final-approve slot.

Appendix A — Canon Compliance Checklist

No em-dashes (commas, colons, parentheses only)
4-continent naming spelled fully (Americas, Europe, Asia-Pacific, Middle East and Africa)
No whitelabel partner names exposed (Cloudflare + Stripe are allowlisted infra-tier)
Persona attribution on first line
HTML companion produced at same path
Deliverable under canonical 00148-EGP-CDAIO-Knowledge-Access/01-strategy/

Appendix B — Discovery Gaps For Follow-On Subagent

A follow-on subagent with Bash permission must:

Grep tools/ for sdai, SDAI, directory, egp_ds to locate prior implementation code.
Grep workflows/ for SDAI workflow markdown.
Inventory 00148-EGP-CDAIO-Knowledge-Access/strategy/ for prior DDs on this topic.
Report findings as Appendix-C addendum.