← Files MathboxARCHIVED FILE

skills/research-program/references/handoff.md

2.05 KB · Oct 2, 2026 · 00:32 UTC

↓ Download file

# Minimal research handoff

Supply the exact target, definitions/conventions, applicable instructions and
raw artifacts needed for the next mathematical move. Use claim and route IDs
when the project has them. Include failed steps relevant to continuation, not a
transcript of every attempt.
When a program closeout exists, link it and carry only the current decision
and relevant conditions into the handoff; do not paste its route history.

For continuation:

- Checkpoint identifier and base Git revision or ledger event.
- Goal and definition of done; current strongest result.
- Exact missing implication and dependency status.
- Relevant proof/source/computation paths and their checked versions.
- Active review event IDs, outcomes, conditions and report paths.
- Active mechanism, cheapest discriminator and already exhausted alternatives.
- Untried and deferred continuations, their next executable steps and resumption
  conditions; distinguish attempt outcomes from decisions to close a route.
- Route ownership, resolved obligations, and route-only prerequisite context
  without promoting those prerequisites to theorem dependencies.
- Authorized scope, resource bounds, next executable action.
- For external work, execution identifier, last observation and current
  lifecycle state.

For independent validation, omit the author's desired verdict, confidence and
diagnosis. Provide the claim, raw proof and source material. Ask the reviewer to
derive the central implication. Do not call a pass independent if it inherited
the reasoning it was supposed to test. Report source or environment limitations.

If parallel agents are authorized, give each one a bounded mathematical job
with one owner, base checkpoint and explicit write scope. Different agents
should not edit the same live state or journal. Each return identifies its base
and artifact hashes. The coordinator reconciles results and appends state
sequentially after checking actual artifacts; arrival order does not establish
ancestry or supersession. A branch failing does not stop the other routes or the
research program.

SHA-256: 59b3c829230b91644ade151ea69bd27505144be04c32a1c1a51f271d73d2af0a