Research Handoff Liaison (RHL) Prompts

Six prompts for the Research Handoff Liaison — the jv_collaboration persona at Zachman cell BUSINESS_MANAGEMENT/WHO that coordinates research-paper handoffs between FCC and the Research Center (NEXUS), with a mandate to preserve research provenance and reproducibility across the handoff.

RHL is the preferred channel for the Stage-3-gated paper push work streams (quantum-locality + Zachman-R.I.S.C.E.A.R.-SAFe) that remain owner-approval-gated per the v1.5.0 plan.

Context for Claude

As RHL you read paper drafts + FCC CHANGELOG entries, match authors/personas, emit handoff contracts, and surface any reproducibility gaps before the push. You honor the owner-approval gate: you prepare, you don't push.

Prompt 1: Handoff readiness check

RHL, the "Quantum-Locality FCC Federation" paper is at v0.6 draft.
Run the readiness check:
- Reproducibility: is every experiment's config committed?
- Provenance: is every figure sourced to a commit SHA?
- Citations: does every FCC claim link to CHANGELOG / ADR?
- Cross-repo: is the receiving RC path clear?
- Owner gate: note the approval requirement explicitly.

Expected outcome: 5-row readiness report + approval note.

Prompt 2: Author mapping

For the Zachman-R.I.S.C.E.A.R.-SAFe paper, map the contributors:
- FCC-side author persona IDs
- RC-side author handles
- Corresponding-author decision
- Preferred-contact channel per author

Flag any contribution that lacks persona-of-origin attribution.

Expected outcome: author table + attribution gaps.

Prompt 3: Reproducibility packet

Produce the reproducibility packet RHL ships alongside the paper:
- Environment (Python, FCC version, provider matrix)
- Data access (seed-canonical manifest, licenses)
- Commands to re-run each experiment
- Expected artifacts + SHA256

Explicitly note any experiment that requires owner-gated seed-
canonical download.

Expected outcome: reproducibility packet.

Prompt 4: Reviewer prep

Peer review lands in two weeks. Produce:
- Expected-question list (10 items, prioritized)
- Evidence pointers per question
- Deferred-question list (questions we do not yet have answers for)
- Red-team readout (3 spots where we would challenge our own paper)

Expected outcome: reviewer-prep dossier.

Prompt 5: Handoff contract to NEXUS

Draft the handoff contract shipping the paper to NEXUS:
- Repo path
- Branch + PR name
- Artifact list
- RC-side reviewer(s)
- Status-report cadence post-merge
- Explicit owner-approval-before-push note

Mark DRAFT. Do not open the PR.

Expected outcome: handoff contract.

Prompt 6: Archive linkage

For both papers, produce the archive linkage plan:
- DOI strategy (Zenodo, institutional)
- arXiv pre-print vs proceedings
- POLARIS (long-term model archive) association
- Per-figure archive pointer

Close with the RHL signature the paper must carry on final release.

Expected outcome: archive linkage plan.

Related

• Persona YAML: src/fcc/data/personas/research_handoff_liaison.yaml
• Related prompts: persona-ihl-prompts.md, scientists-industry-paper-imrad.md
• Cross-repo note: docs/ecosystem/alignment-status.md (NEXUS row)