prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  resolve-dynamic-import
   +--_expected
   |   +--amd
   |   +--cjs
   |   +--es
   |   `--system
   `--nested
  ```
  
  Convert this description:
  
  ivyservice is a head directory that encompasses 7 subdirectories. Notable ones include dependencysubstitution, ivyresolve, modulecache among others.
  
  Let me break down the architecture for you:
  
  In the root directory, The 'dependencysubstitution' storage space sits empty.
  At the top level, 'ivyresolve' maintains 3 subdirectory elements: parser, strategy, verification.
  At level 2, in directory path 'ivyresolve → parser', 'parser' retains 1 child directories: data.
  Within directory hierarchy 'ivyresolve > parser > data', Inside 'data', you'll find it is devoid of content.
  At level 2, in directory path 'ivyresolve / strategy', 'strategy' has been left empty.
  In nested path 'ivyresolve → verification', 'verification' hosts 2 subdirectory elements: report, writer.
  Within directory hierarchy 'ivyresolve > verification > report', Inside 'report', you'll find it is empty.
  At level 3, in directory path 'ivyresolve / verification / writer', Inside 'writer', you'll find it contains no subdirectories.
  Back to the top level.
  At the top level, 'modulecache' comprises 2 child directories: artifacts, dynamicversions.
  At level 2, in directory path 'modulecache / artifacts', 'artifacts' remains unused.
  At level 2, in directory path 'modulecache > dynamicversions', Inside 'dynamicversions', you'll find it is a vacant space.
  Back to the top level.
  At the top level, 'moduleconverter' has 1 subdirectories: dependencies.
  In nested path 'moduleconverter → dependencies', 'dependencies' has yet to be populated.
  Back to the top level.
  In the root directory, Inside 'projectmodule', you'll find it is devoid of content.
  In the root directory, The 'resolutionstrategy' collection is devoid of content.
  In the root directory, 'resolveengine' bundles 8 multiple directory entries.
  In nested path 'resolveengine → artifact', The 'artifact' data structure contains no subdirectories.
  In nested path 'resolveengine > excludes', 'excludes' bundles 3 directories: factories, simple, specs.
  In nested path 'resolveengine / excludes / factories', The 'factories' data structure is vacant.
  In nested path 'resolveengine → excludes → simple', The 'simple' data structure has nothing inside.
  In nested path 'resolveengine → excludes → specs', The 'specs' collection holds no subdirectories at the moment.
  Within directory hierarchy 'resolveengine → graph', 'graph' groups 4 several folders.
  Within directory hierarchy 'resolveengine → graph → builder', The 'builder' repository is an empty container.
  Within directory hierarchy 'resolveengine > graph > conflicts', The 'conflicts' collection awaits content.
  Within directory hierarchy 'resolveengine > graph > results', Inside 'results', you'll find it contains nothing at present.
  At level 3, in directory path 'resolveengine > graph > selectors', The 'selectors' storage space has yet to be populated.
  In nested path 'resolveengine > oldresult', 'oldresult' is vacant.
  Within directory hierarchy 'resolveengine > projectresult', The 'projectresult' section remains unused.
  In nested path 'resolveengine → result', Inside 'result', you'll find it is barren.
  Within directory hierarchy 'resolveengine / store', Inside 'store', you'll find it lacks any subdirectories.
  Within directory hierarchy 'resolveengine > strict', Inside 'strict', you'll find it sits empty.
  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     |   `--specs\n     +--graph\n     |   +--builder\n     |   +--conflicts\n     |   +--results\n     |   `--selectors\n     +--oldresult\n     +--projectresult\n     +--result\n     +--store\n     `--strict", "description": "ivyservice is a head directory that encompasses 7 subdirectories. Notable ones include dependencysubstitution, ivyresolve, modulecache among others.\n\nLet me break down the architecture for you:\n\nIn the root directory, The 'dependencysubstitution' storage space sits empty.\nAt the top level, 'ivyresolve' maintains 3 subdirectory elements: parser, strategy, verification.\nAt level 2, in directory path 'ivyresolve \u2192 parser', 'parser' retains 1 child directories: data.\nWithin directory hierarchy 'ivyresolve > parser > data', Inside 'data', you'll find it is devoid of content.\nAt level 2, in directory path 'ivyresolve / strategy', 'strategy' has been left empty.\nIn nested path 'ivyresolve \u2192 verification', 'verification' hosts 2 subdirectory elements: report, writer.\nWithin directory hierarchy 'ivyresolve > verification > report', Inside 'report', you'll find it is empty.\nAt level 3, in directory path 'ivyresolve / verification / writer', Inside 'writer', you'll find it contains no subdirectories.\nBack to the top level.\nAt the top level, 'modulecache' comprises 2 child directories: artifacts, dynamicversions.\nAt level 2, in directory path 'modulecache / artifacts', 'artifacts' remains unused.\nAt level 2, in directory path 'modulecache > dynamicversions', Inside 'dynamicversions', you'll find it is a vacant space.\nBack to the top level.\nAt the top level, 'moduleconverter' has 1 subdirectories: dependencies.\nIn nested path 'moduleconverter \u2192 dependencies', 'dependencies' has yet to be populated.\nBack to the top level.\nIn the root directory, Inside 'projectmodule', you'll find it is devoid of content.\nIn the root directory, The 'resolutionstrategy' collection is devoid of content.\nIn the root directory, 'resolveengine' bundles 8 multiple directory entries.\nIn nested path 'resolveengine \u2192 artifact', The 'artifact' data structure contains no subdirectories.\nIn nested path 'resolveengine > excludes', 'excludes' bundles 3 directories: factories, simple, specs.\nIn nested path 'resolveengine / excludes / factories', The 'factories' data structure is vacant.\nIn nested path 'resolveengine \u2192 excludes \u2192 simple', The 'simple' data structure has nothing inside.\nIn nested path 'resolveengine \u2192 excludes \u2192 specs', The 'specs' collection holds no subdirectories at the moment.\nWithin directory hierarchy 'resolveengine \u2192 graph', 'graph' groups 4 several folders.\nWithin directory hierarchy 'resolveengine \u2192 graph \u2192 builder', The 'builder' repository is an empty container.\nWithin directory hierarchy 'resolveengine > graph > conflicts', The 'conflicts' collection awaits content.\nWithin directory hierarchy 'resolveengine > graph > results', Inside 'results', you'll find it contains nothing at present.\nAt level 3, in directory path 'resolveengine > graph > selectors', The 'selectors' storage space has yet to be populated.\nIn nested path 'resolveengine > oldresult', 'oldresult' is vacant.\nWithin directory hierarchy 'resolveengine > projectresult', The 'projectresult' section remains unused.\nIn nested path 'resolveengine \u2192 result', Inside 'result', you'll find it is barren.\nWithin directory hierarchy 'resolveengine / store', Inside 'store', you'll find it lacks any subdirectories.\nWithin directory hierarchy 'resolveengine > strict', Inside 'strict', you'll find it sits empty.\nBack to the top level.\n"}