Build Bezel process-expectations idea-001
internal prototype · canonical JSON + Dreamborn Forge HTML
internal generated
process-expectations · supabase_json

Build Bezel process-expectations idea-001

process-expectations artifact · for Build Bezel · phase idea-001 · status draft

Planning Surface

Use this to decide what happens next.

Status

draft

Phase

idea-001

Agent Handoff
Start Here

process-expectations artifact · for Build Bezel · phase idea-001 · status draft

Completion Evidence

No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.

Artifact Shape
  • phase: idea-001
  • artifact: process-expectations
  • positioning: This is a production product-definition process, not a quick mockup generator.
  • resume model: Like doing taxes: each step is saved, the user always knows what is complete, what is next, what is blocked, and where to resume.
  • expectation copy: For meaningful products, plan to spend a couple of focused hours reviewing intent, assumptions, AI-first opportunities, screens, workflows, architecture, and build plan before development starts. Bezel will guide the whole process and save progress at every step.
  • project size guidance: 3 items
  • required progress states: 6 items
Structured Payload

Machine-readable source fields

phase

idea-001

artifact

process-expectations

positioning

This is a production product-definition process, not a quick mockup generator.

resume model

Like doing taxes: each step is saved, the user always knows what is complete, what is next, what is blocked, and where to resume.

expectation copy

For meaningful products, plan to spend a couple of focused hours reviewing intent, assumptions, AI-first opportunities, screens, workflows, architecture, and build plan before development starts. Bezel will guide the whole process and save progress at every step.

project size guidance
sizedescription
smallOne-page or narrow workflow; may move through a short one-pass flow.
mediumMultiple screens or user roles; needs intent, AI-first reframe, screen map, wireframes, architecture, and plan review.
large_or_multiphaseMultiple workflows, systems, or releases; must be categorized and phased before detailed design.
required progress states
  • not_started
  • in_progress
  • needs_review
  • approved
  • blocked
  • revised