chore: record hierarchy refresh and analysis direction
Records safe rerun hierarchy refresh, product focus, same-day source reuse, and analysis decomposition direction.
Juan Manuel Servera committed
Jun 5, 2026 at 23:12 UTC
084c25b5f02122cdf86bb3e71c085a13fe567503
4 files changed
+67
.squad/agents/farnsworth/history.md
+1
@@ -43,3 +43,4 @@
43
- 548 tests passing
44
- Ready for merge
45
- 2026-06-05T17:42:56Z: Analysis map/reduce should be justified by context pressure and claim quality, not crawl speed; mappers should emit cited claim ledgers while a single reducer preserves global thesis, dedupe, citations, and the analysis gate contract.
46
+- 2026-06-05T20:57:09Z: Best analysis decomposition candidate is signal-type claim-ledger map/reduce with deterministic preflight compaction, optional hierarchical repo/source sub-mappers only above budget triggers, one reducer/final writer for global thesis and voice, and critic passes as QA rather than competing article writers.
.squad/agents/fry/history.md
+5
@@ -98,3 +98,8 @@
98
99
- Matrix crawl should be gated by deterministic shared run context, per-leg artifacts, fan-in checksums, optional-vs-required failure policy, and explicit rate-limit budgets; GitHub search fan-out is riskier than RSS fan-out because search quota is already the tight limit.
100
- Map/reduce analysis is promising for context reduction only if mapper outputs are schema-validated, reducer output preserves citations and contradictions, and the final markdown still passes the existing analysis gate with current fallback paths retained.
101
+
102
+## Analysis decomposition QA recommendation (2026-06-05T20:57:09Z)
103
+
104
+- Signal-type hierarchical map/reduce is the lowest-risk analysis decomposition MVP because it matches current raw payload boundaries, is fixture-testable, and can run sidecar-first without overwriting the existing Copilot -> GitHub Models -> no-AI publish path.
105
+- Map/reduce must not become publishable until mapper/reducer schemas, citation bindings, rejected-claim/contradiction sidecars, final `analysis_gate.py` compliance, fallback preservation, and A/B quality metrics pass.
.squad/agents/leela/history.md
+1
@@ -45,3 +45,4 @@
45
- Labels: `squad`, `squad:leela`, `squad:bender`, `go:yes`
46
- Decisions recorded in .squad/decisions.md under four entries (Bender, Farnsworth, Fry, Leela)
47
- 2026-06-05T17:42:56.819+00:00 matrix/map-reduce PRD note: treat crawl matrix and analysis decomposition as separate decisions; keep crawl fan-out measurement-gated, while map/reduce is a citation-preserving LLM context/quality experiment with mapper claim ledgers and reducer-owned editorial coherence.
48
+- 2026-06-05T21:03:35.661+00:00 issue hierarchy refresh: updated #248-#259 and created #261 so safe weekly reruns preserve good AI-authored articles, treat no-AI fallback as non-publishable replacement by default, reuse successful same-day per-source evidence artifacts with provenance/freshness guards, and make signal-type claim-ledger map/reduce the selected dry-run analysis architecture.
.squad/decisions.md
+60
@@ -1,3 +1,63 @@
1
+# Leela — Issue hierarchy refresh for safe weekly analysis reruns
2
+
3
+- Date: 2026-06-05T21:03:35.661+00:00
4
+- Lead: Leela
5
+- Parent epic: #248
6
+- New child: #261
7
+
8
+## Product north star
9
+
10
+SquadScope's core product is high-quality AI trend analysis and article generation. Crawling and scrape artifacts are supporting evidence systems: they should improve freshness, provenance, and analysis reliability, but they are not the product focus.
11
+
12
+## Immediate safety objective
13
+
14
+Bad, failed, degraded, stale-evidence-backed, or no-AI fallback reruns must not overwrite a previously good weekly article. A good AI-authored weekly article remains the default last-known-good artifact unless an explicit, audited force/restore path is selected.
15
+
16
+## Final hierarchy
17
+
18
+- #248 — Parent epic: protect published weekly analysis from unsafe reruns and state the AI analysis/article-generation north star.
19
+- #249 — Candidate staging and publish eligibility manifest, including AI provenance, source artifact provenance, freshness/reuse, and gate results.
20
+- #250 — Preserve existing good weekly analysis on failed/degraded/no-AI/stale-evidence reruns.
21
+- #251 — Block no-AI fallback from replacing AI-authored weekly summaries by default.
22
+- #252 — Explicit safe rerun modes and restore controls; normal reruns reuse valid same-day source artifacts and process only missing/stale sources.
23
+- #253 — Immutable backups and publish-branch concurrency safeguards with source provenance preserved.
24
+- #254 — Atomic weekly promotion across analyzed artifacts, content, deploy, and notifications.
25
+- #255 — Stronger analysis publish gate beyond structural validation, focused on editorial/evidence/provenance quality.
26
+- #256 — Deterministic preflight compaction and fallback policy, aligned to future signal-type map/reduce slices.
27
+- #257 — Overwrite-protection, safe-rerun idempotency, same-day reuse, and stale-evidence regression tests.
28
+- #258 — Selected signal-type claim-ledger map/reduce dry-run: deterministic preflight; mappers for `new_repos`, `trending_repos`, `press_correlations`, and `prior_continuity`; reducer/editorial planner; one final writer; critic/QA gates.
29
+- #259 — Safe rerun, force-replace, restore, no-AI, same-day reuse, and map/reduce dry-run operator docs.
30
+- #261 — Reuse successful same-day source scrape artifacts on rerun, with per-source reuse, missing/stale detection, freshness/date guard, deterministic fan-in/dedupe, and artifact provenance.
31
+
32
+## Rationale
33
+
34
+The hierarchy now prioritizes analysis safety and generated article quality before crawl mechanics. The crawler-related work is framed as evidence freshness and provenance, especially avoiding redundant same-day source scrapes while still detecting missing or stale sources. The map/reduce work is no longer a broad exploration: it is explicitly the signal-type claim-ledger architecture from the PRD and remains dry-run until safety, publish, and QA gates are complete.
35
+
36
+## GitHub changes made
37
+
38
+- Edited #248-#259 to clarify priorities, dependencies, and acceptance criteria.
39
+- Created #261 for same-day source scrape artifact reuse.
40
+- Added parent comment on #248 linking #261 and summarizing the refreshed hierarchy.
41
+- Added child comment on #261 linking it back to #248.
42
+
43
+---
44
+
45
+### 2026-06-05T21:01:05.160+00:00: User directive — Product focus
46
+
47
+**By:** jmservera (via Copilot)
48
+**What:** SquadScope is not a scraper; the core purpose is AI analytics and article generation. The product should prioritize trend analysis quality and generated articles over crawl mechanics.
49
+**Why:** User request — captured for team memory
50
+
51
+---
52
+
53
+### 2026-06-05T21:02:36.076+00:00: User directive — Same-day source reuse
54
+
55
+**By:** jmservera (via Copilot)
56
+**What:** Do not repeat successful scraping jobs for the same source on the same day. If a source has already been scraped successfully today, reruns should reuse the latest same-day scrape for that source and continue with the next missing or stale source.
57
+**Why:** User request — captured for team memory
58
+
59
+---
60
+
61
# Fry: quality gate fallback hardening
62
63