# Bad Barrel

> A systems-thinking check for one recurring snag in a shared setup - an office floor, a club, a studio, a flat share. Describe the snag, where it happens, how many people share the setup and whether it traces back to one person, then mark eight staves of the setup as sound, weak or not sure. The page draws a barrel with cracked, leaking staves and gives its own verdict and lever by a fixed rule; one metered run explains the staves in the setup's own terms and suggests one change.

URL: https://bad-barrel.skillsafe.ai/
API: https://bad-barrel.skillsafe.ai/api.html

## What it does
- Free, in the browser: the barrel drawing (SVG and PNG downloads), the counts, the page's own verdict and the stave to pry at first.
- The eight staves, in fixed order: owner (it is clear whose job this is), rule (everyone knows what is expected), easy (doing it right takes no more effort than skipping it), means (what is needed is right there), seen (when it is left undone, someone notices soon), fair (the work is shared fairly), time (it does not fall when people are rushed), cost (nobody loses out by doing it).
- Verdict, first match wins: barrel (3 or more weak staves, or 1-2 weak staves with no single person behind the snag); both (1-2 weak staves and one person behind it); apple (no weak stave, at most one not sure, one person behind it); look-closer (anything else).
- Lever: the first weak stave in the fixed order; if none is weak, the first not-sure one; if every stave is sound, none.
- Metered task `sort` (gpt-terra): a note for each weak or unsure stave, a feedback loop and one setup change for barrel and both, one kind private ask for both and apple, one fact to find out first for look-closer. The page re-checks the verdict, the lever, all 8 stave states and which sections belong to the verdict. Safety hazards and conduct problems (harassment, threats, theft and similar) are declined.

## Input (task `sort`)
All strings: task, snag, setting, people (a whole number or "not given"), traces_to_one (yes, no or not sure), staves (eight numbered lines: id | statement | sound, weak or not sure), notes (or "none"), optional retry_note.

## Reply
One JSON object: task, status (ok or declined), reason, verdict, lever, staves[{id, state, note}], loop, tweak, ask, find_out, closing.

## Sources
- Built on the SkillSafe skill @tjboudreaux/thinking-systems: https://skillsafe.ai/skill/@tjboudreaux/thinking-systems

## Notes
A light thinking tool for everyday snags - not HR, legal or professional advice. Suggestions change the setup, never single out or punish a person.