management/analysis/findings/F-016-self-documentation-is-honest.md

F-016: The repo names its own unresolved problems instead of presenting a clean face

category: works-well confidence: high

evidence:

• Known problems written down and filed as issues, verified present in analysis/data/gitlab_issues.json:
  • hosts/overmind.md:33-35 — "⚠️ gameserver … hat keinen Mirror … dort liegt auf Gitea ein gleichnamiges Repo mit anderem Stand" -> management#32, open. Verified true by measurement: git.lab d5c6ccb2e9 vs Gitea 48441a500f, diverged (F-007).
  • CLAUDE.md:63 — the gitops wiki branch is "ein überholter Mai-Abzug" -> management#19, open. Verified: head 0ff598e, 2026-05-14 (F-006).
  • Mirror failure going unnoticed -> management#28 "MIRROR-01", open.
  • Restore never rehearsed -> management#30, "Der Restore ist nie geprobt — Sicherungen sind bisher eine Vermutung".
  • CLAUDE.md:143-147 — the timestamp rule "schützt nur die Git-Historie", with push times, issue timestamps, pipelines and packages named as remaining exposure. Incomplete (F-002) but volunteered.
• CLAUDE.md:94-97 explains a rule by the damage its absence did, with numbers: 34 migrated issues carried title prefixes, "davon zwei mit einer anderen Aussage als ihr Label", and states the principle — "Zwei Wahrheiten über dieselbe Sache sind schlimmer als eine unvollständige."
• CLAUDE.md:149-158 ("Redlichkeit & gelebte Lehren") requires verified claims to be separated from suspicion, states "Korrelation ≠ Kausalität — ein plausibler Verdacht ist kein Befund", and closes with "Fehlschläge und übersprungene Schritte werden benannt, nicht geglättet; „fertig" heißt verifiziert."
• verfahren/retro/2026-08-09.md:70-71 records CI that was green while doing nothing (build_embedded "lud nie ein Artefakt hoch") and a published npm package of 12.5 KB instead of 12.8 MB — failures found and written down rather than quietly fixed.

impact: This is why the present analysis was possible at all. Most of the drift in this report was found by taking the repo's own statements seriously and checking them; that only works because the statements are specific, dated and falsifiable. A repo that wrote "Mirrors are configured" instead of "seven repos, these six product ones plus management" would have yielded no findings and no confidence either way.

root-cause pattern: Specific, falsifiable claims are a feature. Every finding in this report is downstream of a claim precise enough to be wrong.

neckbeard mechanism: This is AGENTS.md:50-55 almost verbatim — "Never claim something works without evidence: a test run, command output, a rendered result. 'Should work' is not a status" and "Uncertainty is reported, never swallowed. Flag your shakiest calls." It recurs at WORKFLOW.md:68 (Gate 3, "Shakiest calls: name the decisions you are least confident about") and WORKFLOW.md:113-114 (every session ends by answering which choices it is least confident about). WORKFLOW.md:137-139 completes it: "If the wiki has no confident answer, say so. Never file a low-confidence synthesis back as knowledge." The habit already exists here; neckbeard gives it fixed places to live rather than relying on the author's temperament.