1. Pick a workflow
Choose either the single-experiment workflow or a preset experiment-set workflow in GitHub Actions.
This page is the lightweight browser guide for the GitHub Actions runner behind the AbTweak restoration. It uses the same curated experiment vocabulary as the local harness, so you can trigger safe runs, reports, and trace workflows remotely and download the results as artifacts.
Choose either the single-experiment workflow or a preset experiment-set workflow in GitHub Actions.
Use only the predefined harness names listed below. No arbitrary shell or Lisp input is accepted.
Each run publishes a compact summary plus plain output, JSON output where available, and trace artifacts for trace workflows.
Use the Remote experiment workflow with:
blocks-sussman-abtweak blocks-sussman-tweak hanoi2-abtweak hanoi3-abtweak hanoi4-5peg-isbm-weak-pos-lw robot2-abtweak stylistics-abtweak
benchmark-status hanoi2-historical hanoi3-historical hanoi4-historical hanoi4-solve-candidates hanoi4-score-sensitivity wide-domain-sweep
hanoi3 hanoi4 hanoi4-isbm-weak-pos-lw hanoi4-legacy-1991
Runs the short status summary plus the benchmark-status report. Best for a quick “where are we now?” check.
Runs the current narrow `hanoi-4` comparison set: solve candidates, historical-control report, and score-sensitivity report.
Runs the lower-Hanoi publication-facing reports and the benchmark-status report.
A short markdown summary appears directly in the GitHub Actions run view.
When the underlying harness supports it, the artifact bundle includes JSON alongside the plain run or report output.
Trace workflows include the copied trace directory so you can inspect frontier, score, and lineage outputs offline.