Skip to main content

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.7-py3-none-any.whl
dsh plugin --profile evokit add ./dsh-evokit-0.1.7.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.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dsh-evokit 0.1.7
File Size Uploaded Provenance Actions
dsh_evokit-0.1.7.tar.gz 293.5 kB Without provenance Details for dsh_evokit-0.1.7.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for dsh-evokit 0.1.7
File Interpreter ABI Platform Actions
dsh_evokit-0.1.7-py3-none-any.whl Python 3 none any Details for dsh_evokit-0.1.7-py3-none-any.whl

Total release size: 385.1 kB

Release files / dsh_evokit-0.1.7.tar.gz

Download URL dsh_evokit-0.1.7.tar.gz
Size 293.5 kB
Tags Source
SHA-256 checksum
How to use checksums
9202297f0157141e5c3dfc718ec03ac148eb33aec606e676f2b01f98cf7bd6cc
BLAKE2b-256 checksum
How to use checksums
b613bb48dfa6951dcc3d0ad92697816b2d9a18872ace56940eb14aef63963c30
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / dsh_evokit-0.1.7-py3-none-any.whl

Download URL dsh_evokit-0.1.7-py3-none-any.whl
Size 91.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9fc0a504447957e7289a12f0d78bc4d8d87b94e56b69a6b0c3ab6468ceb592ec
BLAKE2b-256 checksum
How to use checksums
bfbf89d5c5c3c4b4df5897764e8c9e78402099dc9d36fb0808c614790efa48f4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for dsh-evokit 0.1.7

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Release history Release notifications | RSS feed

This release

0.1.7 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page