Every Little Thing
Glossary

Every word this product made up.

A heart, a receipt, a transition week. Words a product invented are words nobody can look up, so here they are.

Ordered the way you meet them rather than alphabetically: the loop first, then the numbers, then the settings, then the two modes a couple can be in.

Contribution

One thing one partner did for the two of them, logged in a single tap. It stays pending until the other person confirms it.

Confirmation is not a formality — it is what makes the record two-sided. Nothing counts because one person said so.

Heart

The unit. A contribution is worth some number of hearts, and a week has a total.

A word and never a glyph, and it counts what got done rather than how much anybody cares. The distance between those two sentences is the whole product.

Score receipt

The stored breakdown behind every contribution: each coefficient, what it was, and the running total.

It is what makes “every point is explainable” true rather than aspirational, and it is permanently free. A number you cannot open is a verdict.

Occurrence

Which time this week you logged this particular kind of thing. The fourth load of laundry is worth less than the first, and occurrence is how the formula knows which one it is.

Frozen when you log it. Withdrawing an earlier entry never renumbers the ones after it.

Weekly index

A partner's weekly score expressed against the couple's own target, on a 0–100 scale, and frozen onto the week it measures.

Against your own target, not against each other and not against other couples.

Balance

The gap between the two weekly scores, shown as one label for the couple rather than as a ranking.

There is no winner field in the data. Clients are not allowed to compute one, and the dashboard returns both partners in a fixed order so neither side of the screen is the better one.

Grounding note

The italic line on every screen that shows a number, reminding both of you what the number is not.

A product rule, not a decoration. If a screen has numbers on it, it has one of these.

Weekly review

The Sunday-ish ritual: a few questions each, answered separately, opened together.

Private until mutual — neither of you sees the other's answers until both have submitted. Private notes never cross at all.

Weekly inventory

Two optional questions at the front of the review: how many things you think your partner did, and how many you think you did. Answered blind, then laid next to the record.

Counts, never scores. The gap between what you guessed and what happened is the interesting part, and it usually runs the same direction for both people.

Most valued

What your partner picked out of last week's review as the thing that mattered most. It opens the dashboard.

Never your own pick, and never shown with a score attached.

Quiet mode

A couple setting that hides comparison and keeps explanation: no totals, no indexes, no balance — and every score receipt still opens.

Applied by the server, not the app, so it cannot be undone by a screen that forgot.

Life context

A named stretch — a newborn, a move, an illness, a crunch, a loss — during which the ordinary reading of a week is simply wrong.

It eases the target a week is read against. It changes no score, because weighting the formula would bake a judgement about whose effort counts more into the one mechanical part of the product.

Couple profile

One weight per category, drafted from your own counts and applied only once you have both agreed to it.

Either of you can decline it alone. It is clamped so it can never move a category further than a single step of effort moves a contribution, and there is no per-partner weight — there must never be one.

Connect code

Your permanent public identity, 26 characters, printable as a QR. It is how your partner finds you.

It identifies and it never authenticates. Every connection is approved by the person who owns the code, which is why it is safe on a QR.

Invitation

A secret, single-use, expiring link for the ordinary case where your partner does not have an account yet.

The opposite object to a connect code, and the difference is what makes it safe: you created it deliberately, for them, and you are emailed the moment it is used.

Change log

The record of every change either of you made to a shared setting.

Either partner can change a couple setting alone. This is what stops that being invisible.

Transition week

The short week — one to seven days — created when a couple moves their review day.

The price of never reshaping a week you are already standing in.

Solo mode

One person keeping the record for both, logging what they did and what they noticed their partner do, with the partner never opening the app.

It logs and it never scores. In a pair the person who receives something is the one who says what it was worth; with one reader that rating does not exist, and a number invented in its absence is one partner's opinion of the other, accumulating.

Band

The lowest and highest score a category's shipped actions use — the range a suggested score is clamped into.

Drawn from shipped actions only. If a couple's own generous suggestion widened the band, the guard rail would walk itself upward a week at a time.


The argument behind most of these is on the page about keeping score, and the three that changed the product most have pages of their own: the score receipt, quiet mode and life context.

Something here wrong, unclear, or missing? Tell us. You do not need an account.