Skip to content

[Context] Enrich artist research with dated sources and incremental reuse #2129

Open

Description

@sswiftdrtv

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

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

  1. added
    enhancementNew feature or request
    priority:P0Required for the first shared Sites and external Widgets release
    on Sep 20, 2026
  2. sidneyswift commented on Nov 6, 2026

    @sidneyswift
    Collaborator

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestpriority:P0Required for the first shared Sites and external Widgets release

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions