Explore Code

This is for when you want Claude to try exploratory changes in a deep learning codebase without touching your trusted baseline. It works on isolated branches to transplant modules, swap backbones, add LoRA layers, or stitch together low-risk migration ideas. Everything goes into `explore_outputs/` with rollback instructions and clear candidate status. It's explicitly not for baseline reproduction, conservative debugging, or anything that needs verification rigor. The boundaries are sharp: you must authorize the exploration, the code stays isolated, and the output is always treated as a candidate. Useful when you want to prototype architectural changes quickly while keeping a clear separation from production research code.