Champignon

contribute · a weight

A weight that looks wrong

Every weight in the library is visible, which is the only honest way to invite an argument about one. Here is the form of argument that can change a number.

Bring a comparison, not a feeling

This is the one thing that makes the difference between a submission that changes a number and one that can only be filed.

Each task was scored against anchors and ranked within its category, not judged in isolation — because a number assigned in isolation has nothing holding it in place. So the useful shape is:

This task sits above that task, and it shouldn't — because …

or

These two are scored the same and they are nothing alike — because …

This feels too low has no handle on it. There is no way to act on it that doesn't amount to nudging a number until it stops generating complaints, which is how you end up with a library that is internally inconsistent in a way nobody can see.

The three dimensions, since this is usually where the disagreement is

Most weight disputes turn out to be a disagreement about what vigilance means.

And minutes are marginal: the time a row costs that its neighbouring rows don't already claim. Scored as standalone durations, six kitchen rows came to 56 minutes a day and six bedtime rows to 94 — individually defensible, collectively describing a week nobody lives. If a row's minutes look low, check what its neighbours already account for.

The form is not built yet

Same as the other routes: this site is ahead of the app, and the form gets wired up with the first release. The support page reaches the same person in the meantime, and a well-argued comparison is worth sending now — the library is still open.

What happens to it

If it changes a weight, the change appears in the changelog with its reasoning. If it doesn't, it is usually because a comparison pulled the other way — and where it was close, that gets said. The governance is on the contribute page: weights are not voted on.