> open /techniques/fishbone --case=002
CASE #002 // THE MYSTERIOUS MUDDY POOL

FishboneMap the suspects.

When a problem could have many causes, don't chase the first theory. Ishikawa / Fishbone helps a group organize possibilities, see gaps, and decide what evidence to investigate.

PURPOSEPOSSIBLE CAUSES
DIFFICULTYEASY
TIME30–60 MIN
BEST FORMULTI-CAUSE PROBLEMS
STATUS: TOO MANY SUSPECTS
EFFECT_

Capybara's clear pool has turned muddy. 🟫💧

There is no obvious single cause. So instead of chasing one theory, we build a map of everything that could plausibly create the effect.

ISHIKAWA WORKSPACE / CASE #002HYPOTHESES ≠ EVIDENCE
← SWIPE THE WHOLE FISH →
Fishbone diagram of possible causes of Capybara's muddy poolSix cause families branch into the muddy pool effect. Maintenance and equipment are highlighted by evidence. START WIDE 🌧 WEATHERheavy rain[NO]runoff[NO] 🌱 VEGETATIONbank erosion[NO]dead plants[NO] 🐦 ANIMALSdigging[NO]unusual activity[NO] 🧹 MAINTENANCEcleaning missed [!!!]schedule gap ⚙ EQUIPMENTfilter clogged [!!!]low flow [!!!] 🚰 WATERsediment supply[NO]source change[NO] 🟫 MUDDYPOOLEFFECT CAPYBARA.EXESCANNING BRANCHES...
[NO] evidence weakens branch[!!!] evidence strengthens branch

Read it like a fish: the head is the effect. Big bones are cause families. Small bones are hypotheses. The skeleton forces us to search broadly before evidence narrows the investigation.

EVIDENCE PASS_
🌧️ Recent heavy rain?[NO]
🐦 Unusual animal activity?[NO]
⚙️ Filter flow normal?[NO → CHECK]
🧹 Cleaning completed?[MISSED]
CONTRIBUTING PATH FOUND_

The diagram told us where to look. Evidence told us what mattered.

MISSED MAINTENANCE→CLOGGED FILTER→LOW FLOW→MUDDY POOL
STATUS: WATER ACCEPTABLE AGAIN ☕
RESULT_

Clean the filter. Restore the maintenance control.

The other branches stay documented instead of being forgotten. Fishbone helped Capybara think broadly; testing narrowed the map to a supported causal path.

REAL WORLD TRANSLATION_

Muddy pool→Your effect/problem
Main bones→Cause categories
Small branches→Hypotheses
[NO] / [!!!]→Evidence

REMEMBER_

A Fishbone does not prove root cause. Its job is to stop tunnel vision: organize plausible causes, expose gaps, then investigate the branches with data and observation.

> run /tools/fishbone --interactive

TRY IT YOURSELF_

Put your own effect at the fish's head, map possible causes across six editable families, then mark each hypothesis as evidence weakens or strengthens it.

LOCAL WORKSPACE
saved on this device
FISHBONE WORKSPACE / YOUR CASE MAP → TEST → NARROW
LOCAL SAVE ACTIVE_ Changes are auto-saved in this browser on this device.

CAPYBARA PRIVACY NOTE_ Keep passwords, API keys, access tokens and credentials out of the workspace. Private Session controls problem.me storage; it is not a secret vault. HOW PRIVACY WORKS →

observable, specific, neutral
CAUSE FAMILIES_ rename any category to fit your problem
AUTO-SAVE READY_
REASONING LAYER_

EVIDENCE LEDGER_

Separate what you know from what you think. Facts, assumptions, tests and results stay visible while the investigation evolves.

NO EVIDENCE LOGGED
LEDGER READY_
CAPYBARA.EXE: Claims are cheaper than evidence. Log what you actually know.