LearnNewsExamplesServices
Frontmatter
id10275
titleGolden Path silent-thread visibility section for atrophying open issues
stateClosed
labels
enhancementaiarchitecture
assigneesneo-gpt
createdAtApr 24, 2026, 2:46 AM
updatedAtJun 6, 2026, 1:50 AM
githubUrlhttps://github.com/neomjs/neo/issues/10275
authorneo-opus-ada
commentsCount1
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[]
closedAtJun 6, 2026, 1:50 AM

Golden Path silent-thread visibility section for atrophying open issues

Closed Backlog/active-chunk-7 enhancementaiarchitecture
neo-opus-ada
neo-opus-ada commented on Apr 24, 2026, 2:46 AM

Golden Path silent-thread visibility section for atrophying open issues

Current Verified State (2026-06-03)

Live V-B-A refreshed #10275 against current source and issue state:

  • The original concern remains valid: active work can go silent without becoming mathematically hot enough to re-enter the Computed Golden Path.
  • The original implementation surface is stale. sandman_handoff.md is now centrally rendered by ai/services/graph/GoldenPathSynthesizer.mjs, while DreamService.executeRemCycle() delegates Golden Path rendering to that service.
  • AgentOrchestrator.parseGoldenPath() only parses ## Computed Golden Path; additional handoff sections are visibility-only unless the parser is explicitly changed.
  • GoldenPathSynthesizer already has a visibility-only section precedent: Brain-Pillar Consumer-Friction is rendered for human/swarm reading and intentionally does not change orchestrator routing.
  • GoldenPathSynthesizer already renders ## Stale Assignment Candidates, but that covers assigned tickets with stale assignee/progress activity. It does not cover unassigned or quietly atrophying open issues.
  • IssueIngestor already projects issue nodes with state, labels, and updatedAt; Golden Path scoring already penalizes needs-re-triage; Latest Priority Backlog already excludes needs-re-triage.
  • The old #10030 concept-level extension dependency is no longer a blocker for this issue-level V1. Concept-level silence remains out of scope until a separate, current contract exists.

Problem

The Golden Path answers "what is mathematically hot now?" and Stale Assignment Candidates answer "which assigned tickets have gone quiet?" There is still no durable handoff section for "which open, structurally significant, non-rejected tickets are quietly atrophying outside the current frontier?"

Without that visibility, agents can keep rediscovering stale work only when a human or peer remembers it. With too much automation, the handoff would become noisy or silently start routing work that was meant only as an attention signal. V1 must therefore be visibility-only.

Accepted Scope

Implement a visibility-only Silent Threads section in the Sandman handoff renderer.

This ticket does not add a new daemon, does not insert a DreamService Phase 4.5, and does not change AgentOrchestrator routing.

Contract Ledger

Surface Contract
Owner GoldenPathSynthesizer.synthesizeGoldenPath() owns the render pass because it already centralizes sandman_handoff.md generation. Helper methods may be added on GoldenPathSynthesizer or a narrow helper module if tests justify it.
Section name Render ## Silent Threads in sandman_handoff.md. Ordering: after ## Stale Assignment Candidates and before ## 📋 Latest Priority Backlog / ## Computed Golden Path.
Routing Visibility-only V1. AgentOrchestrator.parseGoldenPath() must continue to consume only ## Computed Golden Path. Tests must prove ## Silent Threads does not produce directives.
Candidate source Use current synced issue markdown / graph issue-node state. Candidate issues must be OPEN, not assigned, not already in Computed Golden Path, and not labeled needs-re-triage, no-auto-close, duplicate, invalid, or wontfix. Issues with open blockers must be excluded.
Last activity Use the latest reliable issue activity from synced issue metadata/timeline: updatedAt when present, otherwise newest parsed comment/event timestamp, otherwise createdAt. Do not require LLM or semantic summarization.
Structural score Prefer the same SQLite incident-edge weight shape used by Golden Path scoring. If unavailable, fall back to deterministic zero/low score and keep the candidate out unless the issue is old enough and explicitly above the configured threshold.
Score / sort Compute silenceScore = daysIdle * max(structuralWeight, 1). Sort descending by silenceScore, then by daysIdle. Render a capped list with issue number, title, days idle, last activity timestamp, structural weight, and reason.
Config Add Memory Core config leaves beside existing Golden Path render config: goldenPathSilentThreadThresholdMs (NEO_GOLDEN_PATH_SILENT_THREAD_THRESHOLD_MS, default 14 days), goldenPathSilentThreadMinScore (NEO_GOLDEN_PATH_SILENT_THREAD_MIN_SCORE, default implementation-chosen but documented), and goldenPathSilentThreadRenderLimit (NEO_GOLDEN_PATH_SILENT_THREAD_RENDER_LIMIT, default 10).
Empty state Render No silent thread candidates detected. so operators can distinguish "section disabled/broken" from "no candidates".
Docs Update learn/agentos/sandman-handoff-format.md and learn/agentos/DreamPipeline.md to document visibility-only semantics and the no-routing boundary.
Evidence Add focused tests for candidate filtering, score sorting, empty-state rendering, config threshold behavior, and the AgentOrchestrator no-route boundary.

Acceptance Criteria

  • GoldenPathSynthesizer renders ## Silent Threads with the contract above.
  • The section is visibility-only; AgentOrchestrator.parseGoldenPath() ignores it.
  • Candidate filtering excludes closed, assigned, blocked, Golden Path, needs-re-triage, no-auto-close, duplicate, invalid, and wontfix issues.
  • Config leaves and environment variable names are added and documented.
  • learn/agentos/sandman-handoff-format.md and learn/agentos/DreamPipeline.md describe the section and its no-routing boundary.
  • Tests cover candidate generation, rendering, empty state, config thresholds, and parser non-consumption.

Out of Scope

  • New daemon or scheduler task.
  • DreamService Phase 4.5 insertion.
  • AgentOrchestrator routing or auto-assignment.
  • Cross-harness notifications.
  • Concept-level silence detection.
  • Friction-suppression aggregate metrics.
  • LLM triage of silent candidates.

Related

Origin Session ID: b02bd06c-a2cb-4aff-8af1-c4f2643c91be

Retrieval Hint: "GoldenPathSynthesizer Silent Threads visibility-only stale open issues no AgentOrchestrator routing"

tobiu referenced in commit f17fc99 - "feat(agentos): surface Golden Path silent threads (#10275) (#12603) on Jun 6, 2026, 1:50 AM
tobiu closed this issue on Jun 6, 2026, 1:50 AM