Notes from the Saytu team

What we learn building a Live2D character that answers preorder, sizing and authenticity questions on anime storefronts.

What verified means when a source is switched off

A control that appears to work and does not is worse than one that visibly fails. Why retrieval reads the switch rather than the rows, and why the inspector is the same code path.

Build logSeptember 21, 20264 min read

Four records, and what the assistant is actually shown

Everything a store has written, narrowed to about two thousand characters for one question. The budget, the two ranking lanes, and the floor below which nothing counts.

Build logSeptember 21, 20264 min read

108 unread

We published 108 articles nobody read

They were written by a model, posted through our own API, and made public on arrival. One of them had no text in it. Here is the count, and what we changed.

Build logSeptember 21, 20264 min read

Draft vs live

A draft should never take the live answer down

Asking for a draft of an FAQ entry quietly unpublished the one the store was already giving. A write that sets a status is a visibility change.

Build logSeptember 21, 20264 min read

When every score ties, the ranking is a coin flip

Keyword scores tie constantly, and a tie handed the order to whatever the database returned. The fix is deliberately not an improvement.

Build logSeptember 21, 20263 min read

One store's reply

A turn id is whatever the client says it is

A retry handed one store the reply written for another. The key was a string the browser chose, used across a collection that spans every tenant.

Build logSeptember 21, 20264 min read