Compact Debug Ledger

Goal

Compress an investigation into a structure that preserves debugging momentum rather than generic conversation history.

Workflow

1. Extract the debugging target.
2. Record the strongest evidence collected so far.
3. Record each attempted line of inquiry and its result:
   • worked
   • failed
   • inconclusive
4. Separate disproved hypotheses from still-viable hypotheses.
5. List the next 1-3 experiments that would most reduce uncertainty.
6. If the platform has a built-in compact or summarize command, use it with this exact structure when possible. Otherwise produce the compacted note inline.

Output Format

Debug Target

<one sentence>

Evidence

• <fact>

Attempts

• <attempt>: worked/failed/inconclusive

Ruled Out

• <hypothesis>

Still Plausible

• <hypothesis>

Next Experiments

• <experiment>

Rules

• Every Attempts line must end with exactly one of worked, failed, or inconclusive.
• Do not use alternate labels like ruled out, confirmed, fixed, or partial in the Attempts section.
• Do not preserve dead conversation detail that does not affect the investigation state.
• Prefer evidence and hypotheses over chronology.
• Keep only enough implementation detail to support the next experiment.