Enter password to view
The complete build, the commercial documents, the licensing flag, and a redeploy map so you can self-serve. The James-facing front door is the separate jpr-hub page — this one is never linked from it.
The play: the JPR app + BFF spine is productisable — JR wants it licensed to other trade firms as a V360HQ product ("TradeStack"). The JPR build is the first reference customer, not a one-off work-for-hire.
The risk: a default work-for-hire SOW would assign the platform IP to JPR and kill the licensing play. The Statement of Work must carve out V360HQ platform/architecture IP — JPR gets a licence to use the build, V360HQ retains the underlying platform.
| Property | CF project | Source path (MM01) | Redeploy command |
|---|---|---|---|
| Presentation | jpr-presentation | /CONSULTING/JPR-Digital-Infrastructure-New-Era/presentation/ | npx wrangler pages deploy presentation --project-name jpr-presentation --branch main --commit-dirty=true |
| App demo | jpr-app-demo | /CONSULTING/JPR-COMBUSTION-2026/demo/ | npx wrangler pages deploy demo --project-name jpr-app-demo --branch main --commit-dirty=true |
| Website | jpr-website-example | /CONSULTING/JPR-COMBUSTION-2026/website/ | npx wrangler pages deploy website --project-name jpr-website-example --branch main --commit-dirty=true |
| App README | jpr-app-readme | /CONSULTING/JPR-COMBUSTION-2026/readme-site/ | npx wrangler pages deploy readme-site --project-name jpr-app-readme --branch main --commit-dirty=true |
| Hub (Page A) | jpr-hub | /CONSULTING/JPR-COMBUSTION-2026/hub-a-james/ | npx wrangler pages deploy hub-a-james --project-name jpr-hub --branch main --commit-dirty=true |
| Internal (this page) | jpr-v360hq-internal | /CONSULTING/JPR-COMBUSTION-2026/hub-b-internal/ | npx wrangler pages deploy hub-b-internal --project-name jpr-v360hq-internal --branch main --commit-dirty=true |
Run from the parent folder shown in each source path. All properties live on the V360HQ Cloudflare account, gated with password jpr (client-side sessionStorage gate — light access control, not hard security; the password is visible in source). The integration report + internal docs are hosted on this page under docs/; re-copy from source if updated, then redeploy.