prompt: Your task is to convert the following English description into an ASCII tree format.
  
  launcher is a core directory that gathers 5 subdirectories. Notable ones include bootstrap, cli, continuous among others.
  
  Let me break down the construction for you:
  
  At the top level, Inside 'bootstrap', you'll find it is vacant.
  At the main level, 'cli' stores 1 directories: converter.
  At level 2, in directory path 'cli / converter', Inside 'converter', you'll find it is a vacant space.
  In the root directory, The 'continuous' folder has no content.
  At the main level, 'daemon' holds 3 subdirectory elements: protocol, registry, server.
  In nested path 'daemon → protocol', The 'protocol' container has no content.
  In nested path 'daemon → registry', The 'registry' container is an empty container.
  Within directory hierarchy 'daemon / server', 'server' stores 4 some child directories.
  At level 3, in directory path 'daemon > server > exec', The 'exec' container remains unused.
  In nested path 'daemon / server / expiry', Inside 'expiry', you'll find it is an empty container.
  At level 3, in directory path 'daemon > server > health', 'health' includes 1 subdirectories: gc.
  At level 4, in directory path 'daemon → server → health → gc', Inside 'gc', you'll find it appears to be unused.
  In nested path 'daemon → server → scaninfo', The 'scaninfo' container appears to be unused.
  Back to the top level.
  In the root directory, Inside 'exec', you'll find it appears to be unused.
  
  
  Format your response in 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
  ```
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "launcher\n +--bootstrap\n +--cli\n |   `--converter\n +--continuous\n +--daemon\n |   +--protocol\n |   +--registry\n |   `--server\n |       +--exec\n |       +--expiry\n |       +--health\n |       |   `--gc\n |       `--scaninfo\n `--exec", "description": "launcher is a core directory that gathers 5 subdirectories. Notable ones include bootstrap, cli, continuous among others.\n\nLet me break down the construction for you:\n\nAt the top level, Inside 'bootstrap', you'll find it is vacant.\nAt the main level, 'cli' stores 1 directories: converter.\nAt level 2, in directory path 'cli / converter', Inside 'converter', you'll find it is a vacant space.\nIn the root directory, The 'continuous' folder has no content.\nAt the main level, 'daemon' holds 3 subdirectory elements: protocol, registry, server.\nIn nested path 'daemon \u2192 protocol', The 'protocol' container has no content.\nIn nested path 'daemon \u2192 registry', The 'registry' container is an empty container.\nWithin directory hierarchy 'daemon / server', 'server' stores 4 some child directories.\nAt level 3, in directory path 'daemon > server > exec', The 'exec' container remains unused.\nIn nested path 'daemon / server / expiry', Inside 'expiry', you'll find it is an empty container.\nAt level 3, in directory path 'daemon > server > health', 'health' includes 1 subdirectories: gc.\nAt level 4, in directory path 'daemon \u2192 server \u2192 health \u2192 gc', Inside 'gc', you'll find it appears to be unused.\nIn nested path 'daemon \u2192 server \u2192 scaninfo', The 'scaninfo' container appears to be unused.\nBack to the top level.\nIn the root directory, Inside 'exec', you'll find it appears to be unused.\n"}