screen-map · supabase_json
Bezel Team screen-map design-001
screen-map artifact · for Bezel Team · phase design-001 · status draft
screens
| id | name | priority | user roles | build phase | data inputs |
|---|---|---|---|---|---|
| project.new | New Product Project | must | - product_owner | M-01 | - project_name - company_or_owner - initial_product_idea - target_user_hint |
| project.intake | Guided Product Intake | must | - product_owner | M-01 | - intake_questions - customer_answers - attachments - domain_context |
| intent.review | Product Intent Review | must | - product_owner - dreamborn_operator | M-01 | - intent_artifact - intake_answers - open_questions |
| opportunity.map | AI-First Opportunity Map | must | - product_owner - dreamborn_operator | M-02 | - intent_artifact - workflow_analysis - screen_candidates |
| agent.expansion.scope | Supporting Agent Scope | should | - product_owner - dreamborn_operator | M-02 | - agent_recommendations - customer_priorities |
| screen.map | Screen Map | must | - product_owner - designer - dreamborn_operator | M-02 | - intent_artifact - opportunity_map - generated_screen_records |
| flow.review | Flow Review | must | - product_owner - designer | M-02 | - screen_map - user_roles - business_rules |
| wireframe.review | Wireframe Review | must | - product_owner - designer | M-03 | - screen_map - flow_spec - wireframe_specs |
| screen.state.matrix | Screen State Matrix | must | - product_owner - designer - developer | M-03 | - screen_map - wireframe_specs |
| architecture.review | Architecture Review | must | - product_owner - technical_reviewer - dreamborn_operator | M-04 | - approved_intent - approved_screen_map - approved_wireframes - integration_needs |
| build.plan.review | Build Plan Review | must | - product_owner - dreamborn_operator | M-04 | - architecture_artifact - screen_state_spec - policy_artifact |
| scope.pricing.review | Scope + Pricing Review | should | - product_owner - dreamborn_operator | M-04 | - plan_artifact - opportunity_map - agent_expansion_backlog |
| build.dashboard | Build Dashboard | must | - product_owner - dreamborn_operator | M-05 | - approved_plan - agent_tasks - cluster_events - proof_bundles |
| task.detail | Build Task Detail | must | - product_owner - dreamborn_operator - developer | M-05 | - agent_task - source_artifacts - proof_bundle |
| proof.bundle | Proof Bundle | must | - product_owner - developer - dreamborn_operator | M-05 | - changed_files - test_output - screenshots - deployment_preview - source_artifacts |
| blocker.review | Blocker Review | should | - product_owner - dreamborn_operator | M-05 | - blocker_event - related_artifacts - agent_context |
| release.review | Release Review | must | - product_owner - dreamborn_operator | M-06 | - release_candidate - proof_bundles - deployment_preview |
| hosting.choice | Hosting Choice | must | - product_owner - dreamborn_operator | M-06 | - architecture_artifact - customer_infrastructure_preferences |
| live.product.status | Live Product Status | should | - product_owner - dreamborn_operator | M-06 | - deployment_status - health_checks - recent_releases |
| iteration.backlog | Iteration Backlog | should | - product_owner - dreamborn_operator | M-07 | - customer_feedback - support_requests - agent_opportunities - build_history |
| discovery.chat | Discovery Conversation | must | - product_owner - dreamborn_operator | M-01 | - chat_messages - intake_context - attachments - prior_answers |
| strategy.qa | Strategy Q&A | must | - product_owner - dreamborn_operator | M-02 | - current_artifact_context - screen_or_task_context - prior_decisions - chat_messages |
| design.qa | Design Q&A | must | - product_owner - dreamborn_operator | M-03 | - current_artifact_context - screen_or_task_context - prior_decisions - chat_messages |
| planning.qa | Planning Q&A | should | - product_owner - dreamborn_operator | M-04 | - current_artifact_context - screen_or_task_context - prior_decisions - chat_messages |
| build.qa | Build Q&A | should | - product_owner - dreamborn_operator | M-05 | - current_artifact_context - screen_or_task_context - prior_decisions - chat_messages |
| release.qa | Release Q&A | should | - product_owner - dreamborn_operator | M-06 | - current_artifact_context - screen_or_task_context - prior_decisions - chat_messages |
| model.comparison.review | Model Comparison Review | must | - product_owner - dreamborn_operator | M-02 | - model_review_artifact - source_artifacts - decision_context |
| decision.synthesis | Decision Synthesis | must | - product_owner - dreamborn_operator | M-04 | - model_reviews - qa_threads - artifact_context |
| model.research.panel | Model Research Panel | must | - product_owner - dreamborn_operator | M-02 | - current_screen_or_artifact - model_review_artifacts - qa_context |
| project.overview | Project Overview + Next Action | must | - product_owner - dreamborn_operator | M-01 | - project_status - artifact_statuses - approval_gates - open_questions - blocked_items - recent_activity |
| playground.review | Playground Review | must | - product_owner - dreamborn_operator - designer | M-03 | - preview_metadata - wireframe_spec - screen_map - model_output |
Agent Handoff
Start Here
screen-map artifact · for Bezel Team · phase design-001 · status draft
Completion Evidence
No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.
Artifact Shape
- kind: bezel.screen-map
- purpose: Dogfood Bezel by designing Bezel screen-by-screen before architecture/build. This artifact is the canonical human-reviewable screen inventory for V1.
- screens: 31 items
- version: 1
- created at: 2026-05-04T12:26:08.890Z
- project id: bezel-team
- updated at: 2026-05-04T14:57:54.482Z
- design rule: Keep the existing artifact process. Add screen-by-screen detail as a required middle layer before architecture and build.
- primary user: founder_or_operator_with_product_idea
- product name: Bezel Product Studio
- screen groups: 6 items
- approval gates: 7 items
Structured Payload
Machine-readable source fields
kind
bezel.screen-map
purpose
Dogfood Bezel by designing Bezel screen-by-screen before architecture/build. This artifact is the canonical human-reviewable screen inventory for V1.
screens
| id | name | priority | user roles | build phase | data inputs |
|---|---|---|---|---|---|
| project.new | New Product Project | must | - product_owner | M-01 | - project_name - company_or_owner - initial_product_idea - target_user_hint |
| project.intake | Guided Product Intake | must | - product_owner | M-01 | - intake_questions - customer_answers - attachments - domain_context |
| intent.review | Product Intent Review | must | - product_owner - dreamborn_operator | M-01 | - intent_artifact - intake_answers - open_questions |
| opportunity.map | AI-First Opportunity Map | must | - product_owner - dreamborn_operator | M-02 | - intent_artifact - workflow_analysis - screen_candidates |
| agent.expansion.scope | Supporting Agent Scope | should | - product_owner - dreamborn_operator | M-02 | - agent_recommendations - customer_priorities |
| screen.map | Screen Map | must | - product_owner - designer - dreamborn_operator | M-02 | - intent_artifact - opportunity_map - generated_screen_records |
| flow.review | Flow Review | must | - product_owner - designer | M-02 | - screen_map - user_roles - business_rules |
| wireframe.review | Wireframe Review | must | - product_owner - designer | M-03 | - screen_map - flow_spec - wireframe_specs |
| screen.state.matrix | Screen State Matrix | must | - product_owner - designer - developer | M-03 | - screen_map - wireframe_specs |
| architecture.review | Architecture Review | must | - product_owner - technical_reviewer - dreamborn_operator | M-04 | - approved_intent - approved_screen_map - approved_wireframes - integration_needs |
| build.plan.review | Build Plan Review | must | - product_owner - dreamborn_operator | M-04 | - architecture_artifact - screen_state_spec - policy_artifact |
| scope.pricing.review | Scope + Pricing Review | should | - product_owner - dreamborn_operator | M-04 | - plan_artifact - opportunity_map - agent_expansion_backlog |
| build.dashboard | Build Dashboard | must | - product_owner - dreamborn_operator | M-05 | - approved_plan - agent_tasks - cluster_events - proof_bundles |
| task.detail | Build Task Detail | must | - product_owner - dreamborn_operator - developer | M-05 | - agent_task - source_artifacts - proof_bundle |
| proof.bundle | Proof Bundle | must | - product_owner - developer - dreamborn_operator | M-05 | - changed_files - test_output - screenshots - deployment_preview - source_artifacts |
| blocker.review | Blocker Review | should | - product_owner - dreamborn_operator | M-05 | - blocker_event - related_artifacts - agent_context |
| release.review | Release Review | must | - product_owner - dreamborn_operator | M-06 | - release_candidate - proof_bundles - deployment_preview |
| hosting.choice | Hosting Choice | must | - product_owner - dreamborn_operator | M-06 | - architecture_artifact - customer_infrastructure_preferences |
| live.product.status | Live Product Status | should | - product_owner - dreamborn_operator | M-06 | - deployment_status - health_checks - recent_releases |
| iteration.backlog | Iteration Backlog | should | - product_owner - dreamborn_operator | M-07 | - customer_feedback - support_requests - agent_opportunities - build_history |
| discovery.chat | Discovery Conversation | must | - product_owner - dreamborn_operator | M-01 | - chat_messages - intake_context - attachments - prior_answers |
| strategy.qa | Strategy Q&A | must | - product_owner - dreamborn_operator | M-02 | - current_artifact_context - screen_or_task_context - prior_decisions - chat_messages |
| design.qa | Design Q&A | must | - product_owner - dreamborn_operator | M-03 | - current_artifact_context - screen_or_task_context - prior_decisions - chat_messages |
| planning.qa | Planning Q&A | should | - product_owner - dreamborn_operator | M-04 | - current_artifact_context - screen_or_task_context - prior_decisions - chat_messages |
| build.qa | Build Q&A | should | - product_owner - dreamborn_operator | M-05 | - current_artifact_context - screen_or_task_context - prior_decisions - chat_messages |
| release.qa | Release Q&A | should | - product_owner - dreamborn_operator | M-06 | - current_artifact_context - screen_or_task_context - prior_decisions - chat_messages |
| model.comparison.review | Model Comparison Review | must | - product_owner - dreamborn_operator | M-02 | - model_review_artifact - source_artifacts - decision_context |
| decision.synthesis | Decision Synthesis | must | - product_owner - dreamborn_operator | M-04 | - model_reviews - qa_threads - artifact_context |
| model.research.panel | Model Research Panel | must | - product_owner - dreamborn_operator | M-02 | - current_screen_or_artifact - model_review_artifacts - qa_context |
| project.overview | Project Overview + Next Action | must | - product_owner - dreamborn_operator | M-01 | - project_status - artifact_statuses - approval_gates - open_questions - blocked_items - recent_activity |
| playground.review | Playground Review | must | - product_owner - dreamborn_operator - designer | M-03 | - preview_metadata - wireframe_spec - screen_map - model_output |
version
1
created at
2026-05-04T12:26:08.890Z
project id
bezel-team
updated at
2026-05-04T14:57:54.482Z
design rule
Keep the existing artifact process. Add screen-by-screen detail as a required middle layer before architecture and build.
primary user
founder_or_operator_with_product_idea
product name
Bezel Product Studio
screen groups
| id | goal | name | screens |
|---|---|---|---|
| entry | Turn a raw product idea into a structured Bezel project. | Project Start | - project.overview - project.new - discovery.chat - project.intake - project.confirmation |
| strategy | Clarify product intent and identify where to move from SaaS-shaped workflows to AI-first workflows. | Intent + AI-First Opportunity | - intent.review - opportunity.map - agent.expansion.scope - strategy.qa - model.comparison.review |
| design | Make the product visible and reviewable before build. | Screen + Wireframe Design | - screen.map - flow.review - wireframe.review - screen.state.matrix - design.qa - playground.review |
| planning | Convert approved product design into production architecture and executable build plan. | Architecture + Build Plan | - architecture.review - build.plan.review - scope.pricing.review - planning.qa - decision.synthesis |
| build | Run the AI dev team against approved artifacts with visible progress and gates. | Build Execution | - build.dashboard - task.detail - proof.bundle - blocker.review - build.qa - model.research.panel |
| release | Deploy real production software and manage follow-on iteration. | Release + Operation | - release.review - hosting.choice - live.product.status - iteration.backlog - release.qa |
approval gates
| gate | requires |
|---|---|
| G1 Intent | - intent.review approved |
| G2 AI-First Opportunity | - opportunity.map reviewed |
| G3 Screens | - screen.map approved - flow.review approved |
| G4 Wireframes + States | - wireframe.review approved for must screens - screen.state.matrix approved |
| G5 Build Plan | - architecture.review approved - build.plan.review approved - scope.pricing.review acknowledged or waived |
| G6 Release | - release.review approved - hosting.choice selected |
| G0 Discovery | - discovery.chat or project.intake produces structured facts and open questions |
cross screen shell
phases
- Discovery
- Intent
- AI-First Opportunity
- Screens
- Wireframes
- Architecture
- Build Plan
- Build
- Release
- Operate/Iterate
required elements
- phase progress rail
- current step header
- next action panel
- blockers/open questions indicator
- ask Bezel contextual Q&A control
next action examples
- Answer discovery question
- Approve intent
- Review AI-first opportunities
- Approve screen map
- Review wireframes
- Approve build plan
- Review proof bundle
- Approve deploy
deployment context
shell name
Dreamborn Build
product name
Bezel
canonical domain
build.dreamborn.ai
navigation implication
Screens should be designed as a Dreamborn-owned build studio, not as a standalone generic SaaS dashboard.
orientation system
principle
The customer should always know where they are in the product-build process and what they are doing next.
action rule
Every review screen must have one primary next action and one clear escape: request changes, ask question, or save for later.
artifact rule
Orientation data should come from phase/gate status and artifact approval state, not static copy.
shell pattern
Persistent project progress rail plus current-step header plus next-action panel.
required questions
- Where am I?
- What phase is this?
- What did Bezel just produce or learn?
- What decision/action is needed from me?
- What happens next after I approve or request changes?
- What is blocked?
process positioning
rule
Screen-map, flow-spec, wireframe-spec, and screen-state-spec extend the current artifact system. They do not replace INTENT, REQUIREMENTS, ARCHITECTURE, POLICY, PLAN, or model review.
statement
Dreamborn already has a strong artifact-driven design process. The gap is not quality; it is screen-level granularity before build.
why it matters
Customers and build agents need to see the product screen by screen. Product owners approve what they can visualize; dev agents build more reliably when each task anchors to an approved screen/state.
integration point
Insert the screen layer after intent/opportunity review and before architecture/build plan approval.
product flow summary
- Customer starts a production product project.
- Bezel interviews them and turns the idea into intent.
- Bezel proposes AI-first opportunities and supporting agents.
- Bezel proposes screen inventory and flows.
- Customer reviews wireframes and screen states.
- Bezel generates architecture and build plan from approved screens.
- Customer approves build.
- Bezel runs the AI dev team and shows production progress.
- Customer reviews implementation and deploys/hosts on Dreamborn or connected infrastructure.
- Customer iterates and optionally buys supporting agents.
playground generation
protocol
id
8f3eee50-794f-4685-848a-b2f3b62ae9a3
phase id
design-001
artifact type
playground-generation-protocol
principle
Screen-level artifacts should be visually reviewable through generated playgrounds before build.
first source
wireframe-spec/design-001
manual trigger label
Generate Playground
artifact source of truth rule
screen-map/wireframe-spec/screen-state-spec remain canonical; generated HTML is disposable review evidence.
immediate review slice
question
Do these screen groups and must-have screens match how Bezel Product Studio should guide a customer from idea to production?
likely cut for v1
- agent.expansion.scope as separate screen
- flow diagram visualization
- live.product.status depth
- iteration.backlog depth
- planning.qa as separate route
- build.qa as separate route
- release.qa as separate route
likely keep for v1
- playground.review
- project.overview
- model.comparison.review
- decision.synthesis
- model.research.panel
- discovery.chat
- strategy.qa
- design.qa
- project.new
- project.intake
- intent.review
- opportunity.map
- screen.map
- wireframe.review
- screen.state.matrix
- architecture.review
- build.plan.review
- build.dashboard
- proof.bundle
- release.review
- hosting.choice
conversational discovery
principle
Bezel should ask and answer questions in context. Conversation is not a generic chatbot; it is the way product uncertainty gets resolved and attached to artifacts.
two modes
| mode | where | output | purpose |
|---|---|---|---|
| intake_discovery | Early project intake | Structured intent, open questions, assumptions, screen candidates, and AI-first opportunity candidates. | Back-and-forth discovery to extract product intent, users, workflows, constraints, business rules, and unknowns. |
| contextual_artifact_qa | Later review screens for intent, opportunity map, screen map, wireframes, architecture, plan, build, and release | Resolved answers, comments, decisions, requested changes, or new open questions attached to the relevant artifact/screen id. | Let the customer ask questions directly on the screen they are reviewing, and let Bezel answer with artifact-aware context or create revision tasks. |
non negotiables
- Q&A must be attached to an artifact id, screen id, flow id, or task id whenever possible.
- Important answers must be promoted into structured artifacts; they cannot remain buried in chat transcript.
- If Bezel is uncertain, it should ask a targeted question instead of guessing.
- Customer chat should support request changes, explain this, why this screen exists, what happens if, and what would the agent do here.
multi model collaboration
principle
Multi-model research and critique should be embedded throughout the screens as evidence and collaboration, not hidden in backend logs.
screen pattern
Each major review screen can show Model Perspectives: raw evidence, disagreement, recommendation, and accepted decision.
required surfaces
- model.research.panel
- model.comparison.review
- decision.synthesis
- evidence.drawer
context attachment rule
Model outputs must attach to artifact/screen/decision IDs and feed structured artifacts after human approval.