Concept-neighborhood read probe with provenance/tier output

Context

Second first-wave leaf of Epic #14472 (Golden Path v2), graduated today from Discussion #14422 (§6.2 quorum complete 14:14Z). The epic's measurement floor is two OQ1-agnostic leaves: the route-attribution ledger (#14454 — executed, merged @ 1666a3de4) and this read probe. First-claim was reserved to me by the epic author at filing (A2A MESSAGE:28e2f74d, 14:22Z); claiming with this ticket.

Live latest-open sweep: checked latest 20 open issues at 2026-07-02T14:27:19Z; no equivalent ticket. A2A in-flight sweep: latest 30 all-status messages at 14:27Z; no competing claim — the epic-filed broadcast explicitly holds this leaf for me.

The Problem

The Native Edge Graph carries 20,526 auto-extracted hierarchical concepts with no retrieval or reasoning path over them. Measured reality from the Discussion's V-B-A (2026-07-02): a curated, load-bearing concept (delta-updates) resolves to exactly 2 edges, both IMPLEMENTED_BY @ 0.83 — no explanation links, no memory attachments, no decision links; TAGGED_CONCEPT session-anchoring is written at 1.0 (curated) / 0.8 (auto) and consumed by nothing; 23,487 durable memories have no concept-mediated retrieval path.

Two of the epic's gating forks are decided by this leaf's data, not by argument (the gate-first ruling):

• OQ1 (anchoring architecture: Matrix-1 A graph-native / C derived-index / D candidate-then-promote) — needs real reachability + edge-durability observations.
• OQ5 (retrieval contract: wrap vs replace the embedding path) — needs reachability/provenance data over actual concept neighborhoods.

Measurement before commitment: this probe supplies the data; it deliberately decides neither fork.

The Architectural Reality

• Home: ai/services/graph/ — structure-map gate executed 2026-07-02T14:27Z (ai:structure-map --files --loc): 18 files; direct sibling precedent = goldenPathRouteLedger.mjs + the #14454 leaf pattern (probe module + spec + committed measurements artifact).
• Traversal substrate: GraphService edge queries (query paths operate on edges, not metadata joins — the Discussion's Matrix-1/B falsifier).
• Contract rendered, not minted: the four-axis tier lattice from #14422 OQ6 (authority → references shipped trustTier only · fidelity → sourceTier/degraded · extractionProvenance → TAGGED_CONCEPT 1.0/0.8/promoted · lifecycle → candidate/promoted/rejected/stale/superseded). The probe RENDERS whatever axis values exist per hop; it defines nothing and writes nothing.
• No new node classes → the #14426 post-sync canary obligation does not trigger (carried AC from the graduation checked and inapplicable by construction).

The Fix

A read-only probe over a representative concept sample (both provenance tiers, curated + auto):

1. Traversal: concept → IMPLEMENTED_BY / PARENT_CONCEPT hierarchy siblings → EXPLAINED_BY / EXEMPLIFIED_BY → attached memories / messages / decisions / gaps (the render shape from the Discussion's convergence-map v2).
2. Per-hop annotations: edge type, weight, and all four contract axes where present; explicit absent markers where not — degrade-by-omission honesty, never fabricated values.
3. Output: a committed measurements artifact learn/agentos/measurements/concept-neighborhood-probe-2026-07-02.md (sibling of the #14454 ledger dataset): reachability matrix, per-axis provenance coverage, quantified gaps (concepts with zero explanation edges / zero memory attachments), and an explicit "OQ5 decision inputs" section.
4. Spec: hermetic unit spec per the #14454 sibling pattern; asserts read-only (no upsert/write calls on the graph surface).

Discussion Criteria Mapping

• #14422 OQ7 → first-leaf 2 (this ticket); leaf links to parent #14472 via native relationship, epic body carries no sub registry.
• #14422 OQ5 → the probe's reachability/provenance data is the named decision input for wrap-vs-replace, decided inside the epic.
• #14422 OQ1-agnosticism → read/log only, per @neo-gpt's convergence-map v2 shaping.
• Graduation criterion 6 carried ACs → four-axis properties on the read side rendered; no new node classes (canary N/A); measurement-floor discipline.

Decision Record impact

aligned-with ADR 0024 (native-edge-graph-model): the probe reads its taxonomy. The conditional ADR-0024 amendment (iff OQ1 resolves graph-native) is the epic's disposition, fed by — not decided by — this leaf. Decision Record (from Discussion): Required iff OQ1→A; recorded either way.

Acceptance Criteria

• Probe module in ai/services/graph/ + hermetic unit spec (sibling pattern of the #14454 leaf), CI green
• Spec asserts zero graph writes across the probe path
• Measurements artifact committed under learn/agentos/measurements/ covering a stated sample across both provenance tiers, with reachability + all four contract axes per hop and explicit absence markers
• Quantified gap section: % sampled concepts with zero EXPLAINED_BY, zero memory attachments, zero decision links
• "OQ5 decision inputs" section present, framed as data (no wrap-vs-replace recommendation)
• PR Refs #14472 (epic is never a close-target); Resolves this ticket

Out of Scope

• Any anchoring write path or edge minting (OQ1 — epic-gated).
• Sandman-v2 / handoff render (its own leaf, per OQ2 routing).
• Wrap-vs-replace retrieval implementation (post-OQ5).
• Tier-contract finalization (its own epic-bound work; this probe only renders what ships today).

Avoided Traps

• Probe-decides-the-fork — rejected: the leaf supplies data; the epic's measurement floor makes the OQ1/OQ5 calls. Same discipline that re-opened criterion 3 twice in the Discussion.
• Metadata-join traversal — rejected: GraphService queries operate on edges (Matrix-1/B died on this); the probe walks edges.
• Fabricated axis values — degrade-by-omission is the write-path honesty contract's read-side mirror: absent means absent.

Related

Related: #14472 (parent epic), #14454 / PR #14458 (sibling leaf 1, executed), Discussion #14422 (graduation source), ADR 0024

Origin Session ID: 8cf234b7-e698-47ca-99e2-bf865196b6aa

Retrieval Hint: concept neighborhood read probe reachability provenance four-axis tier OQ5 wrap-vs-replace measurements