Skip to content

Conductor 0.3.0 — strict attended Stage 2 contracts

Latest

Choose a tag to compare

@Steel-tech Steel-tech released this 31 Jul 00:43
· 8 commits to main since this release

Conductor 0.3.0 adds the reviewed Stage 2 strict task/report data plane while preserving the Stage 1 attended lifecycle and retention model.

Highlights:

  • closed, duplicate-key-rejecting, bounded task and report contracts bound to repository, workspace, run, generation, role, source, and immutable Git identity
  • private identity-bound report outboxes with reviewer and validator source held read-only
  • atomic no-follow publication, journal-authoritative harvest/rejection, deterministic one-CAS integration, and exact-SHA reviewer/validator gates
  • fail-closed replay, ambiguity, archive, source-drift, and forbidden-effect handling
  • retained resources and archive authority across stand-down and crash boundaries
  • 513-test current/Node 20 suites plus explicit concurrency and SIGKILL matrices

Release provenance:

  • runtime candidate Commit A: 0ed952992ef1559808da4d25a2e7166d075b1ce9
  • evidence-only Commit B and tag target: 712863c34d6126c9d95fa3b9bd6caf5220cbfc43
  • installed Herdr 0.7.5 evidence digest: 8547d5cd3215bf79cdb973437de867e803baba1a86d80916eb0ca8b5f2d8bcfd
  • hosted CI: Linux Node 20/current, macOS system Bash 3.2, ShellCheck, Actionlint, docs, manifest, retained evidence, Stage 2 concurrency, and crash matrices

Compatibility: exactly Herdr 0.7.5 (protocol 17, schema 1), Node 20 or newer.

Boundaries: attended operation only. This release does not provide Stage 3 approval/apply/recovery, suite adapters, unattended orchestration, automatic cleanup/prune, Browser promotion, or protection against malicious same-UID processes. Human selection still governs suite workflow composition.