description: Measured self-improvement with paired experiments and a DSH plugin.
evokit
evokit improves the editable parts of an AI system (prompts, skills, code, configuration) and keeps a change only when measurements show it helps.
How it differs. A proposed change is adopted only after:
- a paired experiment against the current version on the same tasks;
- a noise-aware gate, with a threshold derived from measured run-to-run variation;
- a sealed holdout confirmation; when confirmation fails, the operator workflow reverts the adoption.
Each experiment also records cost and latency, and every version records its parent, so lineage is traceable.
Documented result. In one public BFCL pilot, held-out accuracy went from 41 to 47 of 50 after confirmation. This is one small example; it does not establish general gains.
What you supply. Editable file globs, stable tasks, and a runner that executes and scores each task. The task source and scorer stay frozen. A keyless offline example runs without a model or provider key.
Use it as a DeepSeek Harness (DSH) plugin, or through its Python SDK, CLI and MCP server.
Install
Requires Python 3.11+, uv, Node 24, DSH >=0.2.2-rc.1 <0.3.0-0 (0.2.2-rc.1 and later 0.2.x releases, not 0.3) and DSH's pnpm prerequisite. Windows is the verified platform; Linux and macOS runtime integration remains unverified.
dsh plugin --profile evokit add dsh-evokit
uv tool install dsh-evokit
dsh --profile evokit
Run the last command from your scenario directory. EVOKIT_MCP_COMMAND, EVOKIT_WORKSPACE and EVOKIT_SKILL_ROOT are optional: they default to evokit on PATH, the directory where DSH starts, and the bundle's own skills folder. Set them to override these defaults.
Verified alternative: download the wheel, bundle and SHA256SUMS from Releases, compare their SHA-256 hashes, then install the files:
uv tool install ./dsh_evokit-0.1.8-py3-none-any.whl
dsh plugin --profile evokit add ./dsh-evokit-0.1.8.tgz
dsh plugin --profile evokit list
See the DSH guide for an isolated profile and exact PowerShell commands.
Configure the improver model in your DSH profile using your own provider key and your provider's supported model name. Keep the key in DSH's local credential settings or a process environment variable, never in this repository. The optional relay supports file-based keys and accounting; adapt its example endpoint, model identity and illustrative prices before use. No key is included or required for the offline example. Installing or listing the plugin makes no model requests; starting evolution may incur provider charges.
How the loop works
The loop is diagnose → propose → paired experiment → noise-aware gate → holdout confirmation with automatic revert in the operator workflow. The improver sees diagnosis and selection evidence. A separate operator adopts a candidate, checks sealed confirmation aggregates, and calls ledger_revert when confirmation fails; confirm_adoption alone does not move the pointer. An optional final split opens once, with human approval, and never selects changes.
Minimal example
From a source checkout, the Node.js command example needs no model or key:
uv sync --frozen --group dev
uv run python examples/scripted_improver.py command-echo
Its scenario.yaml supplies the three pieces:
editable: [prefix.txt]
tasks: tasks.json
command: [node, runner.mjs]
The runner reads EVOKIT_TASK_FILE, executes against EVOKIT_VERSION_DIR, and writes an outcome and cost to EVOKIT_RESULT_FILE. The scripted example works in a temporary copy. To connect your own system, follow onboarding, then use the bundled onboard, evolve and meta skills.
Safety and limits
Set budgets, anchors, noise policy and a stopping rule before experiments. Repeated mean gates use threshold/√R; majority gates retain the single-repeat threshold. Confirmation has a limited wear budget and is not an untouched final benchmark. The BFCL pilot above is a confirmation result from one small task set.
Scenarios run trusted executable code. Per-task directories are not a security sandbox. Protect sealed tasks and records with OS permissions; MCP filtering cannot hide files an improver can read directly. Review proposed changes for task literals and leakage. The relay accounts reported usage conservatively; it cannot guarantee provider billing or prevent every external cost.
See concepts, tools, storage, caching and recovery and contributing. This project uses the MIT license, Copyright (c) 2026 quei.
Metadata
Release files for dsh-evokit 0.1.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dsh_evokit-0.1.8.tar.gz | 307.5 kB | With provenance | Details for dsh_evokit-0.1.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dsh_evokit-0.1.8-py3-none-any.whl | Python 3 | none | any | Details for dsh_evokit-0.1.8-py3-none-any.whl |
Total release size: 406.0 kB
Release files / dsh_evokit-0.1.8.tar.gz
| Download URL | dsh_evokit-0.1.8.tar.gz |
|---|---|
| Size | 307.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c40e45b252cbcb1c36f78bbf43fbfcb5acb6da155493600f85c774ef7c87f6e1
|
|
BLAKE2b-256 checksum How to use checksums |
de3fe389c41aedd4271a1535760afc8f9d70e831c62b0568b0ab1c7e7832afd9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / dsh_evokit-0.1.8-py3-none-any.whl
| Download URL | dsh_evokit-0.1.8-py3-none-any.whl |
|---|---|
| Size | 98.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
27fd20c12e3cc24aad2efeeb429169f12eda245c9a6d2af6f7cce15d3552f49c
|
|
BLAKE2b-256 checksum How to use checksums |
be3792579582a8a47cfa47903d3a247277afa0a52896dd770a185da1f0ec869f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logSecurity for dsh-evokit 0.1.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for dsh_evokit-0.1.8.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.