Codex Recipe Factory Standard

Date: 2026-05-07

The Recipe Factory is the repeatable pattern for turning a Bezel capability into something a fresh Codex session can build from one URL.

The standard exists because Personal Brain proved the core motion:

``text Build this: https://recipes.bezeliq.ai/personal-brain ``

Codex read the public recipe, built a local Next.js app, connected it to the hosted Bezel Projects Supabase sandbox, ran build/smoke checks, and returned a working localhost URL.

A recipe URL is a product interface for agents.

A GitHub repo is still useful underneath, but a repo is a builder/developer interface. A recipe URL is what a first-time Codex user, buyer, teammate, or customer can paste into an agent and expect a working capability.

A Codex recipe is a URL-addressable capability packet with:

• a human landing page
• a machine-readable manifest
• Codex-specific instructions
• app/API/data/acceptance specs
• demo inputs when useful
• troubleshooting notes
• successful-run evidence

The canonical host is:

``text https://recipes.bezeliq.ai/{recipe-slug} ``

``text recipes/{recipe-id}/ recipe.json START_HERE.md codex-instructions.md app-spec/ screens.md data-model.md api.md acceptance.md demo/ sample-input.json troubleshooting.md future/ ``

The public URL should expose:

``text https://recipes.bezeliq.ai/{recipe-slug} https://recipes.bezeliq.ai/{recipe-slug}/recipe.json https://recipes.bezeliq.ai/{recipe-slug}/START_HERE.md https://recipes.bezeliq.ai/{recipe-slug}/codex-instructions.md ``

For each new project or capability:

1. Define the capability in plain English. 2. Choose the golden path for a first-time Codex user. 3. Decide whether V1 is hosted, private, or local-only. 4. Write the recipe packet. 5. Publish it under recipes.bezeliq.ai. 6. Start a fresh Codex session. 7. Paste only the recipe URL prompt. 8. Let Codex build the local app or workflow. 9. Run mechanical verification. 10. Save the actual successful run as evidence. 11. Harden the recipe until repeated runs converge.

A recipe is not considered real until a fresh Codex session can build it from:

``text Build this: https://recipes.bezeliq.ai/{recipe-slug} ``

with minimal help.

Minimal help means no extra architecture explanation, no hidden setup steps, and no credentials unless the recipe is explicitly a private-account recipe.

Hosted V1 exists to remove setup friction.

Rules:

• generated apps must not receive service role keys
• generated apps must not ask for Supabase credentials when the recipe says hosted V1
• generated apps should talk to a Bezel-hosted API boundary
• user install tokens should stay server-side when the generated app stack supports it
• hosted V1 must be clearly labeled as demo/early setup unless privacy/export/deletion terms are published

Personal Brain follows this model through the Bezel Projects Supabase database and personal-brain-api.

Every recipe needs a successful-run note.

Capture:

• prompt used
• app URL or output location
• generated screens/flows
• hosted/private storage mode
• checks passed
• warnings/advisories
• hardening actions

This evidence is part of the product, not an afterthought. It proves the URL can produce working software in a fresh agent context.

Repository:

``text /Users/justinking/Vaults/Projects/bezel-recipes ``

Recipe:

``text https://recipes.bezeliq.ai/personal-brain ``

Key implementation facts:

• Cloudflare Pages project: bezel-recipes
• Custom domain: recipes.bezeliq.ai
• Static build script: scripts/build-site.mjs
• First recipe: recipes/personal-brain-supabase
• Successful-run evidence: docs/successful-runs/personal-brain-2026-05-07.md

Use this same factory for:

• Gmail/calendar triage
• AI-first task extraction
• project setup wizards
• AD product modules
• future Personal Brain private Supabase and Obsidian modes

The next recipe should not start from scratch. It should start from the playbook in bezel-recipes/docs/recipe-authoring-playbook.md.