Skip to content

Ingestion: evidence-bound entities/relations for add_note and add_event #49

@aurexav

Description

@aurexav

Summary

Extend ingestion (add_note, add_event) to produce evidence-bound entities and relations.

Problem

Graph schema alone is not useful until ingestion can deterministically and safely populate it.

In Scope

  • Extend deterministic add_note payload for explicit entity/relation input.
  • Extend add_event extraction contract for entity/relation output.
  • Validate evidence binding, scope, and policy constraints before persistence.
  • Persist graph writes through existing audit/version paths.

Out of Scope

  • Graph-aware ranking changes.
  • Cross-project relation linking.

Deliverables

  • API contract updates.
  • Extraction contract updates.
  • Validation and persistence logic.
  • Test coverage for accept/reject/update flows.

Acceptance Criteria

  • add_note supports explicit entity/relation writes.
  • add_event can extract and persist supported relations.
  • Invalid relations are rejected with reason codes and field paths.
  • Conflicting updates follow deterministic rules.

Dependencies

Implementation Checklist

  • Request/response schema changes.
  • Extractor output schema changes.
  • Validation and reason-code mapping.
  • Audit/version plumbing.
  • Integration tests for valid and invalid cases.

Done When

  • Both ingestion paths can create graph facts with the same trust boundaries as notes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:serviceRetrieval logic, ranking, and request orchestration.area:storagePostgres schema, SQL queries, and storage correctness.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