TheOnlyFusionCube How
Build an evidence-backed explanation of how the requested subsystem works.
- Find the public/consumer entry point, then trace data and control flow toward the effect. Do not start from filenames guessed by name alone.
- Read the core types and state ownership before narrating individual functions.
- Use
vcs, tests, orobservewhen they resolve an ambiguity. Ifdelegateexists, split independent exploration areas and reconcile them yourself. - Draw a compact text or Mermaid diagram when it reduces reader load.
- Test at least one claim that could easily be wrong by running or inspecting the real path.
- Explain in consumer order: trigger -> boundary -> state/transform -> side effect -> observable result. Name file/symbol evidence and uncertainty.