Runways implement

Brand playbook

Port Runways without forking the Motor.

This Cloudflare Pages site is the sellable standalone surface. The Motor stays in NOETFIELD-RUNWAY. Each brand ships its own landing + HMAC proxy; none re-implement the control plane.

1. Split surfaces

  • Product landing — this repo path: sites/runways-standalone/ → own Pages project.
  • Corporate site — Noetfield/Trustfield/Source* keep brand narrative; deep-link here to sell the capability.
  • Motor — shared staging/production Worker at POST /v1/jobs (HMAC).

2. Minimum copy for another brand

  1. Clone sites/runways-standalone/.
  2. Replace brand mark, fonts only if the brand system requires it, and legal footer.
  3. Keep honesty badges: Demonstrated / Available / Planned — never invent revenue claims.
  4. Point enterprise CTA to that brand’s intake; keep demo dispatch on allowlisted recipes.
  5. Deploy as a separate Cloudflare Pages project (do not bury inside the corporate artifact allowlist unless you intentionally want one deploy unit).

3. Required secrets (Pages)

RUNWAY_RUNTIME_API_SECRET
RUNWAY_RUNTIME_BASE_URL=https://…workers.dev
RUNWAY_RUNTIME_KEY_ID=staging-proof

4. Cost doctrine (shared)

Workers own routing/state/validation. Cheap-first model matrix. Structured JSON. Compress prompts before invoke. Cache repeated goals. Verifier—not the model—qualifies.

5. Suggested brand wiring

  • Noetfield — corporate /runways/ + this standalone sell site.
  • Trustfield.ca — link “Governed execution” → this product or a Trustfield-skinned clone.
  • SourceA / SourceB — contract SKU pages deep-link; do not duplicate Motor.

Back to product Motor source