What problem does it solve? Researchers often need to tweak an existing committed variation without modifying it, since committed variations are SHA-pinned and immutable. This Skill forks a committed variation into a new open variation on a pushable git branch, preserving the original while enabling further experimentation. ## Core Features & Use Cases - Git-based forking: Clones the experiment repo at the source variation's pinned SHA, cuts a variation/<id> branch, and pushes it so the user or a third-party agent can push changes with an install token. - Name resolution: Resolves plaintext variation names to the integer index the Chronicle SDK requires by matching against the experiment's variations list. - Hypothesis pre-registration: Records what the fork sets out to validate differently from the source, required before committing without an explicit override. - Use Case: You committed a baseline variation and want to test a larger batch size while keeping the baseline intact. Fork it, push your config changes to the new branch, and commit when ready. ## Quick Start Fork variation 2 of my experiment into a new variation named baseline-larger-batch with a hypothesis about improving eval accuracy.
