feat(threads): a thread title says what the thread is for #492

Merged

coilyco-ops merged 1 commit from feat/a-thread-title-says-what-it-is-for into main

2026-08-13 14:45:06 +00:00

coilyco-ops commented

2026-08-13 14:27:31 +00:00

Member

closes #461

Kai reversed the earlier decision not to summarise. How much does it cost to build a log house becomes something like log house pricing, rather than the member's sentence with punctuation stripped.

I wrote the sentence being overruled — "Dropped, not summarised. Summarising would be writing a member a title." It was a defensible call, and it is not mine to keep once the person it was protecting says otherwise.

The cost, stated rather than hidden

A summary needs the model, so this is one short extra completion. Proportionate rather than free: a thread only happens on a turn that already ran past the long-reply window, so it lands on the expensive minority by construction rather than on every turn.

It degrades rather than fails

A title call that errors, times out, or returns nothing usable leaves the thread created with the derived name it has today. A feature that could cost a member their thread over its title would be a bad trade, and the fallback is the path already in production.

The summary is cleaned like a name

Same letters-digits-spaces treatment, so a summary cannot introduce markup a member's own message could not. A test feeds it **log house** <@123> pricing! and checks none of it survives — worth having given that two defects today came from exactly this class of thing reaching a reply.

ward exec gate green: build, policy-check, vet, test, test-skips, pre-commit.

closes #461 Kai reversed the earlier decision not to summarise. *How much does it cost to build a log house* becomes something like *log house pricing*, rather than the member's sentence with punctuation stripped. **I wrote the sentence being overruled** — *"Dropped, not summarised. Summarising would be writing a member a title."* It was a defensible call, and it is not mine to keep once the person it was protecting says otherwise. ## The cost, stated rather than hidden A summary needs the model, so this is one short extra completion. **Proportionate rather than free:** a thread only happens on a turn that already ran past the long-reply window, so it lands on the expensive minority by construction rather than on every turn. ## It degrades rather than fails A title call that errors, times out, or returns nothing usable leaves the thread created with **the derived name it has today**. A feature that could cost a member their thread over its title would be a bad trade, and the fallback is the path already in production. ## The summary is cleaned like a name Same letters-digits-spaces treatment, so a summary cannot introduce markup a member's own message could not. A test feeds it `**log house** <@123> pricing!` and checks none of it survives — worth having given that two defects today came from exactly this class of thing reaching a reply. `ward exec gate` green: build, policy-check, vet, test, test-skips, pre-commit.

coilyco-ops added 1 commit

2026-08-13 14:27:32 +00:00

feat(threads): a thread title says what the thread is for

ci / image-build (pull_request) Successful in 30s

Details

ci / test (pull_request) Successful in 35s

Details

ci / publish-echo-image (pull_request) Has been skipped

Details

ci / publish-observed (pull_request) Has been skipped

Details

d408073d5d

Kai reversed the earlier decision not to summarise. A thread asking how much a
log house costs should be called something like log house pricing, not the
member's sentence with the punctuation removed.

I wrote the sentence being overruled: dropped, not summarised, because
summarising would be writing a member a title. That was a defensible call and
it is not mine to keep once the person it was protecting says otherwise.

A summary needs the model, so this is one short extra completion. It is
proportionate rather than free: a thread only happens on a turn that already
ran past the long-reply window, so it lands on the expensive minority by
construction rather than on every turn.

It degrades rather than fails. A title call that errors, times out, or returns
nothing usable leaves the thread created with the derived name it has today. A
feature that could cost a member their thread over its title would be a bad
trade, and the fallback path is the one already in production.

The summary takes the same cleaning a derived name takes, so it cannot
introduce markup a member's own message could not, which a test holds.

closes #461

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops requested review from coilysiren

2026-08-13 14:27:32 +00:00

coilyco-ops merged commit 56f4bffaad into main

2026-08-13 14:45:06 +00:00

coilyco-ops referenced this pull request from a commit

2026-08-13 14:45:08 +00:00

Merge pull request 'feat(threads): a thread title says what the thread is for' (#492) from feat/a-thread-title-says-what-it-is-for into main