{
  "id": "devon_dev_ui_workspace",
  "label": "DEVON-DEV UI Workspace Canonical",
  "phase": "phase-02",
  "category": "architecture_engineering_core",
  "status": "ACTIVE_DH_MIRROR",
  "source_no": 55,
  "purpose": "Define the operational workspace where DEVON-DEV exposes code, preview, files, terminal evidence, diffs, modals and chat without losing execution focus.",
  "function": "Govern the primary UI workspace layout contract that hosts editor, preview, file tree, terminal output, diff viewer, log panel, modal action system and floating chat as one controlled operator surface.",
  "overview": {
    "summary": "DEVON-DEV UI Workspace Canonical owns the operator workbench, not a generic frontend shell. It defines the surface where human review, code inspection, preview, evidence and controlled interaction must coexist without turning the product into scattered panels.",
    "function": "FUNCTION: Specify workspace zones, allowed panels, focus rules, evidence surfaces, editor relationship, preview relationship, terminal output placement, modal entry points and chat containment.",
    "system_position": "Floating Chat, Modal Action System and UI State Machine are downstream interface mechanisms. Admin Console governs administrative control. Preview Engine renders sandbox evidence. The workspace category is the structural host that decides how those UI capabilities can be composed without breaking operator cognition.",
    "failure_impact": "When the workspace is missing, DEVON-DEV can still have isolated UI components, but no governed operating room. Code, preview, logs, chat and approvals compete for space; the operator loses context exactly when execution decisions require concentrated evidence."
  },
  "failure_impact": "When the workspace is missing, DEVON-DEV can still have isolated UI components, but no governed operating room. Code, preview, logs, chat and approvals compete for space; the operator loses context exactly when execution decisions require concentrated evidence.",
  "technology_requirements": [
    {
      "technology": "DEVON-DEV Web UI Workspace",
      "required_for": "Define the operational workspace where DEVON-DEV exposes code, preview, files, terminal evidence, diffs, modals and chat without losing execution focus.",
      "required_by_phase": "phase-02",
      "required_by_category": "devon_dev_ui_workspace",
      "required_by_buckets": [
        "Prerequisites",
        "Installation",
        "Configuration",
        "Validation",
        "Observable Evidence",
        "Failure Modes & Recovery",
        "Completion & Promotion"
      ],
      "expected_version": "MISSING until DEVON-DEV Web UI Workspace is implemented and validated in the future Execution & Monitoring Panel",
      "validation_command": "MISSING until devon_dev_ui_workspace can prove function, source coverage, evidence state and promotion readiness",
      "evidence_path": "/home/yeff/public_html/devon/canon/execution/state/dh_sources/devon_dev_ui_workspace_canonical.json",
      "status_source": "Documentation Hub + future Execution & Monitoring Panel",
      "blocking_if_missing": true,
      "failure_impact": "When the workspace is missing, DEVON-DEV can still have isolated UI components, but no governed operating room. Code, preview, logs, chat and approvals compete for space; the operator loses context exactly when execution decisions require concentrated evidence."
    }
  ],
  "depends_on": [
    "ui_state_machine",
    "floating_chat",
    "modal_action_system"
  ],
  "used_by": [
    "devon_dev_admin_console",
    "preview_engine",
    "terminal_output_panel",
    "human_approval_service"
  ]
}