Catalog

This is not the latest version.

Viewing v1.0, published August 17, 2026.

Go to Latest Version

JuliusBrussee

investigate-first v1.0

as of v1.0latest is B

Diagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing evidence-ranked hypotheses.

NewPublished August 17, 2026all versions

Byte-exact. Everything on this page is exactly what v1.0 published, including every file.

What changedInitial version — nothing to compare.

Investigate first

Gather evidence before changing product code.

  • Separate observed symptom from inferred cause.
  • Trace inputs, state transitions, ownership boundaries, and failure output.
  • Rank hypotheses by evidence and cheap falsification value.
  • Do not edit until one credible mechanism explains evidence.
  • Stop exploration when evidence is sufficient to name cause or exact blocker.

Report cause and proof. Make no fix unless task authorizes implementation.

Command Palette

Search for a command to run...