| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
feat(plan): guide and observe progress updates | 19 天前 | |
docs(evolve): name the single entry /evolve-design everywhere The composer already has one entry: the algorithm picker opens only for /evolve-design and no /evolve command is handled. The docs and code comments still described the feature as /evolve, which reads as a second entry. Rename those mentions to /evolve-design in the explanation, how-to, README and REST reference pages (en and zh) and in comments. Comments and prose only; the /api/evolve/... routes are untouched. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> | 8 天前 | |
docs: document /evolve — explanation, how-to and tutorial in both languages /evolve ships a 23-module Python sidecar, two search engines, four scoring modes, two agent tools, a design skill, 13 web components, 188 evolve.* message keys and four HTTP endpoints. Its documentation was one Chinese file, explanation/evolve-standalone.md, which no index linked and which answers a maintainer's question — how the two engines differ, and what it would take to run the sidecar as a standalone backend. In English the word "evolve" appeared in exactly one file, in passing. A researcher had no way to learn what a search is for, when scoring will actually discriminate, or how to start one. Add, in English and Chinese: - explanation/evolve.md — what a search is and the one property everything rests on, the four scoring modes with the case each suits, the two engines, the rollout/gate/test split, the discrimination probe, the frozen scorer, where candidates execute, and when not to run a search at all. - how-to/run-an-evolution-search.md — proposing a search, the four design checkpoints, shard sizing with the numbers that matter, choosing a seed, reading the panel, and a table of what to do when a run goes wrong. - tutorial/02-evolve-a-solution.md — one compression search a reader can complete, with what to look at at each checkpoint and how to tell a real improvement from a fitted one. The guidance is drawn from what the code and the skill already state rather than invented: the seed measurements (a cache task seeded with a working LRU climbing 0.2218 → 0.9396 against a compression task seeded with identity encoding finishing at 0.226), the gate/rollout/test sizing bands, and the upstream note on why the scorer is frozen. The seed guidance is framed around what the measurements actually show: the seed has to contain the mechanism the search will improve, in working form, because candidates edit what is in front of them and a from-scratch implementation fails far more often than an edit does. Headroom is a separate requirement — a starting point around 0.3–0.7 — rather than a reason to hand the search something deliberately poor. Screenshots come from the two merge requests that built the feature — !55 (PUCT) and !79 (OpenEvolve) — and are committed under docs/images/evolve/ rather than hot-linked. Also: link evolve-standalone.md from the Chinese explanation index, which takes the repository's orphan pages from three to two, and add a pointer at its top routing readers to the new user-facing pages; add the four evolve endpoints to both REST API references and the two agent tools to both built-in tool references. Refs openJiuwen-ai/sciencediscovery#55 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> | 11 天前 | |
docs(evolve): name the single entry /evolve-design everywhere The composer already has one entry: the algorithm picker opens only for /evolve-design and no /evolve command is handled. The docs and code comments still described the feature as /evolve, which reads as a second entry. Rename those mentions to /evolve-design in the explanation, how-to, README and REST reference pages (en and zh) and in comments. Comments and prose only; the /api/evolve/... routes are untouched. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> | 8 天前 | |
first commit | 1 个月前 |
ScienceDiscovery Documentation
ScienceDiscovery maintains complete documentation in both Chinese and English. Each language tree can be browsed independently and uses the same tutorial, how-to, reference, and explanation structure.
For the shortest path to a working installation, start with the quick start in your preferred language: