prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  test
   +--__snapshots__
   +--fixtures
   |   `--has-vulnerabilities
   `--utils
       `--responses
  ```
  
  Convert this description:
  
  internal is a head directory that incorporates 5 subdirectories. Notable ones include adapter, build, consumer among others.
  
  Let me break down the hierarchy for you:
  
  At the top level, 'adapter' has no content.
  At the main level, 'build' remains unused.
  At the top level, 'consumer' features 6 various directories.
  In nested path 'consumer → async', 'async' has nothing inside.
  In nested path 'consumer / connection', The 'connection' directory is empty.
  At level 2, in directory path 'consumer → converters', The 'converters' section has been left empty.
  At level 2, in directory path 'consumer → loader', 'loader' is an empty container.
  In nested path 'consumer / parameters', The 'parameters' container remains unused.
  Within directory hierarchy 'consumer > versioning', 'versioning' remains unused.
  Back to the top level.
  At the main level, The 'gradle' container is blank.
  At the top level, 'protocol' groups 5 assorted subdirectory elements.
  In nested path 'protocol → cpp', The 'cpp' collection is barren.
  Within directory hierarchy 'protocol / events', Inside 'events', you'll find it sits empty.
  In nested path 'protocol > exceptions', 'exceptions' appears to be unused.
  At level 2, in directory path 'protocol > problem', 'problem' is unpopulated.
  At level 2, in directory path 'protocol / test', 'test' is vacant.
  Back to the top level.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "internal\n +--adapter\n +--build\n +--consumer\n |   +--async\n |   +--connection\n |   +--converters\n |   +--loader\n |   +--parameters\n |   `--versioning\n +--gradle\n `--protocol\n     +--cpp\n     +--events\n     +--exceptions\n     +--problem\n     `--test", "description": "internal is a head directory that incorporates 5 subdirectories. Notable ones include adapter, build, consumer among others.\n\nLet me break down the hierarchy for you:\n\nAt the top level, 'adapter' has no content.\nAt the main level, 'build' remains unused.\nAt the top level, 'consumer' features 6 various directories.\nIn nested path 'consumer \u2192 async', 'async' has nothing inside.\nIn nested path 'consumer / connection', The 'connection' directory is empty.\nAt level 2, in directory path 'consumer \u2192 converters', The 'converters' section has been left empty.\nAt level 2, in directory path 'consumer \u2192 loader', 'loader' is an empty container.\nIn nested path 'consumer / parameters', The 'parameters' container remains unused.\nWithin directory hierarchy 'consumer > versioning', 'versioning' remains unused.\nBack to the top level.\nAt the main level, The 'gradle' container is blank.\nAt the top level, 'protocol' groups 5 assorted subdirectory elements.\nIn nested path 'protocol \u2192 cpp', The 'cpp' collection is barren.\nWithin directory hierarchy 'protocol / events', Inside 'events', you'll find it sits empty.\nIn nested path 'protocol > exceptions', 'exceptions' appears to be unused.\nAt level 2, in directory path 'protocol > problem', 'problem' is unpopulated.\nAt level 2, in directory path 'protocol / test', 'test' is vacant.\nBack to the top level.\n"}