{
  "id": "studio-d661b935-1f2d-49c9-a42f-b1c3b23f7f3c",
  "scope": "studio_project",
  "source_of_truth": "supabase.studio_artifacts",
  "source_path": "studio_artifacts/d661b935-1f2d-49c9-a42f-b1c3b23f7f3c",
  "source_kind": "supabase_json",
  "visibility": "internal",
  "renderer_id": "design_doc.dreamborn-forge.generated.v1",
  "design_system": "dreamborn-design-system:forge",
  "generated_at": "2026-05-09T13:00:56.409Z",
  "artifact_type": "hitl-screen-design",
  "schema_version": "studio_artifact.generated.v1",
  "title": "Bezel Team hitl-screen-design design-001",
  "summary": "The current design process produces useful intent, architecture, and plans, but it does not reliably break the product into human-reviewable screens, wireframes, and states before implementation. That creates a gap where agents can build technically plausible software that the product owner never truly visualized or approved.",
  "status": "draft",
  "version": 5,
  "phase_id": "design-001",
  "project_id": "dbe36f96-c50d-46a8-badb-a0be0feeec09",
  "project_slug": "bezel-bezel-team-dbe36f96",
  "project_title": "Bezel Team",
  "client_id": "bezel",
  "platform_project_id": null,
  "format_source": "supabase_json",
  "content_shape": [
    "goal",
    "kind",
    "name",
    "problem",
    "version",
    "created_at",
    "hitl_rules",
    "project_id",
    "updated_at",
    "next_decision",
    "success_metrics",
    "wireframe_level",
    "product_principle",
    "orientation_system",
    "required_artifacts",
    "screen_record_schema",
    "customer_visible_flow",
    "multi_model_collaboration",
    "ui_implications_for_bezel",
    "first_implementation_slice"
  ],
  "sections": [
    {
      "title": "Problem",
      "level": 2,
      "body": "The current design process produces useful intent, architecture, and plans, but it does not reliably break the product into human-reviewable screens, wireframes, and states before implementation. That creates a gap where agents can build technically plausible software that the product owner never truly visualized or approved."
    },
    {
      "title": "Goal",
      "level": 2,
      "body": "Before any production build starts, Bezel must guide the customer through a concrete screen and workflow review: what screens exist, what each screen does, what states it has, what data it needs, what actions are possible, and what the customer is approving."
    },
    {
      "title": "Success Metrics",
      "level": 2,
      "body": "- Customer can explain what will be built by pointing to screens, not prose.\n- Zero build tasks are dispatched for screens lacking approved records.\n- Implementation defects caused by misunderstood screen behavior decrease over successive projects.\n- First customer approves screen map and top wireframes before build starts."
    }
  ],
  "html_path": "projects/bezel-bezel-team-dbe36f96/artifacts/hitl-screen-design-design-001-d661b935.html",
  "json_path": "projects/bezel-bezel-team-dbe36f96/artifacts/hitl-screen-design-design-001-d661b935.json"
}