Skip to content

Instantly share code, notes, and snippets.

@belisarius222
Last active April 3, 2026 23:23
Show Gist options
  • Select an option

  • Save belisarius222/4d437dcbdda9f913ef790a63c5fa96f6 to your computer and use it in GitHub Desktop.

Select an option

Save belisarius222/4d437dcbdda9f913ef790a63c5fa96f6 to your computer and use it in GitHub Desktop.
volta-loop example in paragraph format

volta-loop

main(experiment_name, git_repo)

LABEL: implement

let commit_hash = AWAIT FORK implement-experiment experiment_name fail_path?.

let setup_ok = AWAIT FORK setup-experiment commit_hash.

IF not setup_ok?

GOTO implement, and pass setup_ok.fail_path to the sub-agent.

AWAIT FORK run-experiment.

AWAIT FORK eval-experiment.

implement-experiment(experiment_name, fail_path?)

Write the experiment code. IF fail_path is set, read that folder to understand what went wrong with the previous implementation.

LABEL: review

Have Codex CLI review code, using gpt-5.4 on xhigh reasoning, in a fresh session.

IF codex did not find medium- or higher-priority issues,

RETURN git commit hash.

Fix all issues that Codex flagged.

Git commit and push.

GOTO review.

setup-experiment(commit_hash)

Load code at commit_hash onto experiment machine(s).

LABEL: pre_flight_checks

Run the experiment's smoke test.

IF the smoke test passed,

RETURN ok.

let fail_path = AWAIT FORK "write_failure_folder"

Write a folder that captures as much information as possible about what went wrong. Use a filepath that is unique and searchable later, i.e. it includes experiment_name, git_repo, machine id(s), and datetime.

RETURN filepath of the folder you just wrote.

IF it failed due to a code issue rather than just a machine configuration problem,

RETURN failed, with fail_path.

Try to fix the machine configuration.

IF you were able to fix the machine configuration,

GOTO pre_flight_checks.

run-experiment

TODO

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment