Skip to content

docs: rewrite hero around general-purpose positioning #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Protocol-zero-0 merged 1 commit into from
May 14, 2026
Merged

docs: rewrite hero around general-purpose positioning #24

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,18 @@
# Evolution Kernel

<p align="center">
<strong>Take a 3 B-active open-weight model. Close most of the SWE-bench gap to GPT-5.5 — overnight, hands-off, fully audited.</strong><br>
<em>No retraining. No fine-tuning. No weight changes. Only the harness around the model evolves.</em>
<strong>A soul plugin for any code.</strong><br>
Drop it into any git repository, give it a measurable goal, and the
codebase begins to perceive its own environment, judge its own
output, and rewrite itself toward the goal — sandboxed, ledgered,
every change a real git commit you can roll back.
</p>

<p align="center">
<em>Code on disk does not evolve. But once a codebase can read its own
outputs, hold a conversation with its own past, and shed failed
experiments without leaving scars — it stops being a body of text and
becomes a process.</em>
</p>

<p align="center">
Expand Down Expand Up @@ -76,7 +86,7 @@ Every attempt is written to a **ledger**: goal, observation, plan, diff, evaluat

---

## Our v1.1 target
## A worked example: SWE-bench Verified (our v1.1 target)

> 📋 **ROADMAP TARGET · NOT A LOGGED RUN.** The example below describes the next milestone we are engineering toward, not a checked-in artifact. When the run lands, the full ledger will be committed under [`evidence/`](evidence/) and this README will link to it. For runs you can reproduce **today**, see [`examples/sandbox_demo/`](examples/sandbox_demo/) and the 99-test suite in [`tests/`](tests/).

Expand Down
14 changes: 11 additions & 3 deletions README.zh.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,16 @@
# Evolution Kernel

<p align="center">
<strong>给一个 3 B-active 的开源小模型，用一晚上无人值守，把它在 SWE-bench Verified 上推到接近 GPT-5.5 的水平。</strong><br>
<em>不重训，不微调，不动一个权重——只进化模型背后的 solver harness。</em>
<strong>任意代码的灵魂插件。</strong><br>
把它放进任意 git 仓库，给它一个可衡量的目标，这份代码便开始感知自己的
环境、评判自己的产出、朝着目标重写自己——沙箱里隔离、ledger 留档、
每次接受的变更都是一条可回滚的 git commit。
</p>

<p align="center">
<em>静止的代码本不会进化。但当一段代码能读取自己的产出、能与自己
的过去对话、能丢掉失败的实验而不留疤——它便不再是被写下的文本，
而成为一个正在发生的过程。</em>
</p>

<p align="center">
Expand Down Expand Up @@ -76,7 +84,7 @@ Evolution Kernel 把 harness 调优变成一个可复现的 runtime。把它指

---

## v1.1 路线图目标
## 一个具体示范：SWE-bench Verified（也是我们的 v1.1 目标）

> 📋 **路线图目标 · 不是已落盘的运行。** 下面这个例子描述的是我们下一步要工程化达到的里程碑，不是已经 checked-in 的 artifact。当这个 run 落地后，完整 ledger 会提交到 [`evidence/`](evidence/) 目录，本 README 会链接过去。**今天就能复现**的真实运行，请参考 [`examples/sandbox_demo/`](examples/sandbox_demo/) 和 [`tests/`](tests/) 下的 99 个测试。

Expand Down
Loading