Skip to content

dream(ledger-signals): s for 2026-09-01..2026-09-05 as quoted in tonight's evidence - #10

Merged
jjohare merged 2 commits into
mainfrom
dream/ledger-signals-2026-09-06
Sep 6, 2026
Merged

dream(ledger-signals): s for 2026-09-01..2026-09-05 as quoted in tonight's evidence#10
jjohare merged 2 commits into
mainfrom
dream/ledger-signals-2026-09-06

Conversation

@jjohare

@jjohare jjohare commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Draft PR opened by the dream engine on a GATED ACCEPT night (2026-09-06-dream-machine, run d8ca5630048cb58a).

Candidate tree 4cadb33e3f23d056727edf323a871ab613ab9823 was applied in isolation and the required evaluators re-run against it: bench=PASSED, darwin=PASSED. Witness d288b79b6292.

A human decides the merge — evaluation is not promotion.

Finding: Given the ledger rows for 2026-09-01..2026-09-05 as quoted in tonight's evidence pack, when those rows are validated by a row-contract validator requiring (a) finding non-empty, ≤80 chars, not pointer-only, not frozen-hypothesis text; (b) prior-night fates either empty or space-separated #N:FATE tokens; (c) ACCEPT rows carrying a non-NONE PR entry and a non-empty witness; with enforcement cutoff 2026-09-06, then all five rows are flagged (09-01 by pointer rule; 09-02..05 by hypothesis-leak rule), and a compliant row plus the live ledger from the cutoff produce zero violations.

Gate: ACCEPT upheld: 2 required evaluator(s) passed on candidate tree 4cadb33e3f23

Dream Machine and others added 2 commits September 1, 2026 09:55
@jjohare
jjohare marked this pull request as ready for review September 6, 2026 16:10
@jjohare
jjohare merged commit 02e78b0 into main Sep 6, 2026
7 checks passed
jjohare added a commit that referenced this pull request Sep 7, 2026
…ract

The engine writes the ledger finding by truncating the frozen hypothesis at
80 chars, discarding the compliant row each report authors at its own Step 19.
The 09-06 and 09-07 rows therefore landed with `Given …` text, tripping the
`finding-hypothesis-leak` rule that PR #10 introduced the night before —
the validator failing on rows the engine wrote after it merged.

Both replacements are lifted verbatim from the nights' own Step 19 blocks
(79 and 74 chars), and touch no other cell. Rows 09-02..09-05 stay
grandfathered by ENFORCE_FROM = 2026-09-06.

npm test: 135/135 (was 134/135, exit 1).

Co-Authored-By: jjohare <github@thedreamlab.uk>
Claude-Session: https://claude.ai/code/session_01EzN6LxAjkxypXeZ3fTQhz8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant