Epic: Claracle Data Observatory Relaunch

[jmservera]

Epic: Claracle Data Observatory Relaunch

Reposition Claracle from time-first weekly summaries into a discoverable, linkable public database of GitHub technology trends.

• PRD: docs/prds/claracle-data-observatory-relaunch.md (Ready)
• BRD: docs/brds/claracle-data-observatory-relaunch-brd.md (BRD-CLARACLE-002 v1.0)
• Owner: Leela (Lead)

How the Squad works these issues (read first). These issues do not use RPI tooling. Each child issue spells out the work as three plain stages in order — 1) Research (understand), 2) Plan (decide the approach), 3) Implement (build) — followed by Test → Review → PR. Every step names the agent who owns it. Assign work by the squad:<member> label already on each issue. Reviewers (Fry for tests, Hermes for security, Nibbler for AI-safety) are listed as steps inside the issues, not as separate issues.

Guardrails (apply to every child issue)

• The weekly crawl/analysis pipeline is working and must not be modified — consume its data/ output only.
• Do not change the Podcaster handoff contract (scripts/podcaster_handoff.py) or config/podcast.json; the handoff smoke test must stay green.
• Keep markup.goldmark.renderer.unsafe = false — charts/tools ship as Hugo shortcodes/layouts, never raw HTML in content.
• CI must be correct, not just green. Verify rendered output for any site change.

Child issues

Wave 1 — Foundation

• Spike: evergreen data model + generation cost #595 Spike: evergreen data model + generation cost squad:bender type:spike
• Emit topics frontmatter from content generation (FR-002) #596 Emit topics frontmatter from content generation (FR-002) squad:farnsworth
• Topic hubs: layouts, highlights, dynamic lifecycle (FR-001/003/004) #597 Topic hubs: layouts, highlights, dynamic lifecycle (FR-001/003/004) squad:amy
• Structured on-page SEO metadata + schema (FR-030..034) #598 Structured on-page SEO metadata + schema (FR-030..034) squad:amy squad:zapp
• Connect GA4 + Google Search Console (FR-035) #599 Connect GA4 + Google Search Console (FR-035) squad:zapp
• Internal linking graph + CI link-check gate (FR-040/041) #600 Internal linking graph + CI link-check gate (FR-040/041) squad:amy squad:fry

Wave 2 — Data assets

• Data pages from the trend dataset (FR-010/011) #601 Data pages from the trend dataset (FR-010/011) squad:bender
• Repository pages with lifecycle handling (FR-020..022) #602 Repository pages with lifecycle handling (FR-020..022) squad:bender
• MIT datasets + State of statistics page (FR-050/053) #603 MIT datasets + "State of" statistics page (FR-050/053) squad:farnsworth

Wave 3 — Amplification

• Embeddable charts (FR-051) #604 Embeddable charts (FR-051) squad:amy squad:calculon
• Client-side interactive tool (FR-052) #605 Client-side interactive tool (FR-052) squad:amy
• SquadScope README as discovery engine (FR-060) #606 SquadScope README as discovery engine (FR-060) squad:farnsworth squad:calculon

Parallelization map

KICKOFF (4 streams can start immediately, in parallel):
  ├─ #595 Spike (Bender)            ── blocks Wave 2 data work
  ├─ #598 On-page SEO (Amy/Zapp)    ── independent
  ├─ #599 GA4 + GSC (Zapp)          ── independent
  └─ #606 README (Farnsworth)       ── independent

AFTER #595 defines the topic list + data model:
  Content track:  #596 ─▶ #597 ─▶ #600
  Data track (parallel with content track): #601 ∥ #602 ∥ #603
        (#602 links into #597 hubs — soft dependency, coordinate)

AFTER Wave 1 SEO (#598) + spike tool recommendation (#595):
  #604 Charts ∥ #605 Tool   (both parallel; #606 already done)

Can be spawned in parallel right now: #595, #598, #599, #606.
Serial chain (longest path): #595 → #596 → #597 → #600, and #595 → (#601 / #602 / #603) → #604 / #605.

Definition of done (epic)

All child issues merged; PRD success checklist (FR-030..035) validated; GA4 + GSC reporting; no regression to weekly pipeline or Podcaster handoff smoke.

[github-actions]

📋 Assigned to Leela (Lead)

Issue: #594 — Epic: Claracle Data Observatory Relaunch

Leela will pick this up in the next Copilot session.

For Copilot coding agent: If enabled, this issue will be worked automatically.
Otherwise, start a Copilot session and say:
Leela, work on issue #594