Origin Session ID: d5ed6767-0292-46bf-9346-439f268048ec
Context
The M4 Architectural Convergence (Epic #11077) shifts daemon and coordinator architecture from a fragmented polled model to an event-driven and strictly supervised model. Specifically, the Golden Path synthesis and GitHub Issue sync pipelines are currently inefficient and prone to staleness.
The Problem
- State Stagnation: The IssueCoordinator relied on a single-stage ingestion process that could operate on stale data.
- Polled Coordinators: The GoldenPathCoord was originally proposed as a polling coordinator, adding cognitive load and unnecessary intervals.
The Architectural Reality
The system is moving toward unified supervision and event-driven architectures.
- GitHub issues are managed locally as
.md files but ingestion into the graph must happen in a distinct second stage after the fetch to ensure freshness.
- Golden path modifications should be explicitly triggered via the
mutate_frontier MCP tool rather than polled on an interval.
The Fix
Implement a strict two-stage issue synchronization pipeline (fetch to local .md -> ingest to Graph). Replace the polled Golden Path logic with a direct mutate_frontier event-driven trigger.
Contract Ledger Matrix
| Target Surface |
Source of Authority |
Proposed Behavior |
Fallback |
Docs |
Evidence |
| Issue Sync Pipeline |
M4 Epic #11077 |
Two-stage: sync .md then ingest to graph |
Re-sync on failure |
None |
Ingestion accurately reflects latest local .md state |
mutate_frontier |
M4 Epic #11077 |
Triggers Golden Path synthesis directly upon mutation |
Emit failure event if synthesis errors |
None |
Synthesis log confirms execution post-mutation |
Acceptance Criteria
Out of Scope
- Expanding Golden Path synthesis logic beyond current triggers.
- Other coordinators (like Summarization) are unaffected.
Avoided Traps / Gold Standards Rejected
- Individual Polling Coordinators: Rejected polling for Golden Path because it creates unnecessary load and delay compared to an explicit event trigger when the frontier is mutated.
Related
Retrieval Hint: "Event-driven Golden Path Synthesis via mutate_frontier", "Two-stage GitHub Issue sync pipeline"
Origin Session ID: d5ed6767-0292-46bf-9346-439f268048ec
Context
The M4 Architectural Convergence (Epic #11077) shifts daemon and coordinator architecture from a fragmented polled model to an event-driven and strictly supervised model. Specifically, the Golden Path synthesis and GitHub Issue sync pipelines are currently inefficient and prone to staleness.
The Problem
The Architectural Reality
The system is moving toward unified supervision and event-driven architectures.
.mdfiles but ingestion into the graph must happen in a distinct second stage after the fetch to ensure freshness.mutate_frontierMCP tool rather than polled on an interval.The Fix
Implement a strict two-stage issue synchronization pipeline (fetch to local
.md-> ingest to Graph). Replace the polled Golden Path logic with a directmutate_frontierevent-driven trigger.Contract Ledger Matrix
.mdthen ingest to graph.mdstatemutate_frontierAcceptance Criteria
mutate_frontiersuccessfully triggers event-driven Golden Path synthesis.Out of Scope
Avoided Traps / Gold Standards Rejected
Related
Retrieval Hint: "Event-driven Golden Path Synthesis via mutate_frontier", "Two-stage GitHub Issue sync pipeline"