The Pharoah coder has a live App Builder backend to wire.

Craig instructed that App Builder needs to be live on Pharoah. The shared backend is deployed and smoke-proven. Pharoah should consume the shared builder stack, not fork or rebuild it.

Open live health View homepage section

Use These

Backend base: https://app-builder-api-production.up.railway.app
Health route: /health
Shared shell source in BRG: _web/app-builder-shell/
Pharoah source in BRG: _web/pharoah-tech/
Pharoah live hub: ATTOH_DIGITAL/_hubs/pharoahtechnology.com/

First Tasks

Read the Pharoah repo CLAUDE.md, LANE-CHARTER.md, and ESTATE-REGISTER-CONSULT-FIRST.md.
Add a Pharoah-branded App Builder route using the shared shell pattern.
Inject only non-secret route metadata into the browser.
Wire health and read-only status first.
Run deployed no-write smoke before claiming Pharoah readiness.

Do Not Ship These Yet

Provider tokens, Supabase service keys, GitHub OAuth secrets, deploy keys, or Stripe keys in browser code.
Write routes before tenant auth and RLS proof exist.
Stripe checkout, live payment links, DNS changes, user invites, or outbound launch claims without receipts.
A forked builder engine. ATTOH/BRG owns the shared builder engine, model gateway, data layer, and reusable blocks.

Ownership Boundary

Pharoah is a partner-branded deployment and product route on the shared ATTOH/BRG infrastructure. The correct pattern is skin, wire, smoke, register, then launch-gate. Rebuilds only happen when the asset register proves a real gap.