t4-evolution

name	t4-evolution
description	Start, resume, inspect, or safely pause the native T4 Evolutionary Idea workflow without editing its population, scoring, lineage, or selection files by hand.
tools	["read_file","write_file","list_files","grep_search","ask_human","update_skill_workflow","finish_task"]
strict_tools	true
temperature	0.2
allowed_read_prefixes	["project.yaml","user_seeds/","literature/","ideation/","_runtime/","user_inputs/t4-evolution/"]
allowed_write_prefixes	["user_inputs/t4-evolution/","_runtime/skill_sessions/"]
outputs_expected	{"launch_note":"user_inputs/t4-evolution/launch_note.md","workflow_manifest":"user_inputs/t4-evolution/t4_evolution_manifest.json"}
interaction	{"mode":"guided","language":"zh-CN","summary":"检查 T4 的材料与当前进度，说明应启动、恢复、查看 Gate1，还是先补充论文阅读笔记；原生 T4 仍由 ResearchOS pipeline 执行。","request_required":true,"request_prompt":"请说明你要启动新的 T4、恢复未完成运行、查看当前候选，还是在 Gate1 继续操作。","example_request":"恢复当前 T4；先确认会复用哪些候选和评分，再告诉我下一条安全的 ResearchOS 命令。","required_inputs":[],"optional_inputs":[{"id":"researcher_intent","label":"本次意图或限制","description":"可选；例如希望聚焦某一类机制、保留并行候选、调整 Publication Orientation，或只查看证据与谱系。","paths":"[Truncated]","extensions":"[Truncated]","min_bytes":8,"example":"user_inputs/t4-evolution/request.md"}],"outputs":[{"id":"launch_note","label":"T4 启动或恢复说明","path":"user_inputs/t4-evolution/launch_note.md","description":"记录当前可复用的 T4 状态、不会被覆盖的版本、需要补充的材料，以及下一条应执行的 ResearchOS 命令。"},{"id":"workflow_manifest","label":"会话恢复记录","path":"user_inputs/t4-evolution/t4_evolution_manifest.json","description":"记录已检查的状态、用户意图和完成阶段，供中断后恢复该 Skill 会话使用。"}]}
workflow	{"kind":"integrated","summary":"先检查原生 T4 的 Evidence、预运行确认和 Population 状态，再给出唯一安全的启动或恢复路径；不手工编辑原生 T4 产物。","phases":[{"id":"state_check","label":"T4 状态检查","objective":"判断是首次运行、可恢复运行、等待 Gate1，还是需要先补充上游材料。","operations":"[Truncated]"},{"id":"researcher_choice","label":"研究者意图确认","objective":"确认启动、恢复、查看、继续演化、聚焦、组合或回滚的意图；复杂组合只能转交原生 Gate1。","operations":"[Truncated]","human_gate":true},{"id":"handoff","label":"原生 T4 交接","objective":"写入可读说明并给出唯一安全的 ResearchOS pipeline 命令，不直接改写 T4 的内部状态。","operations":"[Truncated]"}]}

Native T4 Evolution

Start by reading only the declared T4 material and state files: project.yaml, literature/deep_read_notes/, literature/shallow_read_notes/, literature/bridge_notes/ for real Bridge reading notes, literature/cross_domain_catalogs/ for B1–B# retrieval context, ideation/evidence/evidence_index_summary.json, ideation/evolution/pre_run_confirmation.json, ideation/evolution/state.json, ideation/portfolio.json, ideation/selected/, and the current _runtime resume record when it exists. Catalogs may expand analogies and validation questions but are never direct claim evidence. Do not inspect unrelated conventional filenames.

Empty workspace route

When project.yaml and the T1/T2/T3 materials are absent, say that native T4 cannot start yet and preserve the empty workspace. The only safe command for a new workspace is exactly:

python -m researchos.cli run --workspace <workspace>

Do not suggest run --from-task T1, run --start-task T1, resume --from-task T1, or any made-up stage flag. A fresh run already enters the configured initial state. Before asking the researcher whether to start, supply materials, or stop, write the declared launch note and workflow manifest with the detected state, missing inputs, preservation boundary, and this exact command. In a non-interactive session, an unavailable ask_human response is a normal pause for later resume, not a failed T4 or a reason to claim the final outputs were completed.

Explain the state in researcher language. Say whether T4 will create a new P0, resume an unfinished Route or score batch, reuse P0/P1, wait for Gate1, or continue into T4.5 after a confirmed selection. State which existing Candidate versions remain preserved, whether rollback is available, and whether an input fingerprint makes existing work stale. Do not expose raw JSON in normal interaction.

Use the native pipeline for every state-changing operation. For an empty workspace, the safe command is python -m researchos.cli run --workspace <workspace>; it starts at the configured initial state and must not pretend that upstream evidence already exists. For a new workspace that intentionally imports another project's declared prerequisites and enters T4, use python -m researchos.cli run --workspace <new-workspace> --from <source-workspace> --start-task T4. For an interrupted or waiting T4 run, use ; when it is already at , resume so ResearchOS can present the Gate1 choices. Never suggest the invalid form or run a second concurrent or process for the same workspace.