chore(fork): Dream Engine fork identity (README + FORK.md); track upstream - #7
Closed
jjohare wants to merge 2 commits into
Closed
chore(fork): Dream Engine fork identity (README + FORK.md); track upstream#7jjohare wants to merge 2 commits into
jjohare wants to merge 2 commits into
Conversation
…tream DreamLab-AI's fork takes this engine in an internal direction (agentbox estate, Loom-driven sovereign mutations, Rust dream-engine path). Rename the displayed product brand and credit rUv's original ruvnet/dream-machine. Scope (branding + inert identifiers only — live dream cycle untouched): - README: new Dream Engine identity, badges/links repointed to DreamLab-AI/dream-engine, explicit "Origin & credit" section + upstream reference (we do not push branches/PRs back to ruv). - SECURITY.md, ADR-0001, ADR INDEX, docs/site/* marketing site: brand prose. - package.json descriptions (all workspaces) + JSDoc header comments. Deliberately NOT renamed (deferred to a validated follow-up): - npm package identifiers (dream-machine, @dream-machine/*), dream.config.json, the evolve/compile CLI surface — the running nightly cycle resolves these. - Compiled-prompt output strings in packages/compile + their golden snapshots, the scheduled routine name, and dream-nightly.mjs OpenRouter attribution — these are asserted by tests and collide with the in-flight compiler-parity branch; renaming needs a snapshot-regeneration run. Original © rUv (MIT) preserved. All 96 tests green. Co-Authored-By: jjohare <github@thedreamlab.uk>
We keep merging ruvnet/dream-machine as rUv develops it, so a broad internal rebrand is counter-productive — every renamed line becomes a merge conflict. Revert the diffuse "Dream Machine → Dream Engine" prose (docs/site, ADRs, SECURITY, package descriptions, source comments) back to upstream text, so the engine, docs, and site stay byte-identical to upstream and merge cleanly. Fork identity is now concentrated where it can't conflict: - README front door: "Dream Engine" + Origin & credit + tracking-fork notice. - New FORK.md: rationale, the upstream sync recipe, and a "how to tell them apart" table. A new file has no upstream counterpart, so it never conflicts. Upstream tracking is wired: `upstream` → ruvnet/dream-machine (push URL disabled so nothing can go back by accident). Sync via `git fetch upstream && git merge upstream/main`. Internal naming (dream-machine, @dream-machine/*, dream.config.json, compiled prompt) intentionally left as rUv ships it. All 96 tests green. Co-Authored-By: jjohare <github@thedreamlab.uk>
jjohare
changed the title
jjohare
pushed a commit
that referenced
this pull request
Aug 16, 2026
…roMergeStreak always-true bug) Nightly Dream Cycle, 2026-08-14. DEEP=developer-experience, SCAN=cli,tui. `dream-machine ledger signals` never passed mergedPrNumbers into learningSignals(), so zeroMergeStreak was a worst-case default (true whenever the window has a real PR) presented as a verified reading. Reproduced first-hand against this repo's real ledger: the CLI reported zeroMergeStreak=true even though PR #7 is confirmed merged via the GitHub API. Adds an optional `--merged "7,12"` flag on `ledger signals` that threads known-merged PR numbers into the library's existing, already-correct learningSignals(rows, { mergedPrNumbers }) option. Full report: docs/dream-cycle/2026-08-14-developer-experience-report.md
jjohare
added a commit
that referenced
this pull request
Aug 16, 2026
Land the concentrated fork marker on main (previously PR #7): README front door reads "Dream Engine", adds an Origin & credit section crediting rUv's original ruvnet/dream-machine, and a tracking-fork notice. New FORK.md documents the rationale, the upstream sync recipe, and a "how to tell them apart" table. Net divergence from upstream stays 2 files — the engine, docs, and site are byte-identical to ruvnet/dream-machine so `git merge upstream/main` stays clean. Co-Authored-By: jjohare <github@thedreamlab.uk>
Contributor
Author
|
Integrated into |
jjohare
pushed a commit
that referenced
this pull request
Aug 16, 2026
The CLI's `ledger signals` command has always called learningSignals(rows) with no mergedPrNumbers option, so zeroMergeStreak was unconditionally true whenever any PR existed in the window, regardless of real merge status — demonstrated live tonight: PR #7 merged three days ago but the signal still reported a zero-merge streak. Prior-night fates already exists to record per-PR MERGED/CLOSED/OPEN/STALE fates from each night's STEP-1 check; wire it in via a small #N:FATE token parser (parsePriorFates), additive to the existing option so nothing regresses when fate data is absent. Dream Cycle 2026-08-16, DEEP=ledger-signals, SCAN=witness,verify.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Marks this repo as DreamLab-AI's tracking fork of
ruvnet/dream-machinewith a concentrated identity, so we can keep merging rUv's development cleanly.Net change: 2 files —
README.md+FORK.md. Everything else (packages, CLI,dream.config.json, compiled prompt, docs, marketing site) is byte-identical to upstream on purpose — a broad rebrand would turn every upstream change into a merge conflict.FORK.mddocuments why the fork exists, the upstream sync recipe (git fetch upstream && git merge upstream/main), and a "how to tell them apart" table.upstreamremote wired to ruvnet/dream-machine (push URL disabled). Internal naming left as rUv ships it.All 96 tests green.
🤖 Generated by Claude Code