Other

/research-lifecycle

Research corpus: stale context, R-number, research docs link (Google Docs/Deep Research report URL). NOT drive-filing.

$ golems-cli skills install research-lifecycle
11 evals
fixtures

Updated 1 week ago

Anti-pattern: R75 says "FTS5 is 96.9% desynced" — but it's been fixed for days. Without lifecycle management, R76 starts from wrong assumptions.

Research context files live at docs.local/claude-web/projects/<project>/. After a sprint implements research findings, these files go STALE. The local corpus is the source; Google Drive keeps the grounding provenance corpus; Deep Research receives prepared files directly by default, with Drive source off. This skill refreshes both so the next research round starts from truth, not assumptions.


HARVEST GATE — research without a harvest path is PARKED, not done

Every research dispatch — fleet-fired OR Etan-fired in his own Gemini/NotebookLM UI (standing fire=Etan rule) — MUST carry these fields at dispatch time:

FieldRequired content
harvest_ownerNamed agent/LEAD who owns pulling results back into the fleet
harvest_triggerWhat event starts harvest (report complete, Drive export lands, cron poll, Etan says "it's done", etc.)
export_routeWhere results land for the fleet: Drive path, docs.local/research/, collab ack, brain_store digest — adapters must name this explicitly

Research without all three = PARKED. Do not mark done, do not brain_store conclusions, do not close the collab row until harvest completes and VERIFY BEFORE STORE passes for those conclusions, or Etan explicitly parks it.

Applies to /gemini-research, /claude-desktop-research, and orc W5 research dispatches. The E07 integrity gate catches bad claims; this gate catches throughput — results sitting unharvested since morning.


When research links arrive, the receiver's FIRST dispatch is ONE coordinator child for the whole batch, including already-filed reports. Use delegate_task with role: "research", target.providerInstanceId: "codex-worker", high effort/default tier, and label its brief codex.research.coordinator. Pass the workflow, all links and the verifier parameter. Omit isolation (shared checkout). Then end the turn. The receiver does no harvesting, splitting, verifying or filing. A non-research link does not take this route. Children briefed by a coordinator (the coordinator itself and its Drive harvest child) skip this route.

The coordinator skips intake dispatch. Per /agent-routing § Execution capability, delegate harvest/readback/filing/NotebookLM to a Drive-write-capable child; wait for its receipt while orchestrating verification. The workflow preserves R{NN}-<slug>-result, readback/export_route and PARKED-not-guessed associations.

ADMISSION BEFORE REPORT — author-held key

For project-grounded /gemini-research, the author records every admission question's exact source answer and real first heading/line in the private admission-key JSON under the prompt record's # Pre-fire checks. Never send the key to the researcher. Preflight --emit refuses incomplete keys or verbatim answer leaks. Before reading the report, extract only its admission table and run:

node skills/golem-powers/gemini-research/scripts/prompt-preflight.mjs --harvest-check admission.md R{NN}-prompt.md

Every answer AND first-line string must match the author key. Any mismatch or missing/extra/duplicate/non-yes row: retain the failure receipt as a fabricated read, discard the whole result; no report reading, verification, filing or conclusion storage. Agreement permits report verification, not acceptance of its claims. Web-only research has no admission table/key. Evidence: NarrationLayer R02 on 2026-11-13, six attached grounding files, six readable: yes rows with invented answers (1.05 vs source 1.5; 0.179 vs 0.484); the author-held key caught the fabricated reads. Earlier Drive-grounded runs stopped with honest readable: no rows. This rule is scoped to these two research skills.