timwhitez/dsh-self-evolving#packages/dsh-self-evolving
Evidence-first self-evolution controller: bounded Cordis candidate generation, one-shot real-Loader admission, Harbor evaluation, and a crash-resumable journaled lineage.
An evidence-first self-evolution controller for DSH: it treats every candidate change as something to be proven rather than assumed. Bounded Cordis candidate generation is written to a content-addressed object store so each candidate has a verifiable identity, and the project verifies itself with the real Cordis Loader rather than a stand-in. Pinning is explicit: DSH, Harbor and Terminal-Bench checkouts are read-only upstreams, pnpm setup:source installs the accepted DSH pin, and a separate scheduled workflow tests against current DSH.
Install
dsh plugin --profile headless add @dsh-self-evolving/core@0.2.3README install path for the controller: into a headless profile, with an explicit state root and run id, because omission fails Config validation by design — export DSH_SELF_EVOLVING_STATE_DIR="${XDG_STATE_HOME:-$HOME/.local/state}/dsh-self-evolving/demo-1" and export DSH_SELF_EVOLVING_RUN_ID=demo-1 before the plugin add line above. A source checkout (pnpm setup:source) is the documented route for development, self-hosting or reproducing release artifacts.
Compatibility
Node >= 22.19, pnpm 11.7, Apache-2.0. A standard DSH Cordis plugin/service — not a fork of DSH and not a second controller wrapped around it. The headless-profile install needs DSH_SELF_EVOLVING_STATE_DIR and DSH_SELF_EVOLVING_RUN_ID set explicitly; missing either fails config validation on purpose. Test suite reported as 291 unit + 36 E2E tests.
Details
- Repo: timwhitez/dsh-self-evolving#packages/dsh-self-evolving
- Category: Workflow & Automation
- Stars: 0
- Version: 0.2.3 (npm @dsh-self-evolving/core; registry repository field → github.com/timwhitez/dsh-self-evolving, verified 2026-09-11). GitHub release tag dsh-self-evolving-v0.2.0
- Last push: 2026-08-29
- First seen: 2026-08-15
Recent updates
README documents the trust stance: self-modifying agent systems are easy to demo and hard to trust, so every candidate is bounded, content-addressed and verified against the real Cordis Loader; upstream policy and the reproducible pinning channel live in docs/upstream-policy.md.
FAQ
- How do I install dsh-self-evolving?
- Export DSH_SELF_EVOLVING_STATE_DIR and DSH_SELF_EVOLVING_RUN_ID, then run: dsh plugin --profile headless add @dsh-self-evolving/core@0.2.3 — the explicit state root and run id are required by config validation.
- Is dsh-self-evolving a DSH fork?
- No — it is a standard DSH Cordis plugin/service, not a fork of DSH and not a second controller wrapped around it.
- How do I reproduce a release or develop against it?
- Use a source checkout: git clone the repo, run corepack enable then pnpm setup:source, which installs the workspace and materializes the upstream repositories at the exact commits in provenance.lock.json.