1.2 KiB
1.2 KiB
Purpose
Canonical specification for article-tldr-summary requirements synced from OpenSpec change deltas.
Requirements
Requirement: System generates structured TL;DR summary for each fetched article
The system SHALL generate a concise summary artifact for each newly fetched article using Perplexity during ingestion.
Scenario: Successful summary generation
- WHEN a new article is accepted in ingestion
- THEN the system generates TL;DR bullet points and a concise summary body
- AND output is persisted in a structured, template-compatible format
Scenario: Summary generation fallback
- WHEN summary generation fails for an article
- THEN ingestion continues without failing the entire cycle
- AND the article remains available with existing non-summary content
Requirement: Summary storage includes citation and source context
The system SHALL persist source/citation information needed to render summary provenance.
Scenario: Persist source and citation metadata
- WHEN summary content is stored
- THEN associated source/citation fields are stored with the article summary artifact
- AND response payloads can render a "Source and Citation" section