Real retrospective · reviewed public excerpts

When an earlier investigation changes a diagnosis

The monitor says a runner is idle. Does that mean it is dead, and what should I check before I plan a repair?

01 · CODING AGENTasks
02 · GRAPH AGENTplans
03 · CYPHERretrieves
04 · GRAPH AGENTchecks
05 · CODING AGENTacts
Graph agent plan

Research before running a diagnostic.

  1. Retrieve the prior investigation.
  2. Group copies by incident and source family.
  3. Read material counterexamples.
  4. Keep identical symptoms with different causes separate.
  5. Recheck current applicability before proposing an action.
Cypher 1

Count independent support.

MATCH (episode:YsgLessonDemoEpisode)-[:FROM_SOURCE]->
      (:YsgLessonDemoSource {source_id: $source_id})
WHERE episode.stance = 'supports'
RETURN count(episode) AS cited_occurrences,
       count(DISTINCT episode.incident_family_id) AS independent_incidents,
       count(DISTINCT episode.source_family_id) AS independent_source_families
passagesincidentssources
211

Two passages from one retrospective describe one incident family. They are two citations and one evidentiary source, not two independent votes.

Cypher 2

Read the contrary evidence.

MATCH (episode:YsgLessonDemoEpisode)-[:CITES]->(evidence:YsgLessonDemoEvidence)
WHERE episode.stance IN ['counterexample', 'unresolved']
RETURN episode.episode_id AS episode, episode.stance AS stance,
       episode.incident_family_id AS incident_family,
       episode.same_symptom AS same_symptom,
       evidence.excerpt AS selected_excerpt,
       evidence.excerpt_sha256 AS excerpt_sha256
ORDER BY stance, episode
kindcount
counterexample1
unresolved same-symptom incident1
BEFORE CITING A FIELD, ESTABLISH WHAT WRITES IT.

Role: support · excerpt 7a85a1af25d8

The habit that catches all of them costs seconds: find the writer before you
quote the reader.

Role: support · excerpt ebcfc002373b

Also worth stating: all three dead were idle, but two idle runners survived, so
"idle runners die" does NOT hold — I recorded that explicitly so nobody inherits
a false correlation.

Role: counterexample · excerpt f05990d2330b

OVER-AGGREGATION IS THE CHARACTERISTIC ERROR OF THIS SEAT. I was caught three
times in one night by IDENTICAL ERROR TEXT FROM A DIFFERENT CAUSE — a test file,
a verification_reason word-for-word identical to another note's, and a refusal
code. Adjacent-but-different failure codes are the highest-risk moment. Name the
shape a failure set has, say what it implies, and let the outliers stay outliers
rather than forcing one explanation over all of them.

Role: boundary · excerpt ce68d6c3e08c

Post-processing

Revise the lesson and retain the boundary.

MATCH (lesson:YsgLessonDemoLesson {lesson_id: $lesson_id})
RETURN lesson.original_hypothesis AS original_hypothesis,
       lesson.hypothesis_state AS state_after_counterexample,
       lesson.revised_lesson AS revised_lesson,
       lesson.remaining_check AS remaining_read_only_check,
       lesson.review_basis AS review_basis,
       lesson.model_calls AS model_calls

Original hypothesis: An idle runner is dead.

State: contradicted

Reviewed lesson: An idle label is insufficient. Establish what writes the field, then inspect the per-entity artifact before explaining the state.

The excerpts are real. The concise hypothesis and revised lesson are an authored demonstration fixture. No model produced them.

Graph agent → coding agent

Prior research changes the first check.

The retrospective is relevant, but it does not prove that the current idle runner is dead. A material counterexample contradicts that blanket claim, and a separate same-symptom incident remains unresolved.

Safe next check: Locate the current field writer and inspect one current per-run artifact.

This establishes no current mitigation, merged repair, verified deployment or current disposition. Refresh the writer and per-entity evidence before planning a change.

Evidence receipt

Public source label
throughput-agent retrospective
Source content SHA-256
33a915f0165fe5a77763e01de9b67a1280c0ec117427dded74293afd03161c31
Reviewed capture
3e7d6d718d3660a323432efa6eddab67ff0100828028a7b05f85e732b3492ab7
Observed
2026-09-09T06:40:42.226587Z
Protected query receipt
3a221b07a4a52587935f57c441f548066a75be20e0de99d2c2691fbc15d0cda2
Invalidation receipt
2321406a8ee6be0f4b73588f9d873be2441d4f03288cfc5b8f6a56773d9451b3
Gallery revision
cec4fc7fae81a642debb23538a7acb3ecdf92e73
Remote model calls
0