REFORM-To-CODE Handoff

Open repos, packages, search results, and trust snapshots directly in CODE with preserved source, score, evidence, and validation context

REFORM-To-CODE Handoff

REFORM-to-CODE handoff turns discovery into execution. When a user finds a repository, package, search result, or public trust snapshot, ReformCode can open CODE with the source context already packaged into the workspace.

What Gets Carried Into CODE

  • Source kind, target, display name, description, and source URL.
  • ReformCode Score, language, license, default branch, and evidence snapshot when available.
  • Code Genome score, status, benchmark summary, and recommended moves when the source came from trust evidence.
  • A reform objective that tells CODE whether the next move is adoption, remixing, white-labeling, starter extraction, replacement, or proof generation.
  • A validation checklist covering attribution, license review, risk review, type-check, lint, tests, build, preview smoke, and proof capture.

Workspace Files

Every handoff creates six durable context files:

  • /REFORMCODE_HANDOFF.md is the human-readable brief shown in CODE.
  • /.reformcode/handoff.json is the machine-readable handoff contract for agents, workflows, and future automation.
  • /REFORMCODE_RECIPE_PLAN.md is the ranked reform-recipe plan with selected recipe, alternatives, workflow stages, validation commands, guardrails, and missing inputs.
  • /.reformcode/reform-recipes.json is the machine-readable recipe marketplace contract for CODE agents and future governance memory.
  • /REFORMCODE_WHITE_LABEL_PLAN.md is the reviewable white-label plan for brand, package, domain, env, docs, metadata, asset, and attribution changes.
  • /.reformcode/white-label-plan.json is the machine-readable white-label plan for agents, workflows, recipes, and governance memory.

Repository transfers also include selected source files from the repo snapshot, with the active file opened beside the handoff brief.

Entry Points

  • Repository pages use the primary Open in CODE action to transfer selected repo files plus handoff context.
  • Package detail pages open CODE with package score, trust, license, and integration objective.
  • GitHub and NPM search results open CODE without requiring a detail-page detour.
  • Public Trust Network pages open CODE with Code Genome and evidence snapshot context.
  • REFORM Recipes open CODE with a selected curated recipe and ranked alternatives for starter extraction, white-labeling, migrations, dependency replacements, partner templates, or Code Genome decisions.

Why It Matters

This makes REFORM and CODE feel like two modes of one product. REFORM chooses and qualifies source material; CODE receives a prepared workspace that can continue into generation, editing, validation, Git, preview, deploy proof, and white-label reform.

Developer Notes

Use createReformToCodeHandoffHref() for URL handoffs and createReformToCodeHandoff() for workspace transfers. CODE consumes parseReformToCodeHandoffSearchParams() on /code and creates a builder workspace with origin: 'reform'.