Repository navigation
Description
Parent epic: #2116
Priority and sequence
P0 within the Context Engine epic · CE13. Required for the first two-song/two-brief checkpoint.
Customer journey
A manager enters a second song by the same artist. Recoup keeps useful prior research, adds genuinely new evidence, and does not repeat the same search or replace history with a new paragraph.
Customer value and architecture
Build artist understanding across requests while controlling noise and cost.
Scope
- Use targeted topic/gap-driven research with explicit source/search/call/spend limits rather than unbounded crawling.
- Retain direct source attribution, publication/event/retrieval dates and precision; distinguish quotes, reported facts and interpretation.
- Separate collaborators and focal-artist evidence; repeated press-release copies count as one underlying source, not multiple confirmations.
- Reuse compatible fresh accepted research. New evidence updates affected topic documents while prior versions remain attributable; old interviews cannot silently redefine current identity.
- Keep source text untrusted and scoped; use selected GPT-6 Astra for synthesis where configured, recording actual prompts/model/provider/output and costs.
Acceptance criteria
- Second related URL reuses accepted artist identity and compatible research; only justified missing/stale topics invoke paid work.
- Conflicting statements retain provenance and uncertainty rather than blindly appending contradictory prose.
- Publication/event dates and copies of the same story affect freshness and corroboration correctly.
- Customer-private strategy stays scoped and cannot become public artist research.
- Each accepted statement/interpretation cites its inputs; research records no campaign idea as factual evidence.
Blocking dependencies
- [Context] Resolve provider identities and attach artists to the correct workspace #2119
- [Context] Run durable context requests with recoverable per-module execution #2122
- [Context] Authorize context spending and reconcile provider attempts with existing credits #2123
- [Context] Accept, reuse, correct and withdraw context without losing good history #2124
These are completion prerequisites, mirrored by native GitHub blocked-by links. Contracts, fixtures and independent scaffolding may begin earlier.
Execution gates
Paid search/model calls require CE07; scheduled paid refresh and broad backfills are excluded.
Validation
Two-song incremental run, duplicate article, historical interview, collaboration/name collision, malicious source, scoped private input and bounded research failure fixtures.
Owning implementation
API research/search adapters + artist topic synthesis
Delivery conventions
Shared API business logic serves HTTP, MCP and workers; clients do not duplicate it. Validate input with Zod and use the existing Supabase access layer. Database changes go through database-repository migrations and PRs. Use Vercel Workflows for new durable work. Reuse existing credits and record costs without exposing credentials or private traces. Every owning repository uses a feature branch and PR; distinguish fixture, local, merged and deployed verification.
Activity
sidneyswift commentedon Nov 6, 2026
Partly done. Artist research and source-discovery modules exist (recoupable/api#916), and the Sites pipeline runs attributed public artist research (recoupable/api#929).
Still open: dated source normalization and refresh planning (recoupable/api#1006, unmerged), duplicate-story corroboration rules, second-song incremental reuse, and spend authorization under recoupable/api#2123.