genomeft-proposal

name	genomeft-proposal
description	Use when a GenomeHarness v15 campaign has pending PROPOSE requests and proposal JSON must be written from request packets.

GenomeHarness Proposal

Use plans/genomeharness_v15_plan.md as the active authority.

Input

Read only the pending PROPOSE packet(s) from campaigns/X/packets/. Each packet contains:

• request_id
• slot_id
• selected_parent_id
• selected_path
• uct_trace
• root/best/leaderboard/running context
• allowed patch fields
• forbidden changes
• remaining launch time

Do not read test data or raw logs unless the packet explicitly points to a small summary.

Output Schema

Write one JSON file under the campaign proposals/ directory:

{
  "responses": [
    {
      "request_id": "req_0007",
      "parent_node_id": "n_0002",
      "proposal_name": "short_snake_case_name",
      "primary_focus": "lr",
      "recipe_patch": {
        "learning_rate": 5e-5,
        "warmup_steps": 100
      },
      "rationale": "Brief evidence-backed reason."
    }
  ]
}

You may answer multiple pending requests in one file. Each response must use the request's selected parent.

Rules

• Codex proposes concrete recipe patches; the harness validates, deduplicates, schedules, and executes.
• Compound patches are allowed when scientifically justified.
• Do not include v14 fields: axis, changed_axes, granularity, edit_radius, family_key, action_family, or suggested_min_fidelity.
• Do not modify split, labels, primary metric, test protocol, trainer code, budget, patience, or search deadline.
• Do not access test or use test information.
• Bootstrap: avoid repeating an accepted primary_focus within the same bootstrap group unless the harness retry relaxation has been reached.
• Do not create weak proposals merely to fill GPUs.
• Prefer proposals that improve validation MCC under full-data train->validation, not cheap proxy scores.

Submission

After writing the JSON:

genharness submit-proposals --campaign campaigns/X --proposal campaigns/X/proposals/proposal_XXXX.json

If the request expired, stale, or rejected, read the returned replacement request and respond to that new request.