prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  ws
   +--__snapshots__
   `--test
       `--__snapshots__
  ```
  
  Convert this description:
  
  internal is a head directory that holds 7 subdirectories. Notable ones include component, locking, management among others.
  
  Let me break down the system for you:
  
  In the root directory, 'component' retains 4 some subdirectory elements.
  At level 2, in directory path 'component > external', 'external' contains 2 folders: descriptor, model.
  At level 3, in directory path 'component / external / descriptor', 'descriptor' awaits content.
  Within directory hierarchy 'component > external > model', 'model' encompasses 2 subfolders: ivy, maven.
  In nested path 'component > external > model > ivy', 'ivy' has nothing inside.
  Within directory hierarchy 'component > external > model > maven', 'maven' is an empty container.
  In nested path 'component > local', 'local' holds 1 subdirectory elements: model.
  At level 3, in directory path 'component > local > model', Inside 'model', you'll find it is an empty container.
  In nested path 'component → model', The 'model' repository is currently empty.
  In nested path 'component → resolution', 'resolution' maintains 1 directories: failure.
  In nested path 'component > resolution > failure', 'failure' organizes 6 a few directories.
  At level 4, in directory path 'component / resolution / failure / describer', The 'describer' folder has yet to be populated.
  Within directory hierarchy 'component / resolution / failure / exception', 'exception' is currently empty.
  At level 4, in directory path 'component / resolution / failure / formatting', Inside 'formatting', you'll find it is an empty container.
  Within directory hierarchy 'component > resolution > failure > interfaces', The 'interfaces' container has no content.
  At level 4, in directory path 'component / resolution / failure / transform', Inside 'transform', you'll find it appears to be unused.
  At level 4, in directory path 'component / resolution / failure / type', The 'type' storage space awaits content.
  In the root directory, Inside 'locking', you'll find it has no content.
  In the root directory, The 'management' collection is currently empty.
  At the top level, 'resolve' features 3 nested folders: caching, resolver, result.
  Within directory hierarchy 'resolve > caching', Inside 'caching', you'll find it stands empty.
  Within directory hierarchy 'resolve → resolver', 'resolver' hasn't been filled with any content.
  In nested path 'resolve / result', Inside 'result', you'll find it has nothing inside.
  Back to the top level.
  At the main level, 'resource' possesses 4 diverse directory entries.
  At level 2, in directory path 'resource → cached', Inside 'cached', you'll find it appears to be unused.
  In nested path 'resource > local', 'local' stores 1 subdirectories: ivy.
  Within directory hierarchy 'resource / local / ivy', Inside 'ivy', you'll find it appears to be unused.
  Within directory hierarchy 'resource / transfer', 'transfer' stands empty.
  At level 2, in directory path 'resource → transport', 'transport' encompasses 1 subdirectory elements: file.
  In nested path 'resource / transport / file', The 'file' folder is a vacant space.
  In the root directory, Inside 'rules', you'll find it lacks any subdirectories.
  At the top level, 'service' maintains 1 nested folders: scopes.
  In nested path 'service > scopes', 'scopes' hasn't been filled with any content.
  Back to the top level.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "internal\n +--component\n |   +--external\n |   |   +--descriptor\n |   |   `--model\n |   |       +--ivy\n |   |       `--maven\n |   +--local\n |   |   `--model\n |   +--model\n |   `--resolution\n |       `--failure\n |           +--describer\n |           +--exception\n |           +--formatting\n |           +--interfaces\n |           +--transform\n |           `--type\n +--locking\n +--management\n +--resolve\n |   +--caching\n |   +--resolver\n |   `--result\n +--resource\n |   +--cached\n |   +--local\n |   |   `--ivy\n |   +--transfer\n |   `--transport\n |       `--file\n +--rules\n `--service\n     `--scopes", "description": "internal is a head directory that holds 7 subdirectories. Notable ones include component, locking, management among others.\n\nLet me break down the system for you:\n\nIn the root directory, 'component' retains 4 some subdirectory elements.\nAt level 2, in directory path 'component > external', 'external' contains 2 folders: descriptor, model.\nAt level 3, in directory path 'component / external / descriptor', 'descriptor' awaits content.\nWithin directory hierarchy 'component > external > model', 'model' encompasses 2 subfolders: ivy, maven.\nIn nested path 'component > external > model > ivy', 'ivy' has nothing inside.\nWithin directory hierarchy 'component > external > model > maven', 'maven' is an empty container.\nIn nested path 'component > local', 'local' holds 1 subdirectory elements: model.\nAt level 3, in directory path 'component > local > model', Inside 'model', you'll find it is an empty container.\nIn nested path 'component \u2192 model', The 'model' repository is currently empty.\nIn nested path 'component \u2192 resolution', 'resolution' maintains 1 directories: failure.\nIn nested path 'component > resolution > failure', 'failure' organizes 6 a few directories.\nAt level 4, in directory path 'component / resolution / failure / describer', The 'describer' folder has yet to be populated.\nWithin directory hierarchy 'component / resolution / failure / exception', 'exception' is currently empty.\nAt level 4, in directory path 'component / resolution / failure / formatting', Inside 'formatting', you'll find it is an empty container.\nWithin directory hierarchy 'component > resolution > failure > interfaces', The 'interfaces' container has no content.\nAt level 4, in directory path 'component / resolution / failure / transform', Inside 'transform', you'll find it appears to be unused.\nAt level 4, in directory path 'component / resolution / failure / type', The 'type' storage space awaits content.\nIn the root directory, Inside 'locking', you'll find it has no content.\nIn the root directory, The 'management' collection is currently empty.\nAt the top level, 'resolve' features 3 nested folders: caching, resolver, result.\nWithin directory hierarchy 'resolve > caching', Inside 'caching', you'll find it stands empty.\nWithin directory hierarchy 'resolve \u2192 resolver', 'resolver' hasn't been filled with any content.\nIn nested path 'resolve / result', Inside 'result', you'll find it has nothing inside.\nBack to the top level.\nAt the main level, 'resource' possesses 4 diverse directory entries.\nAt level 2, in directory path 'resource \u2192 cached', Inside 'cached', you'll find it appears to be unused.\nIn nested path 'resource > local', 'local' stores 1 subdirectories: ivy.\nWithin directory hierarchy 'resource / local / ivy', Inside 'ivy', you'll find it appears to be unused.\nWithin directory hierarchy 'resource / transfer', 'transfer' stands empty.\nAt level 2, in directory path 'resource \u2192 transport', 'transport' encompasses 1 subdirectory elements: file.\nIn nested path 'resource / transport / file', The 'file' folder is a vacant space.\nIn the root directory, Inside 'rules', you'll find it lacks any subdirectories.\nAt the top level, 'service' maintains 1 nested folders: scopes.\nIn nested path 'service > scopes', 'scopes' hasn't been filled with any content.\nBack to the top level.\n"}