Contributing

You’ve finished Validation and the Auditor pass and want to ship your patch. In a fresh coding-agent session from the task directory, paste:

386 lines · 33,844 chars View →

That’s the whole contribution flow. The agent turns your validated pipeline/run.{py,R} into an AutoZyme patch, runs package-level attest, and opens the PR.

Time: plan on a few hours. The code lift is the small part — zyme attest dominates the wall-clock, measuring every data tier across the full thread sweep at the default 2 reps each (auto-escalating to 3 on a noisy cell). Longer still if attest exposes a real mismatch you need to debug.

Before you run it:

  • Validation has passed
  • the converged implementation lives in pipeline/run.{py,R}

What the agent does:

  • moves the fast implementation into autozyme_py/ or autozyme_r/
  • registers the patch so users can call autozyme.activate("<name>")
  • adds the manifest/catalog metadata needed for discovery
  • runs zyme attest (default --reps 2)
  • opens a PR with the verification table and summary

What to watch for:

  • package_verify.tsv is written in the task directory
  • every required attest row passes
  • the PR body includes the patch name, tested upstream version, speedup table, and any platform notes

If attest fails, let the agent debug the package lift. Do not loosen task.yaml thresholds to make a failure pass; that changes the claim instead of fixing the patch.

After the PR opens: CI reruns the checks, then a maintainer reviews the binding, smoke recipe, concordance gate, and metadata. Once merged, your name goes into the CITATION.cff contributors field, contributors.md, and the patch catalog (the first two are created on the first merged external contribution) — see Credit & citation.