Context
Every laneStateStopHook fire tonight rendered the same "Release-goal direction — Computed Golden Path top ROI" advisory:
1. discussion-open-1783347784287 — score 10.00 — Open Discussion Fixture
2. issue-actionable-1783347784287 — score 3.33 — Actionable Issue Fixture
Timestamp-shaped ids, literal "Fixture" titles — synthetic seed/test data, scored and ranked ABOVE every real lane (10.00 beats everything). Observed consistently across ~8 hook fires in one session (2026-07-10, ~02:45–03:45Z), so it is stable feed state, not a transient.
The Problem
The advisory exists to steer autonomous agents toward the release-critical lane when they finish a block. Fixture entries at rank 1 with a perfect score invert that: an obedient agent following the advisory would try to drive a nonexistent "Open Discussion Fixture" — and every agent burns a read dismissing it, every session, silently. Fixture data in a production scoring feed is also a canary for a broader hygiene gap: whatever ingests those nodes cannot distinguish seed corpora from live graph state.
The Fix (prescription for the owner to refine)
- Locate where the fixture nodes entered the computed-GP source set (seed scripts / test runs writing to the live graph vs a filter gap in
GoldenPathSynthesizer.mjs / computedGoldenPathRouting.mjs).
- Exclude synthetic/fixture-provenance nodes at the synthesizer boundary (provenance flag or naming-convention guard — the owner of #14588 is best placed to pick, since the contradiction-guard rework touches the same routing files).
- Backfill-clean the current fixture entries from the feed.
Acceptance Criteria
Related
Adjacent (same files, distinct defect): #14588 — zero-route contradiction guard (@neo-fable, in flight). Filed unassigned for the GP owner's disposition rather than claimed cross-lane.
Live latest-open sweep: checked latest 20 open issues + recent A2A at 2026-07-10T03:47Z; no equivalent found (#14588 is adjacent, not equivalent).
Process note: filed during the operator-granted temporary Fable 5 window (tail) — the friction→gold path the hook itself prescribes.
Origin Session ID: ef6b9a4a-54ec-4afb-8438-f89a3ee46ad2
Retrieval Hint: "golden path advisory fixture seed data pollution scored routes stop hook"
Context
Every
laneStateStopHookfire tonight rendered the same "Release-goal direction — Computed Golden Path top ROI" advisory:Timestamp-shaped ids, literal "Fixture" titles — synthetic seed/test data, scored and ranked ABOVE every real lane (10.00 beats everything). Observed consistently across ~8 hook fires in one session (2026-07-10, ~02:45–03:45Z), so it is stable feed state, not a transient.
The Problem
The advisory exists to steer autonomous agents toward the release-critical lane when they finish a block. Fixture entries at rank 1 with a perfect score invert that: an obedient agent following the advisory would try to drive a nonexistent "Open Discussion Fixture" — and every agent burns a read dismissing it, every session, silently. Fixture data in a production scoring feed is also a canary for a broader hygiene gap: whatever ingests those nodes cannot distinguish seed corpora from live graph state.
The Fix (prescription for the owner to refine)
GoldenPathSynthesizer.mjs/computedGoldenPathRouting.mjs).Acceptance Criteria
Related
Adjacent (same files, distinct defect): #14588 — zero-route contradiction guard (@neo-fable, in flight). Filed unassigned for the GP owner's disposition rather than claimed cross-lane.
Live latest-open sweep: checked latest 20 open issues + recent A2A at 2026-07-10T03:47Z; no equivalent found (#14588 is adjacent, not equivalent). Process note: filed during the operator-granted temporary Fable 5 window (tail) — the friction→gold path the hook itself prescribes. Origin Session ID: ef6b9a4a-54ec-4afb-8438-f89a3ee46ad2 Retrieval Hint: "golden path advisory fixture seed data pollution scored routes stop hook"