prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  babel-plugin-bugfix-v8-static-class-fields-redefine-readonly
   +--src
   `--test
       `--fixtures
           +--assumption-setPublicClassFields
           |   +--length-name
           |   `--other
           `--basic
               +--after-side-effect
               +--computed
               +--length-name
  ```
  
  Convert this description:
  
  t is a source directory that houses 4 subdirectories. Notable ones include benchmarks, integration, smoke among others.
  
  Let me break down the layout for you:
  
  At the top level, 'benchmarks' is an empty container.
  At the main level, Inside 'integration', you'll find it sits empty.
  In the root directory, 'smoke' encapsulates 3 subfolders: operations, tests, workers.
  In nested path 'smoke → operations', 'operations' contains nothing at present.
  At level 2, in directory path 'smoke / tests', 'tests' houses 3 folders for testing purposes.
  In nested path 'smoke / tests / failover', The 'failover' repository is blank.
  Within directory hierarchy 'smoke → tests → quorum_queues', Inside 'quorum_queues', you'll find it awaits content.
  At level 3, in directory path 'smoke / tests / stamping', 'stamping' retains 1 folders: workers.
  At level 4, in directory path 'smoke → tests → stamping → workers', 'workers' is currently empty.
  Within directory hierarchy 'smoke / workers', 'workers' hosts 1 nested folders: docker.
  Within directory hierarchy 'smoke > workers > docker', The 'docker' directory is devoid of content.
  Back to the top level.
  In the root directory, 'unit' bundles 12 distinct nested folders.
  In nested path 'unit / app', 'app' holds no subdirectories at the moment.
  In nested path 'unit > apps', The 'apps' repository is barren.
  In nested path 'unit → backends', The 'backends' storage space is empty.
  In nested path 'unit > bin', 'bin' possesses 1 folders: proj.
  At level 3, in directory path 'unit > bin > proj', Inside 'proj', you'll find it is a vacant space.
  In nested path 'unit / concurrency', Inside 'concurrency', you'll find it is unpopulated.
  At level 2, in directory path 'unit / contrib', 'contrib' shelters 2 nested folders: django, proj.
  In nested path 'unit / contrib / django', The 'django' collection has yet to be populated.
  At level 3, in directory path 'unit / contrib / proj', Inside 'proj', you'll find it has yet to be populated.
  In nested path 'unit > events', The 'events' directory lacks any subdirectories.
  In nested path 'unit > fixups', The 'fixups' section hasn't been filled with any content.
  At level 2, in directory path 'unit / security', 'security' contains no subdirectories.
  In nested path 'unit / tasks', 'tasks' is devoid of content.
  In nested path 'unit / utils', The 'utils' container is vacant.
  In nested path 'unit > worker', The 'worker' container has yet to be populated.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "t\n +--benchmarks\n +--integration\n +--smoke\n |   +--operations\n |   +--tests\n |   |   +--failover\n |   |   +--quorum_queues\n |   |   `--stamping\n |   |       `--workers\n |   `--workers\n |       `--docker\n `--unit\n     +--app\n     +--apps\n     +--backends\n     +--bin\n     |   `--proj\n     +--concurrency\n     +--contrib\n     |   +--django\n     |   `--proj\n     +--events\n     +--fixups\n     +--security\n     +--tasks\n     +--utils\n     `--worker", "description": "t is a source directory that houses 4 subdirectories. Notable ones include benchmarks, integration, smoke among others.\n\nLet me break down the layout for you:\n\nAt the top level, 'benchmarks' is an empty container.\nAt the main level, Inside 'integration', you'll find it sits empty.\nIn the root directory, 'smoke' encapsulates 3 subfolders: operations, tests, workers.\nIn nested path 'smoke \u2192 operations', 'operations' contains nothing at present.\nAt level 2, in directory path 'smoke / tests', 'tests' houses 3 folders for testing purposes.\nIn nested path 'smoke / tests / failover', The 'failover' repository is blank.\nWithin directory hierarchy 'smoke \u2192 tests \u2192 quorum_queues', Inside 'quorum_queues', you'll find it awaits content.\nAt level 3, in directory path 'smoke / tests / stamping', 'stamping' retains 1 folders: workers.\nAt level 4, in directory path 'smoke \u2192 tests \u2192 stamping \u2192 workers', 'workers' is currently empty.\nWithin directory hierarchy 'smoke / workers', 'workers' hosts 1 nested folders: docker.\nWithin directory hierarchy 'smoke > workers > docker', The 'docker' directory is devoid of content.\nBack to the top level.\nIn the root directory, 'unit' bundles 12 distinct nested folders.\nIn nested path 'unit / app', 'app' holds no subdirectories at the moment.\nIn nested path 'unit > apps', The 'apps' repository is barren.\nIn nested path 'unit \u2192 backends', The 'backends' storage space is empty.\nIn nested path 'unit > bin', 'bin' possesses 1 folders: proj.\nAt level 3, in directory path 'unit > bin > proj', Inside 'proj', you'll find it is a vacant space.\nIn nested path 'unit / concurrency', Inside 'concurrency', you'll find it is unpopulated.\nAt level 2, in directory path 'unit / contrib', 'contrib' shelters 2 nested folders: django, proj.\nIn nested path 'unit / contrib / django', The 'django' collection has yet to be populated.\nAt level 3, in directory path 'unit / contrib / proj', Inside 'proj', you'll find it has yet to be populated.\nIn nested path 'unit > events', The 'events' directory lacks any subdirectories.\nIn nested path 'unit > fixups', The 'fixups' section hasn't been filled with any content.\nAt level 2, in directory path 'unit / security', 'security' contains no subdirectories.\nIn nested path 'unit / tasks', 'tasks' is devoid of content.\nIn nested path 'unit / utils', The 'utils' container is vacant.\nIn nested path 'unit > worker', The 'worker' container has yet to be populated.\n"}