Our own instance holds a few hundred Tasks, Goals, Decisions and Amendments. When we measured on 15 October, Tasks and Goals had no title at all, so every list showed the first line of the body instead: a median of 245 characters, the longest 1,376. Five Decisions had an empty title. One field had twelve spellings of eight meanings, and another had seven spellings of four roles. A list you cannot scan and a field you cannot filter make every reader slower, people and agents alike.
Core v1.155.0 gives every record that needs one a title (D112). It is one line of at most 120 characters. An Amendment's summary is its title. Signals and plans have none.
The rule starts as a warning. A create or update without a title, or with a longer one, still succeeds and returns a warning next to the record. Only when the instance's operator sets a cut-over date does the same write become a refusal, with a message that says what to send. Older untitled records still take every other change.
The Amendment type is now a closed list of eight values, and the retired role field is gone because the band and the actor already say who did the work. "Done" and "resolved" mean one thing each. Done means the work was carried out. Resolved means it closed without being carried out, because it was superseded, declined or found already built, and it needs a reason. The meanings are written in the flow definitions, not only in our heads.
An existing untitled record gets a title from the first line of its text, cut at a word boundary. The migration runs as a dry run by default and reports every change by address. On our instance, 195 of 208 Amendment summaries were longer than 120 characters. The migration shortens them and keeps the full text as the first paragraph of the body, so nothing is lost. It does not guess. A value that is a size rather than a type is listed for a person to map.
Released in core v1.155.0 and mcp v1.61.4, with the strict cut-over in v1.157.0.