prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  fixtures
   +--behavior
   |   +--get-with-falsy-receiver
   |   `--get-without-receiver
   +--dependencies
   |   +--basic
   |   +--deep
   |   +--missing
   |   +--multiple
   |   +--rename-binding-equal
   |   +--rename-deep-global
   |   +--reuse-dependency
   |   `--variable-same-name-dependency
   `--misc
       +--9496
  ```
  
  Convert this description:
  
  ivyservice is a base directory that encompasses 7 subdirectories. Notable ones include dependencysubstitution, ivyresolve, modulecache among others.
  
  Let me break down the configuration for you:
  
  At the top level, The 'dependencysubstitution' container sits empty.
  At the top level, 'ivyresolve' retains 3 subdirectories: parser, strategy, verification.
  At level 2, in directory path 'ivyresolve → parser', 'parser' encompasses 1 subfolders: data.
  At level 3, in directory path 'ivyresolve > parser > data', 'data' is devoid of content.
  In nested path 'ivyresolve → strategy', Inside 'strategy', you'll find it lacks any subdirectories.
  Within directory hierarchy 'ivyresolve / verification', 'verification' shelters 2 subdirectory elements: report, writer.
  At level 3, in directory path 'ivyresolve → verification → report', The 'report' folder has nothing inside.
  In nested path 'ivyresolve / verification / writer', Inside 'writer', you'll find it is a vacant space.
  Back to the top level.
  At the top level, 'modulecache' contains 2 folders: artifacts, dynamicversions.
  At level 2, in directory path 'modulecache / artifacts', Inside 'artifacts', you'll find it contains nothing at present.
  In nested path 'modulecache → dynamicversions', The 'dynamicversions' collection has no content.
  Back to the top level.
  In the root directory, 'moduleconverter' holds 1 contained folders: dependencies.
  At level 2, in directory path 'moduleconverter → dependencies', Inside 'dependencies', you'll find it has no folders inside.
  Back to the top level.
  At the top level, Inside 'projectmodule', you'll find it has no content.
  At the top level, 'resolutionstrategy' has no content.
  At the main level, 'resolveengine' holds 5 distinct nested folders.
  At level 2, in directory path 'resolveengine > artifact', Inside 'artifact', you'll find it lacks any subdirectories.
  At level 2, in directory path 'resolveengine → excludes', 'excludes' features 2 contained folders: factories, simple.
  In nested path 'resolveengine → excludes → factories', 'factories' awaits content.
  In nested path 'resolveengine > excludes > simple', 'simple' hasn't been filled with any content.
  In nested path 'resolveengine / graph', 'graph' retains 4 numerous subdirectory elements.
  In nested path 'resolveengine / graph / builder', The 'builder' storage space awaits content.
  Within directory hierarchy 'resolveengine > graph > conflicts', 'conflicts' is devoid of content.
  In nested path 'resolveengine → graph → results', 'results' is an empty container.
  In nested path 'resolveengine → graph → selectors', Inside 'selectors', you'll find it has no folders inside.
  Within directory hierarchy 'resolveengine → result', Inside 'result', you'll find it remains unused.
  At level 2, in directory path 'resolveengine → store', 'store' has no folders inside.
  Back to the top level.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "ivyservice\n +--dependencysubstitution\n +--ivyresolve\n |   +--parser\n |   |   `--data\n |   +--strategy\n |   `--verification\n |       +--report\n |       `--writer\n +--modulecache\n |   +--artifacts\n |   `--dynamicversions\n +--moduleconverter\n |   `--dependencies\n +--projectmodule\n +--resolutionstrategy\n `--resolveengine\n     +--artifact\n     +--excludes\n     |   +--factories\n     |   `--simple\n     +--graph\n     |   +--builder\n     |   +--conflicts\n     |   +--results\n     |   `--selectors\n     +--result\n     `--store", "description": "ivyservice is a base directory that encompasses 7 subdirectories. Notable ones include dependencysubstitution, ivyresolve, modulecache among others.\n\nLet me break down the configuration for you:\n\nAt the top level, The 'dependencysubstitution' container sits empty.\nAt the top level, 'ivyresolve' retains 3 subdirectories: parser, strategy, verification.\nAt level 2, in directory path 'ivyresolve \u2192 parser', 'parser' encompasses 1 subfolders: data.\nAt level 3, in directory path 'ivyresolve > parser > data', 'data' is devoid of content.\nIn nested path 'ivyresolve \u2192 strategy', Inside 'strategy', you'll find it lacks any subdirectories.\nWithin directory hierarchy 'ivyresolve / verification', 'verification' shelters 2 subdirectory elements: report, writer.\nAt level 3, in directory path 'ivyresolve \u2192 verification \u2192 report', The 'report' folder has nothing inside.\nIn nested path 'ivyresolve / verification / writer', Inside 'writer', you'll find it is a vacant space.\nBack to the top level.\nAt the top level, 'modulecache' contains 2 folders: artifacts, dynamicversions.\nAt level 2, in directory path 'modulecache / artifacts', Inside 'artifacts', you'll find it contains nothing at present.\nIn nested path 'modulecache \u2192 dynamicversions', The 'dynamicversions' collection has no content.\nBack to the top level.\nIn the root directory, 'moduleconverter' holds 1 contained folders: dependencies.\nAt level 2, in directory path 'moduleconverter \u2192 dependencies', Inside 'dependencies', you'll find it has no folders inside.\nBack to the top level.\nAt the top level, Inside 'projectmodule', you'll find it has no content.\nAt the top level, 'resolutionstrategy' has no content.\nAt the main level, 'resolveengine' holds 5 distinct nested folders.\nAt level 2, in directory path 'resolveengine > artifact', Inside 'artifact', you'll find it lacks any subdirectories.\nAt level 2, in directory path 'resolveengine \u2192 excludes', 'excludes' features 2 contained folders: factories, simple.\nIn nested path 'resolveengine \u2192 excludes \u2192 factories', 'factories' awaits content.\nIn nested path 'resolveengine > excludes > simple', 'simple' hasn't been filled with any content.\nIn nested path 'resolveengine / graph', 'graph' retains 4 numerous subdirectory elements.\nIn nested path 'resolveengine / graph / builder', The 'builder' storage space awaits content.\nWithin directory hierarchy 'resolveengine > graph > conflicts', 'conflicts' is devoid of content.\nIn nested path 'resolveengine \u2192 graph \u2192 results', 'results' is an empty container.\nIn nested path 'resolveengine \u2192 graph \u2192 selectors', Inside 'selectors', you'll find it has no folders inside.\nWithin directory hierarchy 'resolveengine \u2192 result', Inside 'result', you'll find it remains unused.\nAt level 2, in directory path 'resolveengine \u2192 store', 'store' has no folders inside.\nBack to the top level.\n"}