# Infrastructure map — accounts, projects, domains

> Living document. Rewritten 2026-10-27 from live reads of GitHub, Vercel and
> Supabase (see `docs/AUDIT-2026-10-25-SYSTEMS-INVENTORY.md`). Anything not
> readable from this repo's connectors is marked **unverified**. Do not record
> keys here, not even publishable ones; find them in each project's dashboard.
> Never put a `service_role` key in Git.

## Accounts

### Dashboard hosting target

Cloudflare Workers (`wrangler.jsonc`) replaces Vercel/Railway for this dashboard;
cutover/deployment is not yet performed. No custom route is configured.
Set `SUPABASE_URL`, `SUPABASE_ANON_KEY`, `ANTHROPIC_API_KEY` and `OPENAI_API_KEY`
as Worker bindings/secrets; optional settings are `ANTHROPIC_MODEL`,
`ANTHROPIC_WORKSPACE_ID`, `CF_ACCESS_TEAM_DOMAIN` and `CF_ACCESS_AUD`.
Setting both Access variables enables JWT verification (except `/healthz`).
Use gitignored `.dev.vars` for local values and `npx wrangler@latest dev --port 8787`.
Never store secret values in tracked files. Legacy runtime files remain for rollback.

| Platform | Account / org | Verified 2026-10-27? | Holds |
|---|---|---|---|
| GitHub | user `SilviaMogas` + org `BMBWeb3-Ventures` | ✅ | ~100 repos; inventory in `assets/repo-map.json` (generated, stale while Actions is down) |
| Vercel | one team: name **BMBWeb3Ventures**, slug **`subirachsventures`** (`team_Akdu67cKS78yGiaF1uXA0lgV`) | ✅ | 81 projects and 13 domains — **every** site, HeyLola included |
| Supabase | org **"SILVIA MOGAS"** (`vercel_icfg_XaPNWkSqbDYgMKW6hsmSAfHd`, created through the Vercel integration) | ✅ | `CRM`, PlacaPump |
| Supabase | org **"Hey Lola"** (`csegxusbwjcmukmjiudr`) | ❌ not visible to the current connector | HeyLola app, `subirachsventures` shared backend (per earlier docs) |
| Supabase | Postcards org (`nhjjenwpewdrcmnjdxsy`) | ❌ never visible | unknown |
| Railway + Cloudflare | — | ❌ no connector | production target for this dashboard, not cut over yet (`docs/RAILWAY-DEPLOY.md`) |

Older versions of this file called the "SILVIA MOGAS" org "Subirachs Ventures".
That was wrong: the Supabase org's name is "SILVIA MOGAS". "Subirachs Ventures" is
the **name of a project** inside it (see PlacaPump below) and the **slug** of the
Vercel team.

## Supabase projects

| Project name | Ref | Org | Region | Verified | What it actually is |
|---|---|---|---|---|---|
| `CRM` | `iexcdxqcygmwsboqongy` | SILVIA MOGAS | us-west-2 | ✅ healthy | CRM2's database. SilviaDashboard reads/writes it through the isolated `dashboard` schema (`docs/CRM_MIGRATION_REPORT.md`). |
| `Subirachs Ventures` | `dhvwycxkkbqzvmrkysym` | SILVIA MOGAS | ap-northeast-2 | ✅ healthy | **PlacaPump** (`placapump_profiles`, `placapump_runs`). Misleading name: it is *not* subirachsventures.com's backend. Unrelated to the dashboard; do not touch. |
| `hey@heylola.co's Project` | `bkzgxqzmkrfgclfxjvnt` | Hey Lola | us-east-1 | ❌ unverified | HeyLola production app (dogs, shelters, adoptions, wallets, donations). |
| `subirachsventures` | `lihxapotbjomnxafefhg` | Hey Lola | us-west-2 | ❌ unverified | Shared backend: newsletters, BMB client CRM (`bmb_clients`, `bmb_cases`), `vault_*`, `longhand_*`, subirachsventures.com admin. |
| Postcards project(s) | ? | Postcards org | ? | ❌ unverified | Unknown. **Contradiction:** an earlier version of this file said Postcards has a dedicated Supabase, yet `longhand_*` tables are listed in `subirachsventures` above. `needs_verification`. |
| Digital Presence (`dp_*`) | ? | ? | ? | ❌ unverified | Separate dedicated project per `DIGITAL_PRESENCE.md`. |

To verify the ❌ rows, reconnect the Supabase connector with the login that owns
those orgs.

## Sites → hosting

All domains are in the one Vercel team. Domain → project links below were read
from Vercel on 2026-10-27 where marked ✅. The 7 domains bought through Vercel
have their nameservers on Cloudflare; the 5 external ones use the registrar's
own nameservers (`registrar-servers.com`). The same table drives the Systems
tab of the dashboard (`assets/data.js` → `infraDomains`).

| Domain | Vercel project | Registrar / renewal | Notes |
|---|---|---|---|
| heylola.co | `hey-lola-eth-global-nyc-2026` ✅ (apex → www); subdomains hey., pearx., eleven., heykai., linktree., letstravel., mcp. | external registrar | earlier docs said "own dedicated Vercel": wrong, it is in the shared team |
| silviamogas.com | `vo-silvia-mogas` ✅; links./linktree. → `linktreesilviamogas`; content./creator. → `contentcreator` | external registrar | |
| blockchainmarketingboutique.com | `blockchainmarketingboutique2026` ✅; reputation. → `reputation-analyser` | external registrar | |
| subirachsventures.com | `subirachsventures` ✅; innovation. → `workingcapital.subirachsventures.com` | external registrar | Vercel shows no verified config for the apex |
| bmbweb3.com | `blockchainmarketingboutique2026` ✅ (308 redirect to www.blockchainmarketingboutique.com) | external registrar | |
| trustthesignal.media | `trust-the-signal-d9bx` ✅ | Vercel, **auto-renew off**, expires 2027-05-02 | DNS on Cloudflare |
| longhand.cards | `poscards` ✅ | Vercel, **auto-renew off**, expires 2027-07-14 | |
| famouspigeon.xyz | `famouspigeon` ✅; handover. → `handover` | Vercel, **auto-renew off**, expires 2027-07-19 | DNS on Cloudflare |
| trustnews.site | `trust-obs-sv` ✅ (not `trust-news-new2026`) | Vercel, **auto-renew off**, expires 2027-09-17 | Vercel shows no verified config for the apex |
| famouspigeon.site | `famous-pigeon-portfolio-7msn` ✅; laliga., warba., handover. | Vercel, **auto-renew off**, expires 2027-09-19 | the Linktree points here; DNS on Cloudflare |
| masafa.media | `masafa-media` ✅ | Vercel, auto-renew on, expires 2027-09-25 | |
| vitalid.site | `vitalid` ✅ | Vercel, auto-renew on, expires 2027-09-29 | |
| trusthesignal.media | none | not purchased | typo; Silvia approved deleting it (2026-10-27) |

Silvia decided on 2026-10-27 to leave the auto-renew settings as they are for
now. Check the external-registrar domains' expiry dates at that registrar.

## This dashboard

| Item | Value |
|---|---|
| Production target | Railway, `dashboard.silviamogas.com`, Cloudflare Access (decided 2026-10-27) |
| Live today | Vercel project `silvia-dashboard` → `silvia-dashboard-zeta.vercel.app` (deprecated, until the Railway cut-over) |
| Data | CRM Supabase project, `dashboard` schema |
| Knowledge | `SilviaMogas/BLACKBOX` (canonical since 2026-10-27); `knowledge/` and `SilviaMogas/obsidian` are legacy |
| CI | GitHub Actions runs again since 2026-11-03 (Validate dashboard green on `main`). Still blocked by missing secrets: **Sync repo map** skips itself (`REPO_MAP_GITHUB_TOKEN`, `VERCEL_TOKEN`) and **Deploy Silvia OS backend** fails at "Validate required secrets" (`SUPABASE_ACCESS_TOKEN`, `CRM_SUPABASE_PROJECT_REF`, `CRM_SUPABASE_DB_PASSWORD` in the `silvia-os` environment); checked 2026-11-07. Migrations are applied by hand until then. |
| Repositories | Listed inside the Systems tab since 2026-10-27, with the nine Linktree sites as Priority. `assets/repo-map.json` was refreshed by hand on 2026-10-27 (3 repos added, 2 dead ones removed) because the daily sync cannot run. |

## Cross-site rule: every contact attempt → 2 emails (decided 2026-07-18)

Applies to **every website** in the map above (heylola.co, subirachsventures.com, blockchainmarketingboutique.com, silviamogas.com, trustthesignal.media, Postcards, and — once built — crm/master email).

**Whenever a user interacts with a site in a way that constitutes a contact attempt** (contact form, lead form, waitlist signup, partner/creator application, booking request, etc.), the site must send:

1. **A confirmation email to the user** — acknowledging their message/submission was received.
2. **A copy/notification to `hello@silviamogas.com`, always** — what was submitted, from which site, and when.

Requires a **Resend API key** (or equivalent SMTP) per site — heylola.co already has one; the subirachsventures-shared sites can share one Resend account across their verified domains. This is implemented **per-repo**, server-side, on each contact-form handler. See `CROSS_SITE_RULES_PROMPT.md` in this repo for a ready-to-paste instruction for those other repos' Claude Code sessions (this repo's GitHub access doesn't extend to them, so the change has to be made from within each one).
