prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  tests
   +--client_certs
   |   `--password_protected
   +--fixtures
   |   +--session_data
   |   |   +--new
   |   |   `--old
   |   `--xmldata
   |       +--invalid
   |       +--valid
   |       `--xhtml
   `--utils
       `--matching
  ```
  
  Convert this description:
  
  app is a origin directory that incorporates 5 subdirectories. Notable ones include client-component, global-error-boundary, server-actions among others.
  
  Let me break down the composition for you:
  
  At the main level, 'client-component' has no folders inside.
  At the main level, 'global-error-boundary' houses 2 directory entries: client, server.
  Within directory hierarchy 'global-error-boundary > client', The 'client' compartment is blank.
  Within directory hierarchy 'global-error-boundary / server', Inside 'server', you'll find it awaits content.
  At the top level, 'server-actions' contains no subdirectories.
  In the root directory, 'server-component' encompasses 4 numerous child directories.
  At level 2, in directory path 'server-component > custom-digest', Inside 'custom-digest', you'll find it is empty.
  In nested path 'server-component > throw-null', Inside 'throw-null', you'll find it lacks any subdirectories.
  Within directory hierarchy 'server-component > throw-string', Inside 'throw-string', you'll find it contains no subdirectories.
  At level 2, in directory path 'server-component / throw-undefined', 'throw-undefined' is vacant.
  At the top level, 'ssr-error-client-component' is blank.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "app\n +--client-component\n +--global-error-boundary\n |   +--client\n |   `--server\n +--server-actions\n +--server-component\n |   +--custom-digest\n |   +--throw-null\n |   +--throw-string\n |   `--throw-undefined\n `--ssr-error-client-component", "description": "app is a origin directory that incorporates 5 subdirectories. Notable ones include client-component, global-error-boundary, server-actions among others.\n\nLet me break down the composition for you:\n\nAt the main level, 'client-component' has no folders inside.\nAt the main level, 'global-error-boundary' houses 2 directory entries: client, server.\nWithin directory hierarchy 'global-error-boundary > client', The 'client' compartment is blank.\nWithin directory hierarchy 'global-error-boundary / server', Inside 'server', you'll find it awaits content.\nAt the top level, 'server-actions' contains no subdirectories.\nIn the root directory, 'server-component' encompasses 4 numerous child directories.\nAt level 2, in directory path 'server-component > custom-digest', Inside 'custom-digest', you'll find it is empty.\nIn nested path 'server-component > throw-null', Inside 'throw-null', you'll find it lacks any subdirectories.\nWithin directory hierarchy 'server-component > throw-string', Inside 'throw-string', you'll find it contains no subdirectories.\nAt level 2, in directory path 'server-component / throw-undefined', 'throw-undefined' is vacant.\nAt the top level, 'ssr-error-client-component' is blank.\n"}