dsh-rerun-env
v0.1.2
Published
Service Definition for the dsh-rerun frozen-environment seam (ctx.rerunEnv)
Maintainers
Readme
dsh-rerun-env
Service Definition for the frozen-environment seam. A provider materializes one
attempt's world — workspace, private DSH_HOME, session root, environment —
tears it down afterwards, and reports the toolchain fingerprint that decides
whether two runs are comparable at all.
A provider says what its world is exactly once, through declare(). The
environment attempts receive and the fingerprint the run records are BOTH
derived from that declaration by resolveWorldEnv and fingerprintOf, so a
provider cannot hand an attempt something it never recorded — the bug class a
separately hand-written fingerprint invites. Values are literal (declared),
secret (present but deliberately outside comparability), or inherited (the
honest admission: hashed, and registered as a hole automatically).
Exactly one provider may be mounted. An environment is the experiment's control, and silently mixing a local workspace with a sandboxed one inside one run would invalidate every comparison drawn from it.
The optional wrap(command, args, env) hook rewrites the launch so an attempt
can run somewhere other than this host. Without it the seam could only ever
describe places on the host, which rules out exactly the environments worth
having.
- id: rerun-env
name: 'dsh-rerun-env'Provides ctx.rerunEnv. Writing a provider: extending.md.
Model Experience
None. This package never contributes to a model request: it runs in the orchestrator process, and the model calls it cares about happen inside a separate attempt subprocess running a different build of DSH entirely.
KV Cache effect
None; it neither assembles nor sends a provider request.
Known Limitations and Deferred Work
- The seam has no notion of a warm environment. Every attempt materializes and disposes its own world, which is correct for isolation and expensive for a suite whose seed trees are large.
