Skip to content

EPIC: General extraction and canonicalization #4

Description

@kmosoti

Outcome

Non-fixture source spans can produce validated graph candidates through a provider-abstracted LLM boundary.

Scope

  • LLM adapter interface
  • Extraction Pydantic schemas
  • Prompt contracts
  • General source span extraction service
  • Title normalizer and alias service
  • Graph writer
  • Extraction audit trail

Source Docs

  • docs/01-requirements.md: Extraction, Canonicalization
  • docs/07-engineering-standards.md: Protocol Rules, Contracts, Token And LLM Cost Controls

Done When

  • LLM outputs validate through schemas.
  • Invalid outputs fail safely.
  • Extracted nodes/edges retain source span provenance.
  • Deterministic transforms are not delegated to the LLM.

Metadata

Metadata

Assignees

Labels

architectureArchitecture and system designepicEpic-level planning issueextractionStructured extraction and canonicalizationmvpRequired for MVP

Projects

Status
Todo

Relationships

None yet

Development

No branches or pull requests

Issue actions