---
{
  "n": 14,
  "title": "A name for every feature, and the work it names",
  "abstract": "",
  "refs": [],
  "seen": [
    "agent"
  ],
  "data": {},
  "created": 1789937048.887677,
  "updated": 1789937074.69394,
  "deleted": 1789937074.693939,
  "completed": 0.0,
  "outcome": "",
  "type": "doc"
}
---
Thirty-three features audited against one test: a feature is a single piece of coherent work, and its name is that work. Eleven names are already right. Fourteen describe a mechanism, a moment or a sentence rather than the work. Eight are names for work that is not coherent — the feature does two things, which is why no single name fits.

## The test
A feature is a single piece of coherent work, and its name is that work. Two things follow from it. A name that describes the mechanism, the moment it fires, or the sentence it says is the wrong name — Handled messages close is a sentence, The context decision is a moment, Buttons on a message is a mechanism. And a feature that cannot be named in a few words without an 'and' is not one piece of work; the naming test finds the merges and the splits by itself, which is why this audit disagrees with the plan in three places.

## Already right
| Feature | Name | |
| --- | --- | --- |
| agents | Subagents | the work is running and minding them |
| housekeeping | Housekeeping | says exactly what it is |
| pins | Pins | the thing it keeps |
| plugins | Plugins | the thing it runs |
| questions | Questions | the work is asking and answering |
| reminders | Reminders | the thing it repeats |
| retention | Retention | the work is keeping and letting go |
| rules | Rules | the thing it enforces |
| sessions | Sessions | the thing it minds |
| style | Coding style | the thing it holds you to |
| work | Work — better as Working | the work is declaring, logging, parking |

## Wrong name, one piece of work
These do one coherent thing and are named for something else — the mechanism, the moment, or the sentence they say.

| Feature | Now | Should be | Why |
| --- | --- | --- | --- |
| inbox | The inbox | Messaging | your word, and the right one: the work is messaging, not the box it sits in |
| handled | Handled messages close | Messaging | a sentence, not a name; it is the same work as the inbox |
| status | A message is answered before the next write | Messaging | a whole sentence as a name; also the same work |
| buttons | Buttons on a message | Messaging | names the widget, not the work |
| tags | Tags | Tagging | the work is tagging what the agent writes |
| attachments | Attachment tags | Attachments | names the mark it leaves, not the work of reading a file |
| video | Video frames | Attachments | names the mechanism; it is how attachments reads one kind of file |
| auto | Auto mode | Working | mode is a machine word; the work is picking up the next row |
| commits | Commits | The to-do list | names the input, not the work: closing a row from a commit |
| deferral | Deferral | The to-do list | names the failing, not the work: catching work put off in words |
| choices | Choices asked properly | Questions | a judgement in the name; the work is asking properly |
| context | The context decision | Memory | names the moment it fires, not the work of deciding what to keep |
| statusline | What the status bar shows | The status bar | a clause, not a name |
| usage | Provider plan usage | The status bar | names one number on the bar |
| skills | The journal skill loaded | Skills | a sentence about a state |
| start | The start block | The start block | right, if a little literal |
| tabfocus | One viewer tab | The viewer tab | close enough; drop the one |
| law | The law, no wigs required | The law | the joke is in the abstract's gift, not the name's |
| suggestions | Suggestions decided | Suggestions | the participle adds nothing |
| plans | Plans | Planning | the work is drafting and advancing them |

## No name fits, because the work is two
Four features cannot be named without an 'and', which is the test telling you they are not one piece of work.

became — links a row to the message in hand, and nudges when a plan cites no source. The first is messaging. The second is provenance and belongs with planning. Two features wearing one name.

cleanup — the reading pass over rules and pins, and an audit of the record's integrity. Already split by question 31: the pass into Memory, the audit keeping its own name.

sessions — eviction, which holds the agent's writes, and the quiet sweep. Both go to Subagents by question 31, which leaves Sessions as a name with nothing under it.

start — what a session is handed, which is one thing, but it is handed by reading every other feature's rows. It is a view over the record rather than work of its own. Leave it; just note that it is the one feature whose job is to render others.

## The names, after everything
Messaging. Memory. The to-do list. Working. Planning. Questions. Attachments. Housekeeping. Retention. Subagents. Skills. Plugins. The law. Coding style. Suggestions. The status bar. The start block. The viewer tab. The record audit. Tagging.

Twenty names for what are now thirty-three features. Three disagreements with the plan as it stands, all from the naming test rather than from a count.

Tagging survives as its own feature. Question 30 said to scatter tags, choices and deferral, and this audit agrees for choices and deferral — asking properly is questions' work, catching deferred work is the to-do list's. But tagging is not messaging: it is about what the agent writes anywhere, and it is the feature that would own the tag grammar in to-do 383. It keeps its name.

Retention stays out of housekeeping. Both run on a clock, but one deletes the user's own rows and the other trims log files nobody reads. Same cadence, opposite consequence.

Attachments takes video, which the plan already says, and the name changes from Attachment tags to Attachments, because the work is reading a file rather than marking it.