Skip to content

D4: sequential capped enrichment convergence wave (#172) #176

Description

@xenodeve

Parent

Part of #172

What to build

Operator convergence wave: sequential secret-guarded dry-run-then-apply calls to generate-taxonomy and generate-case-studies (and cover backfill once D2 lands) until the published scoreboard shows material progress — without raising CASE_STUDY_MAX_PER_RUN above the safe default. Each apply is an intentional prod write; keep a running scoreboard comment on this issue. Close when need_tax/need_content are cleared for reachable README-backed rows (or remaining skips are documented: no README snapshot / no gh binding).

Acceptance criteria

  • Scoreboard comment: before/after has_cat, has_content, has_shot, need_tax, need_content
  • Applies stay capped and sequential; no unbounded single request
  • Human-owned fields remain untouched
  • Unreachable skips (no README snapshot) listed explicitly, not counted as failures

Blocked by

  • Prefers D1 for clearer eligible counts
  • Cover portion blocked by D2

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestready-for-agentFully specified, ready for an AFK agent

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions