v0.8.0-alpha.4 — Fail-Closed Model Cost Admission

v0.8.0-alpha.4 — Fail-Closed Model Cost Admission

E1 infrastructure: READY

Live E1 / DSH re-scan: NOT RUN

Outcome value / multi-client portability: NOT PROVEN

This prerelease makes the user's DeepSeek test-cost rule part of the frozen E1 evidence chain. It performs no DSH installation, live model session or paid API call.

What changed

• The active Goal Governor protocol is frozen as v1.1. v1 was superseded before any live run (0 runs) and remains retrievable by exact alpha.3 tag, commit, blob path, byte length and SHA-256 in the v1 archive record.
• Manifest and run-lock schemas freeze base_url. Remote is exactly provider=deepseek-official, model=deepseek-v4-flash, base_url=https://api.deepseek.com; local also fixes provider=deepseek-official so the DSH DeepSeek-compatible adapter resolves a no-trailing-slash, explicit-port literal loopback base URL. Unknown routes and route/provider/model/base-URL drift fail closed.
• Beijing weekday windows [09:00,12:00) and [14:00,18:00) reject DeepSeek API. Outside those windows and on weekends, remote E1 remains official-Flash-only at the exact official base URL. Weekends waive only the time blackout, not run lock, budget, cost acknowledgement or route constraints.
• Before every child launch, the outer runner creates a frozen settings file with watch=false and injects the locked DEEPSEEK_BASE_URL. The child revalidates the effective URL through DSH's public DeepSeek resolver before create/resume and before and after every model followup. Admission is also recalculated before output, before DSH spawn and in each resumed process; the reserved interval and absolute deadline cap the child runtime.
• Evidence bundles preserve admission receipts—including a pre-spawn denial receipt when launch is refused—and bind process start, end and timeout to the absolute deadline. The offline scorer reconstructs successful-run decisions from frozen policy, route, timestamps and budget rather than trusting an ALLOW label.
• Historical Phase A protocols, locks, bundles and evaluation/runtime/eval-headless.mjs are explicitly audit-only and cannot serve as a new model runner.

Upgrade from alpha.3

npx -y github:TLNing260310/dsh-researcher#v0.8.0-alpha.4 --force

--force replaces the two installed preset directories under DSH_HOME; hand edits inside those directories are not preserved. It does not modify repository-local Project Cognition, approved goals or the verifier registry.

Operational boundary

The policy is mechanically enforced by the official repository E1 runner and checked again by the offline scorer. A loopback base URL proves only the adapter's first hop is local; it does not prove the local service avoids proxying to a remote API. The policy also does not establish host-clock or scheduler integrity, OS-wide egress isolation, provider billing identity, cryptographic human identity, honest bundle production or the absence of out-of-band API calls. A real E1 operator should additionally configure trusted time, a dedicated key, provider-side limits and alerts, and process/host egress controls appropriate to the desired assurance.

Reproduce the offline release gate

npm run check
git rev-parse HEAD
npm run release:artifacts -- --out <empty-directory-outside-repo> --expected-version 0.8.0-alpha.4 --expected-revision <full-git-object-id-from-above> --require-clean

Run the artifact command only after the final commit. The offline checks do not install or start DSH and do not call a model or network API.

Evidence boundary

Repository tests, doctor and E1 preflight establish mechanical behavior only. This release did not run DSH, live E1, a model or an API. The candidate still needs the DSH-dependent Gate 0 checks—including successful rc.7 resolution of the frozen remote and local routes—followed by all live E1 trajectories. In particular, the local route is implemented but not yet demonstrated runnable. Outcome value remains gated on the pilot and E2; a second adapter and model × client attribution remain gated beyond that.