AletheiaFact / AletheiaFact/aletheia

PROC-4 · Investigate cross-checking slowness in production

Offen
#2,502 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
backlog needs-investigation performance
Vorherrschende Sprache
TypeScript
Sterne
55
Forks
20
Ø Merge
2 T. 6 Std.
Gemergte PRs (30 T.)
2

Beschreibung

> Item derived from the fact-checking cycle analysis (**2026-07-03, v2**). ⚠️ Reconciled — read D1 below.

### Finding (reconciled — see D1)
Even in `main` alone, cross-checking went from **~6.6 h (2024) → ~69.8 h (2025–26)** — a **real** slowdown, not just composition. What *is* inflated is the "3× vs. 19.7 h" contrast: the 21.2 h historical figure is deflated by 2022–23 (~0 h, cross-check barely existed).

### Action
Investigate the cause (fewer cross-checkers available? more complex tasks? process change?) **before** setting a target.

### Reconciliation (D1) — real slowdown vs. cohort artifact (PROC-4 × INST-11)
Both, but separable. In pure `main`, 2024 (6.6 h) → 2025–26 (69.8 h) is **real slowdown** — not namespace composition. What *is* an artifact is the "21.2 h historical → ~70 h" contrast, because the historical blend is deflated by 2022–23 (~0 h). **Wording to adopt:** "there was real slowdown in production; do not cite the '3× vs. 19.7 h' as exact — always compare current state vs. 2024/2025 within `main`."

### Impact
Avoids optimizing the wrong stage; may reveal a capacity problem.

---
- **Priority:** 🟡 Medium
- **Dependencies:** a more precise reading depends on INST-2 (#2492); reconcile wording with INST-11.
- **Epic:** #2490

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

Start with the fact-checking cycle analysis dated 2026-07-03 and compare the main-only 2024 and 2025–26 cross-checking figures. Read INST-2 (#2492) first where available and reconcile wording with INST-11; done means identifying whether capacity, task complexity, or process change explains the slowdown before setting a target.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Bereich
performance
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Ruhig
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
45/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.