docs: update branding to Claracle and fix stale references (#450)
* docs: update branding to Claracle, fix stale references - README: rebrand to Claracle, update site URLs to claracle.com - distribution-strategy: update brand and URLs throughout - rollout-checklist: fix stale GitHub Models fallback claim (pipeline is Copilot-only, fail-closed) - processed/qa-report.md: add stale-content banner - processed/learning-audit.md: add stale-content banner Addresses items from docs/cleanup-candidates.md. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: update test to match Claracle URL in distribution strategy Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: address Copilot review comments on PR #450 - Remove non-existent /feed/ URL from README (only /index.xml exists) - Fix stale 'SquadScope' CTA in distribution-strategy.md - Rename rollout checklist section from 'fallback path' to 'fail-closed verification' Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Juan Manuel Servera committed
Jun 13, 2026 at 16:14 UTC
44a95fe977733a51bc9f9bd1bc32f7ca379c8715
6 files changed
+35
-30
README.md
+8
-8
@@ -1,12 +1,12 @@
1
[](https://github.com/jmservera/SquadScope/actions/workflows/crawl-and-publish.yml)
2
[](https://github.com/jmservera/SquadScope/actions/workflows/deploy-site.yml)
3
-# SquadScope
3
+# Claracle (SquadScope)
4
5
-SquadScope is an automated AI-powered GitHub Pages site that publishes weekly, monthly, and yearly summaries of tech trends sourced from GitHub. The system crawls trending and newly-created repositories, applies AI analysis to identify signal vs. noise, and publishes curated insights with zero manual intervention.
5
+Claracle is an automated AI-powered site that publishes weekly, monthly, and yearly summaries of tech trends sourced from GitHub. The system crawls trending and newly-created repositories, applies AI analysis to identify signal vs. noise, and publishes curated insights with zero manual intervention.
6
7
-## What is SquadScope?
7
+## What is Claracle?
8
9
-SquadScope solves the information overload problem in open-source development. Each week, millions of repositories are created or gain stars. SquadScope:
9
+Claracle solves the information overload problem in open-source development. Each week, millions of repositories are created or gain stars. Claracle:
10
11
1. **Crawls** GitHub API for new and trending repositories in a given week
12
2. **Analyzes** the data with Copilot to identify what's genuinely important vs. hype
@@ -18,7 +18,7 @@ Result: Curated tech trend insights delivered automatically every Monday.
18
19
## Architecture
20
21
-SquadScope uses a **5-stage pipeline** executed entirely in GitHub Actions:
21
+Claracle uses a **5-stage pipeline** executed entirely in GitHub Actions:
22
23
```
24
Crawl → Analyze → Generate → Deploy → Reskill
@@ -43,7 +43,7 @@ JSON Markdown Hugo Pages Improvements
43
44
**Stage 4: Deploy** (Hugo + GitHub Pages)
45
- Builds static site from Hugo and publishes to GitHub Pages
46
-- Outputs: Live website + RSS feeds at `https://jmservera.github.io/SquadScope/index.xml` and `https://jmservera.github.io/SquadScope/feed/`
46
+- Outputs: Live website + RSS feed at `https://www.claracle.com/index.xml`
47
48
**Stage 5: Reskill** (every 5th run)
49
- Every 5th run, Copilot reviews squad history and recent analysis outputs
@@ -64,8 +64,8 @@ JSON Markdown Hugo Pages Improvements
64
65
### For end users
66
67
-1. **Visit the site:** [SquadScope](https://jmservera.github.io/SquadScope/): Browse weekly, monthly, yearly summaries
68
-2. **Subscribe to RSS:** Add `https://jmservera.github.io/SquadScope/index.xml` or `https://jmservera.github.io/SquadScope/feed/` to your reader
67
+1. **Visit the site:** [Claracle](https://www.claracle.com/): Browse weekly, monthly, yearly summaries
68
+2. **Subscribe to RSS:** Add `https://www.claracle.com/index.xml` to your reader
69
3. **Check GitHub Releases:** New summaries also posted as releases
70
71
### For operators (see `docs/operator-guide.md` for full setup)
docs/growth/distribution-strategy.md
+19
-19
@@ -1,4 +1,4 @@
1
-# SquadScope Distribution Strategy
1
+# Claracle Distribution Strategy
2
3
**Version:** 1.0
4
**Last updated:** 2026-05-25
@@ -11,7 +11,7 @@
11
12
### Who Reads Weekly Trend Reports?
13
14
-SquadScope's audience spans three overlapping personas:
14
+Claracle's audience spans three overlapping personas:
15
16
1. **Signal-seeking developers** (40-50%)
17
- Want curated insights, not noise
@@ -55,16 +55,16 @@ SquadScope's audience spans three overlapping personas:
55
|---------|--------|-----------------|---------|-------|
56
| **Hacker News** | 5 min | 5K-15K impressions, 50-200 upvotes | Launch + selective weeklies (2-4/month) | Post 9:30-10 AM PST Wed/Thu. "Show HN" for launch only; regular posts must meet HN community standards (no self-promotion feel). Community votes up on genuine signal, downvotes noise. |
57
| **Lobsters** | 5 min | 1K-3K impressions, 20-60 upvotes | Weekly (if editorial quality high) | Strong signal-seeking audience. Moderated well; low spam. Posts link to site with discussion on-platform. |
58
-| **r/programming** | 5 min | 2K-8K impressions, 30-100 upvotes | Bi-weekly (avoid over-posting) | Active, semi-moderated. Respect community rules: no low-effort posts, link to SquadScope site. Engagement via comments is key. |
58
+| **r/programming** | 5 min | 2K-8K impressions, 30-100 upvotes | Bi-weekly (avoid over-posting) | Active, semi-moderated. Respect community rules: no low-effort posts, link to Claracle site. Engagement via comments is key. |
59
| **r/dataisbeautiful** | 3 min | 1K-4K impressions | Selective (when trends are viz-relevant) | High quality bar. Only post when article includes strong data visualization or trend data. |
60
| **r/MachineLearning** | 3 min | 1K-3K impressions | Selective (AI/agent/model weeks only) | Narrow relevance; post only when ML is primary signal. Expect high-signal audience but low traffic if off-topic. |
61
| **Mastodon** | 8 min | 300-1K impressions (federated) | Weekly (thread format) | Target @fosstodon, @techhub, @pixelfed instances. Thread format (5-7 toots). Audience skews FOSS+privacy. No direct link clickthrough expected; community building focus. |
62
| **Bluesky** | 8 min | 500-2K impressions | Weekly (thread format) | Early-adopter tech crowd. Thread format (3-5 posts). Higher retweet/engagement than Mastodon but smaller absolute reach. |
63
| **Twitter/X** | 8 min | 2K-10K impressions | Weekly (thread) | Broader reach; audience spans investors, founders, practitioners. Thread with call-to-action link. Expect 5-15% conversion to clicks. |
64
| **LinkedIn** | 10 min | 1K-5K impressions | Weekly (1-2 posts) | Focus on "Where Industry Meets Code" angle and ecosystem implications for tech leads. Share link + short excerpt. Engagement: modest but high intent. |
65
-| **dev.to** | 15 min | 2K-8K impressions | Weekly (full crosspost with canonical link) | Crosspost full article with `canonical_url` pointing back to SquadScope. Drives SEO authority back to site. Community-friendly audience. |
65
+| **dev.to** | 15 min | 2K-8K impressions | Weekly (full crosspost with canonical link) | Crosspost full article with `canonical_url` pointing back to Claracle. Drives SEO authority back to site. Community-friendly audience. |
66
| **Awesome-lists** | 10 min (one-time setup) | 100-500 impressions/month | Submit once per quarter | e.g., awesome-github-tools, awesome-open-source, awesome-ai-agents. One-time submission or annual update. Setup as a batch task. |
67
-| **GitHub Topics** | 5 min (one-time) | 50-200 impressions/month | Update as categories evolve | Add to SquadScope README: topics like `weekly-trends`, `github-insights`, `open-source-analysis`. One-time, minimal maintenance. |
67
+| **GitHub Topics** | 5 min (one-time) | 50-200 impressions/month | Update as categories evolve | Add to Claracle README: topics like `weekly-trends`, `github-insights`, `open-source-analysis`. One-time, minimal maintenance. |
68
| **Newsletter** | 20 min/week | 500-2K subscribers (TBD) | Weekly digest | Recommendation: **Buttondown** (see below). Auto-send Monday 9 AM UTC with week's article link + 3-5 key insights. |
69
70
---
@@ -75,15 +75,15 @@ SquadScope's audience spans three overlapping personas:
75
76
**Timing:** Wednesday 9:45 AM PST (post time drives visibility on HN)
77
78
-**URL:** `https://jmservera.github.io/SquadScope/`
78
+**URL:** `https://www.claracle.com/`
79
80
-**Title:** Show HN: SquadScope – Weekly curated GitHub trends (AI agents, supply-chain security, noise filtering)
80
+**Title:** Show HN: Claracle – Weekly curated GitHub trends (AI agents, supply-chain security, noise filtering)
81
82
**Text:**
83
```
84
Hi HN,
85
86
-I built SquadScope, an automated system that crawls GitHub's new and trending repos
86
+I built Claracle, an automated system that crawls GitHub's new and trending repos
87
each week, applies AI analysis to separate signal from noise, and publishes curated
88
trend reports every Monday.
89
@@ -91,7 +91,7 @@ The problem I wanted to solve: GitHub's trending list is flooded with star-farm
91
(emulator kits, game unlockers, etc.), making it hard to spot genuine infrastructure
92
work. TechCrunch covers the funding layer; developers building tooling are invisible.
93
94
-SquadScope publishes:
94
+Claracle publishes:
95
- Weekly summaries (Mondays 8:30 AM UTC)
96
- Signal/noise breakdown (what's real, what's hype)
97
- Blind spots analysis (what's missing)
@@ -101,8 +101,8 @@ SquadScope publishes:
101
Stack: GitHub API crawl → Copilot CLI analysis → Hugo → GitHub Pages.
102
No closed model deps; OSS where possible.
103
104
-Two weeks of examples: https://jmservera.github.io/SquadScope/
105
-RSS: https://jmservera.github.io/SquadScope/index.xml
104
+Two weeks of examples: https://www.claracle.com/
105
+RSS: https://www.claracle.com/index.xml
106
107
Looking for feedback: Is this signal/noise split useful? Any categories you'd
108
prioritize differently?
@@ -141,7 +141,7 @@ This week's themes:
141
- Supply-chain security tooling becoming credible (Perplexity's bumblebee, Apple's corecrypto)
142
- Coordinated star-farm campaigns are escalating
143
144
-https://jmservera.github.io/SquadScope/
144
+https://www.claracle.com/
145
```
146
147
**Post 3:**
@@ -177,7 +177,7 @@ Feedback welcome. Boosts + follows appreciated.
177
**Timing:** Monday 12 PM UTC (2 hours after launch)
178
179
**Setup:** In dev.to post editor:
180
-- **Canonical URL:** `https://jmservera.github.io/SquadScope/`
180
+- **Canonical URL:** `https://www.claracle.com/`
181
- **Series:** "SquadScope Weekly" (so all posts thread together)
182
- **Tags:** `github` `trends` `opensource` `analysis`
183
@@ -188,7 +188,7 @@ Feedback welcome. Boosts + follows appreciated.
188
Every Monday, SquadScope publishes an automated analysis of the week's most important
189
new GitHub repositories, separated into signal and noise, with correlation to industry press.
190
191
-This is the dev.to crosspost; the canonical article lives here: https://jmservera.github.io/SquadScope/
191
+This is the dev.to crosspost; the canonical article lives here: https://www.claracle.com/
192
193
## The Story This Week
194
@@ -199,7 +199,7 @@ campaign the crawl has caught.
199
[Full article link below]
200
201
---
202
-*Read the full analysis on SquadScope:* https://jmservera.github.io/SquadScope/
202
+*Read the full analysis on Claracle:* https://www.claracle.com/
203
```
204
205
**Expected outcome:** 200-800 impressions, 5-20 reactions, 30-100 click-throughs to canonical URL.
@@ -212,7 +212,7 @@ campaign the crawl has caught.
212
213
**Input:** `content/weekly/2026/W22.md` (published Monday 8:30 AM UTC)
214
215
-**Before promotion:** Read the public [Methodology and corrections policy](../../content/methodology/_index.md) and link the live methodology page (`https://jmservera.github.io/SquadScope/methodology/`) in launch/crosspost context when space allows. Do not promote an article as neutral or comprehensive; frame it as GitHub- and current-source-based analysis with known source, language, and platform limits.
215
+**Before promotion:** Read the public [Methodology and corrections policy](../../content/methodology/_index.md) and link the live methodology page (`https://www.claracle.com/methodology/`) in launch/crosspost context when space allows. Do not promote an article as neutral or comprehensive; frame it as GitHub- and current-source-based analysis with known source, language, and platform limits.
216
217
**Step 1: Extract key angles** (5 min)
218
- Skim article for 3-5 "most quotable" sections
@@ -228,7 +228,7 @@ GitHub is experiencing metric inflation via coordinated star farming"
228
```
229
230
**Step 2: Draft HN post** (5 min)
231
-- Title: `Show HN: SquadScope – [hook here]`
231
+- Title: `Show HN: Claracle – [hook here]`
232
- Text: ~200 words covering: problem, what SquadScope does, this week's themes, RSS link
233
- Save as `.squad/posts/2026-W22-hn.txt`
234
@@ -385,7 +385,7 @@ Create issue `feat(seo): metadata audit fixes (#185)` with:
385
### Standard UTM Structure
386
387
```
388
-https://jmservera.github.io/SquadScope/?utm_source={channel}&utm_medium={medium}&utm_campaign={campaign}
388
+https://www.claracle.com/?utm_source={channel}&utm_medium={medium}&utm_campaign={campaign}
389
```
390
391
### Channel-Specific UTM Names
@@ -438,7 +438,7 @@ Before GA4, log weekly:
438
439
**Setup workflow:**
440
1. Create Buttondown account (https://buttondown.email)
441
-2. Configure RSS-to-email trigger pointing to `https://jmservera.github.io/SquadScope/index.xml`
441
+2. Configure RSS-to-email trigger pointing to `https://www.claracle.com/index.xml`
442
3. Set delivery: Monday 9 AM UTC (1.5 hours after article publish)
443
4. Template: Auto-generated from RSS feed (title + excerpt + link)
444
5. Custom intro: "New SquadScope analysis just dropped. Here's this week's trends:" + RSS excerpt
docs/processed/learning-audit.md
+2
@@ -1,5 +1,7 @@
1
# SquadScope Learning System Audit
2
3
+> **⚠️ Archived / Partially Stale (as of 2026-06-13):** Some claims (e.g., no reskill job, no `.squad/skills/` directory, no run-counter support) no longer match the current repository. See the live workflows and `.squad/` directory for the current learning system state.
4
+
5
**Author:** Leela (Lead/Architect)
6
**Date:** 2026-05-18T13:20:07.067+02:00
7
**Scope:** End-to-end audit of the learning system — can SquadScope actually learn in production?
docs/processed/qa-report.md
+2
@@ -1,5 +1,7 @@
1
# SquadScope QA Report
2
3
+> **⚠️ Archived / Partially Stale (as of 2026-06-13):** Some claims in this report (e.g., deploy workflow not building Pagefind, reskill being a placeholder) no longer reflect the current implementation. Refer to the live workflows and `docs/pipeline-validation.md` for canonical operational truth.
4
+
5
_Date:_ 2026-05-18
6
_Issue:_ #24 — Final QA readiness review and reskill-cycle simulation
7
_Agent:_ Fry
docs/rollout-checklist.md
+3
-2
@@ -120,10 +120,11 @@ Use this checklist to verify your SquadScope instance is ready for production. C
120
- [ ] Generate: `python3 scripts/generate_content.py data/analyzed/YYYY-WNN-summary.md`
121
- [ ] Build search assets after Hugo: `npx pagefind --site public/`
122
123
-- [ ] **Fallback analysis path works (Copilot unavailable scenario)**
123
+- [ ] **Copilot auth failure handling (fail-closed verification)**
124
- [ ] Comment out or rename `COPILOT_GH_TOKEN` secret temporarily
125
- [ ] Manually trigger workflow
126
- - [ ] Verify workflow still completes but uses GitHub Models API
126
+ - [ ] Verify workflow fails cleanly with a clear error (no fallback — pipeline is Copilot-only, fail-closed)
127
+ - [ ] Confirm token-renewal issue automation triggers if configured
128
- [ ] Restore secret after testing
129
130
- [ ] **Reskill cycle verified (after 5 runs)**
tests/test_site_policy_links.py
+1
-1
@@ -36,5 +36,5 @@ def test_methodology_is_in_navigation_and_distribution_guidance() -> None:
36
assert "identifier = 'methodology'" in hugo_config
37
assert "url = '/methodology/'" in hugo_config
38
assert "Methodology and corrections policy" in distribution
39
- assert "https://jmservera.github.io/SquadScope/methodology/" in distribution
39
+ assert "https://www.claracle.com/methodology/" in distribution
40
assert "Do not promote an article as neutral or comprehensive" in distribution