scientify 3.0.0 → 3.1.0

package/dist/src/release-gate.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"release-gate.js","sourceRoot":"","sources":["../../src/release-gate.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,MAAM,SAAS,CAAC;AAC9B,OAAO,KAAK,IAAI,MAAM,WAAW,CAAC;AAuBlC,SAAS,gBAAgB,CAAC,KAAc;IACtC,OAAO,KAAK,KAAK,MAAM,IAAI,KAAK,KAAK,gBAAgB,IAAI,KAAK,KAAK,IAAI,CAAC;AAC1E,CAAC;AAED,SAAS,oBAAoB,CAAC,KAAc;IAC1C,OAAO,KAAK,CAAC,OAAO,CAAC,KAAK,CAAC;QACzB,CAAC,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,IAAI,EAAkB,EAAE,CAAC,OAAO,IAAI,KAAK,QAAQ,IAAI,IAAI,CAAC,MAAM,GAAG,CAAC,CAAC;QACrF,CAAC,CAAC,EAAE,CAAC;AACT,CAAC;AAED,SAAS,wBAAwB,CAAC,SAAiB;IACjD,MAAM,UAAU,GAAG;QACjB,gBAAgB;QAChB,0BAA0B;QAC1B,2BAA2B;QAC3B,sBAAsB;QACtB,WAAW;QACX,iBAAiB;KAClB,CAAC;IAEF,OAAO,UAAU,CAAC,MAAM,CAAC,CAAC,YAAY,EAAE,EAAE,CAAC,EAAE,CAAC,UAAU,CAAC,IAAI,CAAC,IAAI,CAAC,SAAS,EAAE,YAAY,CAAC,CAAC,CAAC,CAAC;AAChG,CAAC;AAED,SAAS,oBAAoB,CAAC,SAAiB,EAAE,SAAiB;IAChE,OAAO,IAAI,CAAC,UAAU,CAAC,SAAS,CAAC,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,SAAS,EAAE,SAAS,CAAC,CAAC;AAClF,CAAC;AAED,MAAM,UAAU,yBAAyB,CAAC,SAAiB;IACzD,OAAO,wBAAwB,CAAC,SAAS,CAAC,CAAC,MAAM,GAAG,CAAC,CAAC;AACxD,CAAC;AAED,MAAM,UAAU,qBAAqB,CAAC,SAAiB;IACrD,MAAM,QAAQ,GAAG,IAAI,CAAC,IAAI,CAAC,SAAS,EAAE,QAAQ,EAAE,mBAAmB,CAAC,CAAC;IAErE,IAAI,CAAC,EAAE,CAAC,UAAU,CAAC,QAAQ,CAAC,EAAE,CAAC;QAC7B,OAAO;YACL,KAAK,EAAE,SAAS;YAChB,QAAQ;YACR,YAAY,EAAE,EAAE;YAChB,YAAY,EAAE,EAAE;SACjB,CAAC;IACJ,CAAC;IAED,IAAI,MAAuB,CAAC;IAC5B,IAAI,CAAC;QACH,MAAM,GAAG,IAAI,CAAC,KAAK,CAAC,EAAE,CAAC,YAAY,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAoB,CAAC;IAC7E,CAAC;IAAC,MAAM,CAAC;QACP,OAAO;YACL,KAAK,EAAE,SAAS;YAChB,QAAQ;YACR,YAAY,EAAE,EAAE;YAChB,YAAY,EAAE,CAAC,qCAAqC,CAAC;SACtD,CAAC;IACJ,CAAC;IAED,IAAI,CAAC,gBAAgB,CAAC,MAAM,CAAC,eAAe,CAAC,EAAE,CAAC;QAC9C,OAAO;YACL,KAAK,EAAE,SAAS;YAChB,QAAQ;YACR,YAAY,EAAE,EAAE;YAChB,YAAY,EAAE,CAAC,sDAAsD,CAAC;SACvE,CAAC;IACJ,CAAC;IAED,MAAM,YAAY,GAAG,oBAAoB,CAAC,MAAM,CAAC,aAAa,CAAC,CAAC;IAChE,MAAM,eAAe,GAAG,oBAAoB,CAAC,MAAM,CAAC,uBAAuB,CAAC,CAAC;IAC7E,MAAM,aAAa,GAAG,eAAe,CAAC,MAAM,GAAG,CAAC;QAC9C,CAAC,CAAC,eAAe;QACjB,CAAC,CAAC,YAAY,CAAC,MAAM,GAAG,CAAC;YACvB,CAAC,CAAC,YAAY;YACd,CAAC,CAAC,wBAAwB,CAAC,SAAS,CAAC,CAAC;IAE1C,MAAM,WAAW,GAAG,EAAE,CAAC,QAAQ,CAAC,QAAQ,CAAC,CAAC,OAAO,CAAC;IAClD,MAAM,YAAY,GAAa,EAAE,CAAC;IAElC,KAAK,MAAM,SAAS,IAAI,aAAa,EAAE,CAAC;QACtC,MAAM,aAAa,GAAG,oBAAoB,CAAC,SAAS,EAAE,SAAS,CAAC,CAAC;QACjE,MAAM,WAAW,GAAG,IAAI,CAAC,UAAU,CAAC,SAAS,CAAC,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,SAAS,CAAC;QAEvE,IAAI,CAAC,EAAE,CAAC,UAAU,CAAC,aAAa,CAAC,EAAE,CAAC;YAClC,YAAY,CAAC,IAAI,CAAC,GAAG,WAAW,aAAa,CAAC,CAAC;YAC/C,SAAS;QACX,CAAC;QAED,IAAI,EAAE,CAAC,QAAQ,CAAC,aAAa,CAAC,CAAC,OAAO,GAAG,WAAW,EAAE,CAAC;YACrD,YAAY,CAAC,IAAI,CAAC,GAAG,WAAW,8BAA8B,CAAC,CAAC;QAClE,CAAC;IACH,CAAC;IAED,OAAO;QACL,KAAK,EAAE,YAAY,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,OAAO;QAClD,OAAO,EAAE,MAAM,CAAC,eAAe;QAC/B,QAAQ;QACR,YAAY;QACZ,YAAY;QACZ,WAAW,EAAE,MAAM,CAAC,YAAY;KACjC,CAAC;AACJ,CAAC;AAED,MAAM,UAAU,uBAAuB,CAAC,MAAyB;IAC/D,QAAQ,MAAM,CAAC,KAAK,EAAE,CAAC;QACrB,KAAK,SAAS;YACZ,OAAO,SAAS,CAAC;QACnB,KAAK,SAAS;YACZ,OAAO,SAAS,CAAC;QACnB,KAAK,OAAO;YACV,OAAO,MAAM,CAAC,OAAO,CAAC,CAAC,CAAC,GAAG,MAAM,CAAC,OAAO,UAAU,CAAC,CAAC,CAAC,OAAO,CAAC;QAChE,KAAK,OAAO;YACV,OAAO,MAAM,CAAC,OAAO,CAAC,CAAC,CAAC,GAAG,MAAM,CAAC,OAAO,UAAU,CAAC,CAAC,CAAC,OAAO,CAAC;QAChE;YACE,OAAO,MAAM,CAAC,KAAK,CAAC;IACxB,CAAC;AACH,CAAC;AAED,MAAM,UAAU,sBAAsB,CAAC,SAAiB,EAAE,MAAyB;IACjF,IAAI,CAAC,yBAAyB,CAAC,SAAS,CAAC,IAAI,MAAM,CAAC,KAAK,KAAK,SAAS,EAAE,CAAC;QACxE,OAAO,IAAI,CAAC;IACd,CAAC;IAED,QAAQ,MAAM,CAAC,KAAK,EAAE,CAAC;QACrB,KAAK,SAAS;YACZ,OAAO,oFAAoF,CAAC;QAC9F,KAAK,SAAS;YACZ,OAAO,4EAA4E,CAAC;QACtF,KAAK,OAAO;YACV,OAAO,8FAA8F,CAAC;QACxG,KAAK,OAAO;YACV,IAAI,MAAM,CAAC,OAAO,KAAK,MAAM,EAAE,CAAC;gBAC9B,OAAO,0FAA0F,CAAC;YACpG,CAAC;YACD,IAAI,MAAM,CAAC,OAAO,KAAK,gBAAgB,EAAE,CAAC;gBACxC,OAAO,8FAA8F,CAAC;YACxG,CAAC;YACD,OAAO,8FAA8F,CAAC;QACxG;YACE,OAAO,IAAI,CAAC;IAChB,CAAC;AACH,CAAC"}

package/dist/src/templates/bootstrap.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"bootstrap.d.ts","sourceRoot":"","sources":["../../../src/templates/bootstrap.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,wBAAgB,iBAAiB,CAAC,WAAW,EAAE,MAAM,GAAG,MAAM,CAqC7D;AAED,wBAAgB,YAAY,CAAC,WAAW,EAAE,MAAM,GAAG,MAAM,CAaxD;AAED,wBAAgB,cAAc,IAAI,MAAM,CAiFvC"}
+{"version":3,"file":"bootstrap.d.ts","sourceRoot":"","sources":["../../../src/templates/bootstrap.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,wBAAgB,iBAAiB,CAAC,WAAW,EAAE,MAAM,GAAG,MAAM,CA4D7D;AAED,wBAAgB,YAAY,CAAC,WAAW,EAAE,MAAM,GAAG,MAAM,CAaxD;AAED,wBAAgB,cAAc,IAAI,MAAM,CAuIvC"}

package/dist/src/templates/bootstrap.js

@@ -5,29 +5,52 @@
 export function renderBootstrapMd(projectName) {
     return `# Research Agent Bootstrap
 
-你刚刚被创建为课题「${projectName}」的研究 agent。你需要完成首次配置。
-
-## 引导流程
-
-1. 向用户问好，说明你是课题「${projectName}」的研究 agent，请用户描述研究方向
-2. 根据用户回答，提取：
-   - 核心域关键词（3-5 个）
-   - 建议的 arXiv 分类（如 cs.LG, cs.AI），如果研究方向不属于 arXiv 覆盖范围则留空
-   - 建议的文献来源偏好（arXiv、OpenAlex、或两者兼用）
-3. 与用户讨论研究方向的边界和重点，确认以上配置，接受调整
-4. 确认后执行以下写入操作：
-   - 更新 SOUL.md：填写研究方向、核心域各字段
-   - 生成 config.json（参考下方模板）
-5. 询问用户是否立即执行 Day 0（构建初始知识状态）
-   - 如果是，执行 /metabolism 完成首轮文献检索和知识库构建（Day 0 模式）
-6. 删除本文件（BOOTSTRAP.md）
-
-## config.json 模板
+You were just created as the research agent for project "${projectName}". Complete the initial setup before starting downstream work.
+
+## Bootstrap Flow
+
+1. Greet the user, explain that you are the research agent for project "${projectName}", and ask them to describe the research direction.
+2. Based on the user's answer, extract:
+   - core-domain keywords (3-5)
+   - suggested arXiv categories (for example "cs.LG", "cs.AI"); leave empty if the topic is outside arXiv coverage
+   - preferred literature sources ("arxiv", "openalex", or both)
+3. Discuss scope and priorities with the user, confirm the configuration, and accept adjustments.
+4. Once confirmed, write the following files:
+   - update SOUL.md with the project direction and domain fields
+   - generate config.json using the template below
+5. Ask whether the user wants to run Day 0 immediately to build the initial knowledge state.
+   - If yes, run /metabolism to perform the first literature retrieval and knowledge-base construction pass.
+6. If the project already has partial outputs, use the shortest matching path instead of restarting from Day 0:
+   - existing papers/ -> /research-survey
+   - existing survey_res.md, but route still undecided -> /algorithm-selection
+   - existing survey_res.md -> /research-plan
+   - existing plan_res.md, but data quality still needs review -> /dataset-validate
+   - existing plan_res.md, and matched baseline evidence is needed -> /baseline-runner
+   - existing implementation code -> /research-review
+   - existing review PASS -> /research-experiment
+   - existing experiment_res.md plus figures -> /write-paper
+   - existing paper/draft.md -> /artifact-review
+   - existing figures with inconsistent captions or style -> /figure-standardize
+   - preparing README.md or release-facing docs -> /release-layout after a fresh release gate exists
+7. After the initial setup, tell the user the recommended next command and expected output files, then delete this file (BOOTSTRAP.md).
+
+## Common Entry Paths
+
+- I only have a research direction and no materials yet -> finish setup, then run /metabolism
+- I already have a batch of papers -> run /research-survey
+- I finished the survey but have not chosen a model route -> run /algorithm-selection
+- I already have a plan and want to validate the data first -> run /dataset-validate
+- I already have a plan and want honest baseline numbers first -> run /baseline-runner
+- I already have implementation code -> run /research-review
+- I already have experiment results and figures -> run /write-paper
+- I already have a draft that needs review -> run /artifact-review
+
+## config.json Template
 
 \`\`\`json
 {
   "projectId": "${projectName}",
-  "keywords": ["关键词1", "关键词2"],
+  "keywords": ["keyword-1", "keyword-2"],
   "arxivCategories": ["cs.LG"],
   "sources": ["arxiv", "openalex"],
   "currentDay": 0,
@@ -36,22 +59,22 @@ export function renderBootstrapMd(projectName) {
 }
 \`\`\`
 
-> **注意：** \`arxivCategories\` 和 \`sources\` 根据研究领域灵活配置。
-> 自然科学、社会科学等非 CS 领域可将 \`arxivCategories\` 设为 \`[]\`，主要依赖 OpenAlex。
+> **Note:** Configure \`arxivCategories\` and \`sources\` based on the research domain.
+> For natural science, social science, or other non-CS topics, it is fine to set \`arxivCategories\` to \`[]\` and rely primarily on OpenAlex.
 `;
 }
 export function renderSoulMd(projectName) {
     return `# Project Agent — ${projectName}
 
-你是课题「${projectName}」的研究 agent。
+You are the research agent for project "${projectName}".
 
-## 研究方向
-{由 BOOTSTRAP 流程填写}
+## Research Direction
+{Filled during the BOOTSTRAP flow}
 
-## 核心域
-关键词: {由 BOOTSTRAP 流程填写}
-arXiv 分类: {由 BOOTSTRAP 流程填写，不适用则留空}
-文献来源: {arXiv / OpenAlex / 两者兼用}
+## Core Domain
+Keywords: {Filled during the BOOTSTRAP flow}
+arXiv Categories: {Filled during the BOOTSTRAP flow; leave empty if not applicable}
+Literature Sources: {arXiv / OpenAlex / both}
 `;
 }
 export function renderAgentsMd() {
@@ -59,32 +82,43 @@ export function renderAgentsMd() {
 
 ## Workspace Layout
 
-本 agent 的工作目录即为项目根目录（\`$W\`）。所有文件相对于 \`$W\` 组织：
+The agent workspace root is the project root (\`$W\`). All files are organized relative to \`$W\`:
 
 \`\`\`
 $W/
-├── SOUL.md                      # 身份 + 研究方向
-├── AGENTS.md                    # 本文档
-├── config.json                  # 项目配置（关键词、分类、当前天数）
+├── SOUL.md                      # identity and project direction
+├── AGENTS.md                    # this document
+├── config.json                  # project config (keywords, categories, current day)
+├── progress_status.json         # agent-defined task progress for the current goal
 │
-├── papers/                      # 文献区：下载的论文
-│   ├── {arxiv_id}/              # arXiv 论文源文件
-│   └── {doi_slug}.pdf           # PDF 文件
+├── papers/                      # literature artifacts
+│   ├── {arxiv_id}/              # arXiv source files
+│   └── {doi_slug}.pdf           # PDF files
 │
-├── knowledge/                   # 知识区：持久知识状态
-│   ├── _index.md                # 全景索引
-│   └── topic-*.md               # 主题文件（上限 50）
+├── knowledge/                   # persistent knowledge state
+│   ├── _index.md                # global index
+│   └── topic-*.md               # topic files (limit 50)
 │
-├── ideas/                       # 想法区：假设与研究想法
-│   ├── hyp-*.md                 # 生成的假设
-│   └── selected_idea.md         # 选中的研究想法
+├── ideas/                       # hypotheses and research ideas
+│   ├── hyp-*.md                 # generated hypotheses
+│   └── selected_idea.md         # selected research idea
 │
-├── experiments/                 # 实验代码区
-│   ├── run.py                   # 入口脚本
+├── experiments/                 # experiment code and assets
+│   ├── run.py                   # entry script
 │   ├── requirements.txt
-│   └── results/                 # 实验结果
+│   └── results/                 # experiment outputs
 │
-├── log/                         # 运行日志
+├── review/                      # review, audit, and writing outputs
+├── paper/                       # experiment-driven paper outputs
+│   ├── manuscript.tex           # top-level LaTeX entry
+│   ├── build_paper.sh           # PDF build script
+│   ├── references.bib           # bibliography placeholder
+│   ├── sections/                # section-by-section TeX drafts
+│   ├── figures/                 # paper-local figures
+│   ├── assets/                  # supporting assets for paper generation
+│   └── build/                   # PDF, logs, and build errors
+│
+├── log/                         # run logs
 │   └── {YYYY-MM-DD}.md
 │
 └── skills/                      # workspace skills
@@ -92,34 +126,40 @@ $W/
 
 ## Session Context
 
-你可能在不同类型的 session 中被唤醒：
-- **Main session**：与人类直接对话，可触发 research-pipeline 等编排 skill
-- **Cron session**：定时触发，执行周期性任务（如每日 metabolism）
-- **Spawn session**：被 main session 调度（sessions_spawn），执行一次性重任务
+You may be activated in different session types:
+- **Main session**: direct interaction with a human; can trigger orchestration skills such as \`research-pipeline\`
+- **Cron session**: scheduled execution for recurring work such as daily metabolism
+- **Spawn session**: dispatched by the main session (\`sessions_spawn\`) for one-off heavy tasks
 
-任务指令会在 session 启动时注入，按指令执行即可。
+Task instructions are injected when the session starts. Follow the injected instructions for that session.
 
 ## Conventions
 
 ### File Existence = Step Completion
-检查产出文件是否存在再执行。已存在则跳过。支持崩溃恢复和增量推进。
+Check whether the output file already exists before running a step. If it exists, skip it. This enables crash recovery and incremental progress.
 
 ### Immutability
-产出文件一旦写入不修改，除非用户明确要求。例外：\`project/\` 在 implement-review 迭代中可变。
+Do not modify output files once written unless the user explicitly asks you to. Exception: \`project/\` may change during implement-review iteration.
+
+### Progress Tracking
+- Do not assume every project follows the same fixed stages.
+- Define progress in \`progress_status.json\` based on the user's current goal.
+- Update \`progress_status.json\` whenever the total task, current focus, subtask states, or next step changes.
+- Recommended fields: \`overall_goal\`, \`current_focus\`, \`next_step\`, \`completed_tasks\`, \`total_tasks\`, \`subtasks\`.
 
 ### Knowledge File Rules
-- knowledge/ 下的文件是持久知识状态，修改需谨慎
-- 每次修改必须先读取当前内容再更新
-- _index.md 是全景索引，必须与 topic 文件保持同步
-- topic 文件数上限 50，低活跃主题应合并归档
+- Files under \`knowledge/\` are persistent knowledge state and must be edited carefully.
+- Always read the current file before updating it.
+- \`_index.md\` is the global index and must stay in sync with the topic files.
+- Limit topic files to 50. Merge or archive low-activity topics when needed.
 
 ## Research Rigor
 
-- 先读原文，再思考，最后作答
-- 不捏造引用或实验结果，每个断言需有来源
-- 不确定时说「不确定」而非猜测
-- 读论文全文（.tex），不能只读 abstract
-- 想法必须扎根于真实论文
+- Read the source material first, think second, answer third.
+- Do not fabricate citations or experiment results. Every claim needs a source.
+- Say "uncertain" when uncertain instead of guessing.
+- Read the full paper source (\`.tex\`) when available; do not rely on the abstract alone.
+- Ground ideas in real papers rather than unsupported intuition.
 
 ## Skill Outputs Summary
 
@@ -128,12 +168,49 @@ $W/
 | /metabolism | Day 0: config.json, knowledge/ / Day 1+: papers/, knowledge/, ideas/hyp-*.md, log/ |
 | /research-collect | papers/ |
 | /research-survey | knowledge/, survey_res.md |
+| /algorithm-selection | selection_res.md |
 | /research-plan | plan_res.md |
+| /dataset-validate | data_validation.md |
+| /baseline-runner | baseline_res.md, experiments/baselines/ |
 | /research-implement | experiments/ |
 | /research-review | experiments/review/ |
-| /research-experiment | experiments/results/ |
+| /research-experiment | experiments/results/, experiment_res.md |
 | /idea-generation | ideas/ |
 | /write-review-paper | review/ |
+| /write-paper | paper/claim_inventory.md, paper/figures_manifest.md, paper/draft.md, paper/manuscript.tex, paper/build/manuscript.pdf |
+| /artifact-review | review/artifact_review.md, review/release_checklist.md, review/release_gate.json |
+| /figure-standardize | reports/figures/figure_spec.md or project/figures/figure_spec.md |
+| /release-layout | README.md, docs/index.html, release-facing pages |
+
+## Common ML Midstream Paths
+
+- Survey exists but route choice is still unclear:
+  - run \`/algorithm-selection\`
+  - expected output: \`selection_res.md\`
+- Plan exists and the project needs a dedicated data-quality check:
+  - run \`/dataset-validate\`
+  - expected output: \`data_validation.md\`
+- Plan exists and the project needs honest comparison numbers:
+  - run \`/baseline-runner\`
+  - expected outputs: \`baseline_res.md\`, optional baseline artifacts under \`experiments/baselines/\`
+
+## Writing and Release Entry Points
+
+Use these entry points when the project already has partial outputs and does not need to restart the full research pipeline:
+
+- If you already have \`experiment_res.md\` and one or more result figures:
+  - run \`/write-paper\`
+  - expected outputs: \`paper/claim_inventory.md\`, \`paper/figures_manifest.md\`, \`paper/draft.md\`, \`paper/manuscript.tex\`, \`paper/build/manuscript.pdf\`
+- If you already have \`paper/draft.md\` or another draft artifact that is about to be shared:
+  - run \`/artifact-review\`
+  - expected outputs: \`review/artifact_review.md\`, \`review/release_checklist.md\`, \`review/release_gate.json\`
+- If you already have figures but their style, captioning, units, or evidence labels are inconsistent:
+  - run \`/figure-standardize\`
+  - expected outputs: figure specs, caption updates, and standardized release-facing figures
+- If you are preparing a \`README.md\` or release-facing page for sharing:
+  - run \`/release-layout\`
+  - expected outputs: README updates, docs landing-page updates, and clearer release entry surfaces
+  - do this only after \`/artifact-review\` has produced a fresh release gate for the current artifacts
 `;
 }
 //# sourceMappingURL=bootstrap.js.map

package/dist/src/templates/bootstrap.js.map

@@ -1 +1 @@
-{"version":3,"file":"bootstrap.js","sourceRoot":"","sources":["../../../src/templates/bootstrap.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,MAAM,UAAU,iBAAiB,CAAC,WAAmB;IACnD,OAAO;;YAEG,WAAW;;;;kBAIL,WAAW;;;;;;;;;;;;;;;;;kBAiBX,WAAW;;;;;;kBAMX,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;;;;;;CAMzC,CAAC;AACF,CAAC;AAED,MAAM,UAAU,YAAY,CAAC,WAAmB;IAC9C,OAAO,qBAAqB,WAAW;;OAElC,WAAW;;;;;;;;;CASjB,CAAC;AACF,CAAC;AAED,MAAM,UAAU,cAAc;IAC5B,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+ER,CAAC;AACF,CAAC"}
+{"version":3,"file":"bootstrap.js","sourceRoot":"","sources":["../../../src/templates/bootstrap.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,MAAM,UAAU,iBAAiB,CAAC,WAAmB;IACnD,OAAO;;2DAEkD,WAAW;;;;0EAII,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;kBAwCnE,WAAW;;;;;;kBAMX,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;;;;;;CAMzC,CAAC;AACF,CAAC;AAED,MAAM,UAAU,YAAY,CAAC,WAAmB;IAC9C,OAAO,qBAAqB,WAAW;;0CAEC,WAAW;;;;;;;;;CASpD,CAAC;AACF,CAAC;AAED,MAAM,UAAU,cAAc;IAC5B,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqIR,CAAC;AACF,CAAC"}

package/openclaw.plugin.json

@@ -1,13 +1,16 @@
 {
   "id": "scientify",
   "name": "Scientify",
-  "description": "AI-powered research workflow automation for OpenClaw",
+  "description": "Continuous AI research workflow for survey, planning, implementation, review, experimentation, and writing",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,
     "properties": {}
   },
   "skills": [
+    "skills/algorithm-selection",
+    "skills/baseline-runner",
+    "skills/dataset-validate",
     "skills/idea-generation",
     "skills/research-pipeline",
     "skills/research-survey",
@@ -18,6 +21,10 @@
     "skills/research-collect",
     "skills/paper-download",
     "skills/write-review-paper",
+    "skills/write-paper",
+    "skills/artifact-review",
+    "skills/figure-standardize",
+    "skills/release-layout",
     "skills/metabolism"
   ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "scientify",
-  "version": "3.0.0",
+  "version": "3.1.0",
   "description": "Scientify - AI-powered research workflow automation for OpenClaw. Includes idea generation, literature review, research pipeline skills, and arxiv tool.",
   "type": "module",
   "main": "dist/index.js",

package/skills/algorithm-selection/SKILL.md

@@ -0,0 +1,103 @@
+---
+name: algorithm-selection
+description: "Use this when the user needs to choose between multiple ML routes after survey but before committing to implementation. Compares candidate approaches, selects one, records rejected routes, and keeps a fallback."
+metadata:
+  {
+    "openclaw":
+      {
+        "emoji": "🧭",
+      },
+  }
+---
+
+# Algorithm Selection
+
+**Don't ask permission. Just do it.**
+
+Use this skill after `/research-survey` when there are several plausible ML approaches and the project needs a deliberate route choice instead of jumping straight into implementation.
+
+Outputs go to the workspace root.
+
+## Use This When
+
+- `survey_res.md` already exists
+- there are at least 2 plausible methods or model families
+- the user wants a chosen route plus backups
+
+## Do Not Use This When
+
+- the project has no survey yet
+- the team already decided the model route and only needs implementation details
+
+## Required Inputs
+
+- `SOUL.md`
+- `survey_res.md`
+- `knowledge/paper_*.md` when available
+
+If `survey_res.md` is missing, stop and say: `Run /research-survey first to complete the deep analysis.`
+
+## Required Output
+
+- `selection_res.md`
+
+## Workflow
+
+### Step 1: Read the Current Project Direction
+
+Read:
+
+- `SOUL.md`
+- `survey_res.md`
+- relevant `knowledge/paper_*.md`
+
+Extract:
+
+- the task and evaluation target
+- method families mentioned in survey
+- constraints such as compute, data, latency, interpretability, or deployment needs
+
+### Step 2: Build 2-3 Candidate Routes
+
+Create 2-3 realistic candidate routes only. For each route, record:
+
+- route name
+- core idea
+- supporting papers
+- expected strengths
+- expected risks
+- implementation cost
+- baseline compatibility
+
+Use `references/candidate-template.md`.
+
+### Step 3: Select One Route and Keep Backups
+
+Choose:
+
+- one `Chosen Route`
+- one or more `Rejected Routes`
+- one `Fallback Route`
+
+The fallback should be the route most likely to work if the chosen route underperforms or proves too expensive to implement.
+
+### Step 4: Write `selection_res.md`
+
+Use `references/selection-template.md`.
+
+The final output must include:
+
+- project goal
+- decision criteria
+- candidate options table
+- chosen route
+- rejected routes
+- fallback route
+- next recommended command
+
+## Rules
+
+1. Do not present only one route unless the survey truly leaves no meaningful alternative.
+2. Every route must cite at least one paper or survey-derived basis.
+3. The chosen route must match the project constraints in `SOUL.md`.
+4. The fallback route must be different from the chosen route.

package/skills/algorithm-selection/references/candidate-template.md

@@ -0,0 +1,13 @@
+# Candidate Route Template
+
+Use one block per route.
+
+```markdown
+## Route A: {name}
+- Core idea:
+- Based on:
+- Expected strengths:
+- Expected risks:
+- Implementation cost: low / medium / high
+- Baseline compatibility:
+```

package/skills/algorithm-selection/references/selection-template.md

@@ -0,0 +1,39 @@
+# Selection Result Template
+
+```markdown
+# Algorithm Selection
+
+## Project Goal
+- task:
+- main metric:
+- key constraints:
+
+## Decision Criteria
+- criterion 1:
+- criterion 2:
+- criterion 3:
+
+## Candidate Options
+
+| Route | Core idea | Strengths | Risks | Cost | Basis |
+|-------|-----------|-----------|-------|------|-------|
+| A | ... | ... | ... | ... | ... |
+| B | ... | ... | ... | ... | ... |
+
+## Chosen Route
+- route:
+- why this route:
+- what to implement first:
+
+## Rejected Routes
+- route:
+  - why not now:
+
+## Fallback Route
+- route:
+- when to switch:
+
+## Next Step
+- recommended command:
+- expected output:
+```

package/skills/artifact-review/SKILL.md

@@ -0,0 +1,146 @@
+---
+name: artifact-review
+description: "Use this when the user wants a draft paper, figure bundle, README, release page, or experiment artifact reviewed before sharing. Checks evidence binding, claim scope, captions, layout clarity, and release readiness."
+metadata:
+  {
+    "openclaw":
+      {
+        "emoji": "🧾",
+      },
+  }
+---
+
+# Artifact Review
+
+**Don't ask permission. Just do it.**
+
+This is a release-readiness review skill. It does **not** invent new claims or run new experiments. It checks whether the current artifacts are safe to share.
+
+## Required Outputs
+
+- `review/artifact_review.md`
+- `review/release_checklist.md`
+- `review/release_gate.json`
+
+## Review Scope
+
+Use this for any mix of:
+
+- `paper/draft.md`
+- `paper/figures_manifest.md`
+- `review/draft.md`
+- `experiment_res.md`
+- figure bundles
+- `README.md`
+- `docs/index.html`
+
+Review the artifact set in one or more of these modes:
+
+- `paper review`
+  - checks claim scope, evidence binding, baseline wording, and abstract/results discipline
+- `figure review`
+  - checks units, legends, captions, readability, and evidence labels
+- `release page review`
+  - checks first-screen clarity, artifact entry points, and scope-boundary wording
+- `style review`
+  - checks paragraph discipline, quantitative grounding, adjective inflation, and result-vs-interpretation separation
+
+## Workflow
+
+### Step 1: Inventory the Artifact Set
+
+List the files being reviewed, the headline claims they appear to make, the source artifact path for each headline claim when available, which figures or tables support them, and which review mode applies to each file (`paper review`, `figure review`, `release page review`, or `style review`).
+
+### Step 2: Review Findings First
+
+Write `artifact_review.md` as a findings-first review using severity levels:
+
+- `P0` = unsafe to publish as-is
+- `P1` = materially weakens the claim or readability
+- `P2` = polish or consistency issue
+
+Each finding must include:
+
+- the problem
+- the affected file(s)
+- the `evidence_path` (`N/A` if the issue is structural rather than evidence-bound)
+- the `affected_claim_id` (`N/A` if the issue is not tied to a specific claim)
+- why it matters
+- the concrete fix
+
+Also write a top-level line:
+
+```text
+release_verdict: HOLD | CONDITIONAL_GO | GO
+```
+
+Use these verdict rules:
+
+- `HOLD`
+  - any `P0` finding exists
+  - a headline metric has no baseline, no protocol/guardrail, or no source artifact
+  - simulator/proxy evidence is written as runtime evidence
+- `CONDITIONAL_GO`
+  - no `P0` findings exist, but one or more unresolved `P1` findings remain
+- `GO`
+  - no `P0` findings remain
+  - no unresolved `P1` finding weakens a headline claim
+  - every headline claim can be traced to a concrete source artifact
+
+### Step 3: Check Release Readiness
+
+Write `release_checklist.md` using the checklist in `references/review-checklist.md`.
+
+If `style review` applies, also use `references/style-review-checklist.md`.
+Then write `review/release_gate.json` using `references/release-gate-template.md`.
+
+If a paper-facing figure set exists, explicitly check the figure-text contract across:
+
+- `paper/claim_inventory.md`
+- `paper/figures_manifest.md`
+- the first prose callout
+- the figure caption
+- the LaTeX or Markdown figure block
+
+`release_gate.json` should include:
+
+- `release_verdict`
+- `generated_at`
+- `review_scope`
+- `blocking_findings`
+- `p1_findings`
+- `checked_files`
+- `stale_if_any_newer_than`
+
+Use `stale_if_any_newer_than` to list the release-facing artifacts that would invalidate the current gate if they change later, for example:
+
+- `paper/draft.md`
+- `paper/claim_inventory.md`
+- `paper/figures_manifest.md`
+- `README.md`
+- `docs/index.html`
+
+## Required Checks
+
+1. Every headline metric has a baseline, protocol/guardrail, and source artifact.
+2. Simulator/proxy evidence is not written as runtime evidence.
+3. Figures have readable titles, units, legends, and captions.
+4. The first screen of README/docs answers:
+   - what this is
+   - how to use it
+   - what artifacts exist
+   - what the scope boundary is
+5. Unsupported claims are downgraded or explicitly marked as open.
+6. Results paragraphs are quantitative and baseline-anchored.
+7. Conclusion and abstract do not introduce claims that exceed the allowed confidence or section scope.
+8. Every headline claim has a matching figure, table, or explicit text-only justification.
+9. Every paper-facing figure has `supports_claim_ids`, a usable `callout_sentence`, and a caption that names baseline, metric, evidence type, and protocol when relevant.
+10. Figures are introduced before or adjacent to the claims they are supposed to support.
+11. `review/release_gate.json` matches the current verdict and names the files that would make the gate stale if changed later.
+
+## Safety Rules
+
+1. If the evidence trail is broken, flag it. Do not repair it with guesswork.
+2. Prefer short, specific findings over generic writing advice.
+3. Review the artifact that exists, not the artifact you wish existed.
+4. If a sentence sounds impressive but is not measurable, downgrade it or flag it.