Reproducing Folded H Magic State Cultivation

Expected inputs:

• whether the target is sample-circuit inspection, handoff execution, or data comparison,
• physical-noise setting,
• whether the user wants distance-3 examples or a generalized plan.

Expected outputs:

• a folded-H workflow plan,
• the relevant repo entry point,
• explicit limits of current support,
• a comparison note against the original cultivation repo when helpful.

Assumptions to make explicit:

• only stabilizer-based escape is currently supported upstream,
• much of the repo is notebook-driven,
• the HPC-oriented handoff script expects a p value and a task number.

Standard Workflow Checklist

1. Read references/repo-structure-and-workflow.md.
2. Decide whether the task starts from sample_circuits, data, or the handoff script.
3. Treat src as the main implementation area and the notebook content as exploratory support.
4. Keep folded-H specific assumptions separate from the older cultivation repo's assumptions.
5. If the goal is adaptation, identify what depends on folded-transversal Hadamard specifically and what is generic cultivation infrastructure.

Validation Loop

Before closing work:

1. confirm the task stays within the currently supported escape path unless explicitly extending it,
2. confirm the chosen entry point is explicit,
3. confirm any performance claim is tied to either data/ outputs or a new named run,
4. confirm differences from the original cultivation workflow are stated, not implied.

Common Issues And Fixes

Assuming full feature parity with the original cultivation repo

Problem: the plan assumes every earlier cultivation option already exists here.

Fix: restate the repo's narrower current support, especially the stabilizer-based escape boundary.

Notebook-only reproduction

Problem: the workflow depends entirely on notebook state.

Fix: anchor the plan around sample_circuits, src, or handoff_run_3err.py.

Hidden HPC assumptions

Problem: the handoff path is described as if it were a single local interactive run.

Fix: note the upstream script's parallelized task-number interface explicitly.

References

• references/api.md
• references/examples.md
• references/repo-structure-and-workflow.md
• ../reproducing-magic-state-cultivation-workflows/SKILL.md
• ../../docs/TOOLKIT_REGISTRY.md