Part of #14310. Discovered by #14333 capability-coverage audit. Refs #14310, #14333.
Context
The #14333 audit found a concrete mismatch between the current guide-gap output and the Concept Ontology coverage model. resources/content/sandman_handoff.md currently reports golden-path and native-edge-graph as GUIDE_GAPs, but current docs already explain both concepts across learn/agentos/DreamPipeline.md, learn/agentos/MemoryCore.md, learn/benefits/ArchitectureOverview.md, and ADR 0024.
This is not a call to write another speculative guide first. The issue is that the curated ontology edges are stale/incomplete, so the deterministic gap detector cannot see the guide coverage that already exists.
Live latest-open sweep: checked latest 20 open issues at 2026-06-29T13:51:00Z; no equivalent found. Exact GitHub search for Golden Path ontology coverage EXPLAINED_BY Native Edge Graph returned no issue. A2A in-flight sweep of latest 30 messages found no competing [lane-claim] / [lane-intent] for this exact scope. Grace's #14310 grounding-hardening message MESSAGE:348a6cf4-d6e1-417b-bfd4-6efe2f6ef721 was read before filing and is incorporated below.
The Problem
GapInferenceEngine.inferConceptGraphGaps() emits [GUIDE_GAP] when a high-weight concept has no outbound EXPLAINED_BY edge. That is correct behavior for the graph substrate. The false-positive shape is in .neo-ai-data/concepts/edges.jsonl: golden-path and native-edge-graph have implementation/relationship edges but no EXPLAINED_BY edges.
Current evidence:
.neo-ai-data/concepts/edges.jsonl has dream-pipeline -> golden-path and memory-core -> native-edge-graph PARENT_CONCEPT edges.
.neo-ai-data/concepts/edges.jsonl has golden-path -> native-edge-graph and golden-path -> knowledge-base REQUIRES edges.
.neo-ai-data/concepts/edges.jsonl has golden-path -> file:ai/daemons/DreamService.mjs and native-edge-graph -> file:ai/mcp/server/memory-core/services/GraphService.mjs IMPLEMENTED_BY edges.
.neo-ai-data/concepts/edges.jsonl has dream-pipeline -> file:learn/agentos/DreamPipeline.md, memory-core -> file:learn/agentos/MemoryCore.md, and agent-os -> file:learn/agentos/ConceptOntology.md EXPLAINED_BY edges, but none for golden-path or native-edge-graph.
resources/content/sandman_handoff.md currently reports both golden-path and native-edge-graph under Guide Disconnects.
The Architectural Reality
The Concept Ontology is a git-versioned JSONL semantic stratum at .neo-ai-data/concepts/. ConceptIngestor projects it into the Native Edge Graph. GapInferenceEngine then does deterministic edge traversal; it does not perform semantic doc search, so a guide that explains the concept is invisible unless the curated ontology has the right EXPLAINED_BY edge.
ADR 0024 frames this as part of the active Native Edge Graph model: the JSONL ontology is the curated, PR-reviewable layer, and the SQLite graph is the runtime layer consumed by DreamService / Golden Path / handoff generation. This ticket is aligned with ADR 0024; it keeps the curated ontology consistent with the guide reality instead of teaching downstream agents to ignore sandman_handoff.md gaps.
The Fix
Perform the inherited #14310 grounding discipline before editing:
- Memory-mine: query Memory Core for prior Golden Path / Native Edge Graph / Concept Ontology coverage work.
- Use the subsystem's own tools and artifacts: inspect
.neo-ai-data/concepts/nodes.jsonl, .neo-ai-data/concepts/edges.jsonl, resources/content/concepts/golden-path.md, resources/content/concepts/native-edge-graph.md, learn/agentos/DreamPipeline.md, learn/agentos/MemoryCore.md, learn/benefits/ArchitectureOverview.md, learn/agentos/decisions/0024-native-edge-graph-model.md, and the generated resources/content/sandman_handoff.md.
- V-B-A against current code: verify
ConceptIngestor and GapInferenceEngine still consume EXPLAINED_BY as described before changing the ontology.
Then add the minimal curated coverage edges needed to make the concept graph truthful. Likely candidates, to be verified during implementation:
golden-path -> file:learn/agentos/DreamPipeline.md as EXPLAINED_BY.
native-edge-graph -> file:learn/agentos/MemoryCore.md and/or file:learn/benefits/ArchitectureOverview.md / ADR 0024 as EXPLAINED_BY, depending on which artifact actually explains the reader-facing concept at guide altitude.
After the edit, run the relevant ingestion/gap-generation path or a focused equivalent that proves these two concepts no longer emit GUIDE_GAP while preserving legitimate gap signals.
Contract Ledger Matrix
| Target Surface |
Source of Authority |
Proposed Behavior |
Fallback |
Docs |
Evidence |
.neo-ai-data/concepts/edges.jsonl |
learn/agentos/ConceptOntology.md + ADR 0024 |
Add truthful EXPLAINED_BY edges for golden-path and native-edge-graph only after source-grounding the referenced guide(s). |
If no existing guide actually explains one concept at reader altitude, do not add a false edge; comment back to #14333 with the missing-guide finding. |
ConceptOntology.md; referenced guide(s). |
JSONL diff + validation that each line parses and points at existing files. |
resources/content/sandman_handoff.md Guide Disconnects |
GapInferenceEngine.inferConceptGraphGaps() |
Regenerated or focused gap evidence should stop reporting golden-path / native-edge-graph as GUIDE_GAP after the coverage edges exist. |
If full handoff regeneration is too broad, run a focused graph/ontology check over outbound edges and document why full regeneration is deferred. |
Existing handoff docs; PR evidence. |
Command output showing outbound EXPLAINED_BY edges and no false GUIDE_GAP for these concepts. |
| #14333 gap matrix |
#14333 audit checkpoint |
Mark this as the first spawned concrete sub from the audit; keep future subs source-verified before creation. |
If implementation proves the edge fix insufficient, update #14333 with the exact remaining substrate gap. |
#14333 comment thread. |
Link this ticket and its PR back to #14333. |
Decision Record Impact
Aligned with ADR 0024 (learn/agentos/decisions/0024-native-edge-graph-model.md). This ticket does not change the Native Edge Graph model; it keeps the curated concept ontology layer consistent with that model.
Acceptance Criteria
Out of Scope
- Writing a new Golden Path or Native Edge Graph conceptual guide unless the grounding pass proves existing docs do not explain the concept.
- Reworking the whole Concept Ontology, adding examples, or resolving unrelated
GUIDE_GAP, EXAMPLE_GAP, ORPHAN_CONCEPT, or CONCEPT_REVERIFY_DUE signals.
- Changing
GapInferenceEngine semantics. The detector is doing the right kind of deterministic edge traversal; the coverage data is the stale part.
Related
- Parent epic: #14310
- Discovery/audit ticket: #14333
- Current guide-gap output:
resources/content/sandman_handoff.md
- Concept ontology guide:
learn/agentos/ConceptOntology.md
- Native Edge Graph model:
learn/agentos/decisions/0024-native-edge-graph-model.md
Origin Session ID: 019f1258-24e1-7f51-9b09-e366d653430a
Retrieval Hint: query_raw_memories("#14333 Golden Path Native Edge Graph ontology EXPLAINED_BY guide gap false positive")
Part of #14310. Discovered by #14333 capability-coverage audit. Refs #14310, #14333.
Context
The #14333 audit found a concrete mismatch between the current guide-gap output and the Concept Ontology coverage model.
resources/content/sandman_handoff.mdcurrently reportsgolden-pathandnative-edge-graphasGUIDE_GAPs, but current docs already explain both concepts acrosslearn/agentos/DreamPipeline.md,learn/agentos/MemoryCore.md,learn/benefits/ArchitectureOverview.md, and ADR 0024.This is not a call to write another speculative guide first. The issue is that the curated ontology edges are stale/incomplete, so the deterministic gap detector cannot see the guide coverage that already exists.
Live latest-open sweep: checked latest 20 open issues at
2026-06-29T13:51:00Z; no equivalent found. Exact GitHub search forGolden Path ontology coverage EXPLAINED_BY Native Edge Graphreturned no issue. A2A in-flight sweep of latest 30 messages found no competing[lane-claim]/[lane-intent]for this exact scope. Grace's #14310 grounding-hardening messageMESSAGE:348a6cf4-d6e1-417b-bfd4-6efe2f6ef721was read before filing and is incorporated below.The Problem
GapInferenceEngine.inferConceptGraphGaps()emits[GUIDE_GAP]when a high-weight concept has no outboundEXPLAINED_BYedge. That is correct behavior for the graph substrate. The false-positive shape is in.neo-ai-data/concepts/edges.jsonl:golden-pathandnative-edge-graphhave implementation/relationship edges but noEXPLAINED_BYedges.Current evidence:
.neo-ai-data/concepts/edges.jsonlhasdream-pipeline -> golden-pathandmemory-core -> native-edge-graphPARENT_CONCEPTedges..neo-ai-data/concepts/edges.jsonlhasgolden-path -> native-edge-graphandgolden-path -> knowledge-baseREQUIRESedges..neo-ai-data/concepts/edges.jsonlhasgolden-path -> file:ai/daemons/DreamService.mjsandnative-edge-graph -> file:ai/mcp/server/memory-core/services/GraphService.mjsIMPLEMENTED_BYedges..neo-ai-data/concepts/edges.jsonlhasdream-pipeline -> file:learn/agentos/DreamPipeline.md,memory-core -> file:learn/agentos/MemoryCore.md, andagent-os -> file:learn/agentos/ConceptOntology.mdEXPLAINED_BYedges, but none forgolden-pathornative-edge-graph.resources/content/sandman_handoff.mdcurrently reports bothgolden-pathandnative-edge-graphunder Guide Disconnects.The Architectural Reality
The Concept Ontology is a git-versioned JSONL semantic stratum at
.neo-ai-data/concepts/.ConceptIngestorprojects it into the Native Edge Graph.GapInferenceEnginethen does deterministic edge traversal; it does not perform semantic doc search, so a guide that explains the concept is invisible unless the curated ontology has the rightEXPLAINED_BYedge.ADR 0024 frames this as part of the active Native Edge Graph model: the JSONL ontology is the curated, PR-reviewable layer, and the SQLite graph is the runtime layer consumed by DreamService / Golden Path / handoff generation. This ticket is aligned with ADR 0024; it keeps the curated ontology consistent with the guide reality instead of teaching downstream agents to ignore
sandman_handoff.mdgaps.The Fix
Perform the inherited #14310 grounding discipline before editing:
.neo-ai-data/concepts/nodes.jsonl,.neo-ai-data/concepts/edges.jsonl,resources/content/concepts/golden-path.md,resources/content/concepts/native-edge-graph.md,learn/agentos/DreamPipeline.md,learn/agentos/MemoryCore.md,learn/benefits/ArchitectureOverview.md,learn/agentos/decisions/0024-native-edge-graph-model.md, and the generatedresources/content/sandman_handoff.md.ConceptIngestorandGapInferenceEnginestill consumeEXPLAINED_BYas described before changing the ontology.Then add the minimal curated coverage edges needed to make the concept graph truthful. Likely candidates, to be verified during implementation:
golden-path -> file:learn/agentos/DreamPipeline.mdasEXPLAINED_BY.native-edge-graph -> file:learn/agentos/MemoryCore.mdand/orfile:learn/benefits/ArchitectureOverview.md/ ADR 0024 asEXPLAINED_BY, depending on which artifact actually explains the reader-facing concept at guide altitude.After the edit, run the relevant ingestion/gap-generation path or a focused equivalent that proves these two concepts no longer emit
GUIDE_GAPwhile preserving legitimate gap signals.Contract Ledger Matrix
.neo-ai-data/concepts/edges.jsonllearn/agentos/ConceptOntology.md+ ADR 0024EXPLAINED_BYedges forgolden-pathandnative-edge-graphonly after source-grounding the referenced guide(s).ConceptOntology.md; referenced guide(s).resources/content/sandman_handoff.mdGuide DisconnectsGapInferenceEngine.inferConceptGraphGaps()golden-path/native-edge-graphasGUIDE_GAPafter the coverage edges exist.EXPLAINED_BYedges and no falseGUIDE_GAPfor these concepts.Decision Record Impact
Aligned with ADR 0024 (
learn/agentos/decisions/0024-native-edge-graph-model.md). This ticket does not change the Native Edge Graph model; it keeps the curated concept ontology layer consistent with that model.Acceptance Criteria
EXPLAINED_BYedge(s) forgolden-pathandnative-edge-graphin.neo-ai-data/concepts/edges.jsonl.GapInferenceEngine/ ontology-edge check, or an equivalent source-grounded proof, showing these two falseGUIDE_GAPs are resolved.Out of Scope
GUIDE_GAP,EXAMPLE_GAP,ORPHAN_CONCEPT, orCONCEPT_REVERIFY_DUEsignals.GapInferenceEnginesemantics. The detector is doing the right kind of deterministic edge traversal; the coverage data is the stale part.Related
resources/content/sandman_handoff.mdlearn/agentos/ConceptOntology.mdlearn/agentos/decisions/0024-native-edge-graph-model.mdOrigin Session ID:
019f1258-24e1-7f51-9b09-e366d653430aRetrieval Hint:
query_raw_memories("#14333 Golden Path Native Edge Graph ontology EXPLAINED_BY guide gap false positive")