Skip to content

Search: graph relation context and explain integration #50

@aurexav

Description

@aurexav

Summary

Expose graph relation context in search and explain outputs without breaking current retrieval behavior.

Notes

  • Shipped in 35c9fe6 (2026-02-19).
  • relation_context is evidence-bound and bounded (configurable), and is omitted unless enabled.

Problem

Even with graph facts stored, users cannot benefit unless retrieval surfaces relation context and provenance.

In Scope

  • Add relation_context to search and explain payloads.
  • Resolve graph context under existing tenant/project/agent scope rules.
  • Keep ranking unchanged by default.
  • Add feature flag for optional graph-aware ranking experiments.

Out of Scope

  • Mandatory graph-based ranking.
  • Unbounded traversal over large neighborhoods.

Deliverables

  • API response extensions.
  • Explain payload extensions.
  • Trace persistence updates for graph provenance.
  • Compatibility tests for clients without graph fields.

Acceptance Criteria

  • Search returns bounded graph context when available.
  • Explain identifies which relations influenced context.
  • Existing clients remain compatible when graph context is absent.
  • Trace rows persist graph context provenance.

Dependencies

Implementation Checklist

  • Response schema updates.
  • Graph context resolver with bounds.
  • Explain integration.
  • Feature flag wiring.
  • Backward-compatibility tests.

Done When

  • Graph memory becomes visible and inspectable during retrieval.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:serviceRetrieval logic, ranking, and request orchestration.kind:featNew capability or product behavior that is not primarily a refactor or cleanup.theme:provenanceEvidence, citations, lineage, and explainability.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions