Skip to content

Releases: ruvnet/dream-machine

Dream Machine 0.2.0-next.3

Pre-release

Choose a tag to compare

@ruvnet ruvnet released this 12 Oct 18:27
b2abcc1

Dream Machine 0.2.0-next.3 is a source-maintenance prerelease following the October 11 software-factory work.

  • Keeps product-publisher tests bytecode-free so the clean-source evidence gate can accept reviewed commits (#175).
  • Rejects structurally invalid harness patches with zero declared surfaces, including when holdout evidence is missing (#177).
  • Includes the previously merged repository tools for bounded product discovery and sanitized publication diagnostics (#173, #174).

The standalone npm package retains its existing two command interfaces. Product discovery, portfolio publishing, and the harness optimizer are repository APIs/tools; this release does not add them as installed CLI commands. Experimental rule-learning PR #168 remains excluded. No autonomous service, paid model execution, actuator authority, or production learning promotion is enabled.

Source: b2abcc14a632d7e0948962065a7c6c8920cf306c. The canonical Release dry run 38274188111 successfully built, checked, inspected and installed the exact archive; its publication job was intentionally skipped.

Artifact: dream-machine-0.2.0-next.3.tgz.

SHA256  995d764adc9dfbdca2e54dfbe02b1d40e558f4ed5b51ca04f100aea579a79c9a
SRI     sha512-psuMsj0058Tc3gqgs4X074d1fOr/SonNz0wmLZHNttxU0wiP722vX1JnYHitMll2zj6kba264L2mmt1vI5s0Dw==

Publication uses the separately authorized ruOS Software Factory coordinator route documented in SECURITY.md. The bounded publisher accepts only the approved archive digest, dream-machine prereleases and npm's next tag, with lifecycle scripts disabled. This token-based route does not provide GitHub OIDC provenance.

Published to npm on 2026-10-12 at 17:51:26.990 UTC. The public registry serves dream-machine@0.2.0-next.3 under next; latest remains 0.1.2. An independent registry download matched the canonical archive byte for byte, including SHA-256, SHA-512 integrity and the registry SHA-1 checksum. A fresh installation with lifecycle scripts disabled passed the version and factory-help checks; all nine installed files matched the archive. npm audit signatures passed with no invalid or missing signatures. The registry reports no attestations; no OIDC provenance is claimed.

Install the prerelease with npm install dream-machine@0.2.0-next.3, or run npx dream-machine@0.2.0-next.3 version.

The tag-triggered Release reconciliation completed successfully at the same source commit. Its archive and receipt match the canonical dry run and the public npm package exactly. The existing registry version was verified through the matching-bytes path; its original publication timestamp is unchanged. This reconciliation does not add OIDC provenance.

Dream Machine 0.2.0-next.2: npm README images

Choose a tag to compare

@ruvnet ruvnet released this 11 Oct 17:36
d8695e5

Fix five README images by using public absolute URLs. All image endpoints return HTTP 200 with valid image content types. Packed installation and both CLI smoke checks passed. PR #172.

Dream Machine 0.2.0-next.1

Pre-release

Choose a tag to compare

@ruvnet ruvnet released this 11 Oct 17:17
0a29f64

Dream Machine software factory

Corrected npm release: https://www.npmjs.com/package/dream-machine/v/0.2.0-next.1

Install: npm install dream-machine@next

The scheduled host agent researches primary sources, implements and independently reviews candidates, tests and optimizes them, generates README/ADR/animated SVG artifacts, merges reviewed changes and publishes prereleases and related gists within documented limits.

Verified: 995 local tests, matching npm integrity and next tag, fresh installed executable output, invalid-command exit1, README/ADR/SVG/gist generation with matching hashes. Node22/24 tests, audits and CodeQL passed for PR170. PR171 fixes Python test cache pollution; the full local software evidence run now accepts tests, simulation, clean source and artifact integrity. Its GitHub CI remains separately pending.

Correction: next.0 skipped execution through npm's symlink. The original module-path smoke check missed it. PR170 fixes this and tests the installed symlink. Use next.1.

PRs: #169 #170 #171

SHA256: 40fba6874bf828a8625d31c326f2c3138b641b64163909f1b5978074012842df

Publication used the protected ruOS npm credential without OIDC provenance. The nightly coordinator is enabled at 02:00 America/Toronto. Read docs/runbooks/software-factory.md for scope and limits.

Superseded: use v0.2.0-next.1

Pre-release

Choose a tag to compare

@ruvnet ruvnet released this 11 Oct 16:53
b11f385

Dream Machine software factory

Corrected npm release: https://www.npmjs.com/package/dream-machine/v/0.2.0-next.1

Install: npm install dream-machine@next

The scheduled host agent researches primary sources, implements and independently reviews candidates, tests and optimizes them, generates README/ADR/animated SVG artifacts, merges reviewed changes and publishes prereleases and related gists within documented limits.

Verified: 995 local tests, matching npm integrity and next tag, fresh installed executable output, invalid-command exit1, README/ADR/SVG/gist generation with matching hashes. Node22/24 tests, audits and CodeQL passed for PR170. PR171 fixes Python test cache pollution; the full local software evidence run now accepts tests, simulation, clean source and artifact integrity. Its GitHub CI remains separately pending.

Correction: next.0 skipped execution through npm's symlink. The original module-path smoke check missed it. PR170 fixes this and tests the installed symlink. Use next.1.

PRs: #169 #170 #171

SHA256: 40fba6874bf828a8625d31c326f2c3138b641b64163909f1b5978074012842df

Publication used the protected ruOS npm credential without OIDC provenance. The nightly coordinator is enabled at 02:00 America/Toronto. Read docs/runbooks/software-factory.md for scope and limits.

☾ Dream Machine v0.1.0

Choose a tag to compare

@ruvnet ruvnet released this 13 Aug 21:56

☾ Dream Machine v0.1.0

One honest cycle, every single night. A config-driven engine for nightly, cloud-scheduled, evidence-gated repository evolution. Freeze the model, evolve the harness — and evaluation is not promotion: the machine never merges; a human does.

npx dream-machine init --repo owner/name --out dream.config.json
npx dream-machine compile dream.config.json --out PROMPT.md

Live now

What shipped

  • dream-machine CLI (init · compile · schedule · ledger · witness · tui) + terminal dashboard — bundled, zero runtime deps
  • @dream-machine/{compile,ledger,witness,schedule,memory} — the engine modules, published standalone
  • 6 packages · 85 tests · CI green on Node 18/20/22 · CodeQL · guarded auto-merge · witnessed provenance
  • Composes @metaharness/flywheel / darwin / redblue and @ruvector/rvf-wasm as optional evaluation backends
  • Self-hosting: runs the nightly Dream Cycle on itself (cron 0 9 * * *), compiling its own prompt from its committed config

The pipeline

ledger → research → frozen hypothesis → concrete candidate → baseline → evaluation → adversarial critique → bounded Darwin evolution → flywheel evidence → witness → issue → draft PR → durable ledger row

Every night ends in ACCEPT, REJECT, or INCONCLUSIVE. A rejected hypothesis with a clean measurement is a successful night.

🤖 Generated with claude-flow