- What Mira remembers about a talent's boundaries was measured against real conversations, and a fifth of it was wrong. When a talent tells Mira something that should hold for every future job (nothing under five hundred dollars, no more logo work, not before the fifteenth), she saves it, and a person approves it before it filters anybody. Two hundred and fifty six real conversations that produced one of these were exported and a hundred and ten of them read by hand against the words they came from. Twenty one were a wrong reading, and twelve of those twenty one had been approved, because the approval screen shows the saved row and not the sentence behind it. Every one of those mistakes is now a rule in the instructions that do the saving: the unit next to a number decides what kind of number it is, a price per video is the boundary and never a total worked out from it, a condition stays attached to the rule it came with, a month is not a date, a morning and an afternoon are two windows and not one long one, and a figure counts only if the talent wrote it, never because Mira's own reply repeated it back. Replayed on forty one conversations, seventeen of the twenty one wrong readings came out right and all twenty right ones stayed right.
- Clearing a boundary is now something said out loud, and saving nothing is refused. A talent lifting their minimum and Mira firing the save on some chatter about availability and finding nothing used to produce exactly the same empty record, and both landed on the approval queue as a blank card. Twenty nine of those were in production, one of them approved and live, enforcing nothing. A save now names what it erased, a record that neither sets nor erases anything is turned away, and both are counted so the rate can be watched. The instructions that do the saving also moved to where every other instruction of that kind already lives, so an operator can finally read them, draft a change and compare before and after, instead of them sitting buried inside the code where no screen could show them.
- Taking back one rule deleted all of them. A talent lifted an eight hundred dollar monthly minimum. Mira answered, correctly, that she was removing it and keeping their preference for residential work. The saved record came out with no rules at all, because the only way to take anything back emptied the whole list. Promising a talent one thing and storing another is the serious half. Rules now come off one line at a time, the same way they go on, copied back exactly as saved; a removal that matches nothing is dropped and counted rather than guessed at, because deleting a boundary nobody named is the very failure this exists to prevent. Everything still clears at once when a talent says to clear everything. On the same conversation, one per video price had been filed under two different categories, because the reminder Mira reads showed the category as a bare number she could not recognise as her own. It now shows the name.
- A talent who said ninety euros an hour was nearly talked into a thirteen percent pay cut in her own words. The euros were converted once, stored as a hundred and four dollars, and then stopped existing. Three messages later she mentioned something unrelated, the save re-read the whole conversation, saw her "ninety" next to a stored "a hundred and four" and nothing saying one was the other, saved it again as a plain ninety, and the safety question that exists to stop a boundary being overwritten quietly asked her to approve her rate going from a hundred and four to ninety. That question is meant to protect her; here it would have been how she agreed to earn less. The currency a figure was named in is now kept beside it, the reminder reads "an hourly floor of $104, which is the 90 EUR they named", and a figure already listed there counts as saved even when the number looks different. Earlier the same evening a single currency for the whole save had turned a dollar per video price into a euro one and inflated it; each figure now carries its own.
- The queue where those boundaries get approved stopped at a hundred, silently. Everything past the hundredth row was unreachable, the show more control was never told there was more, and the counter said "100 waiting" for a backlog of four hundred. On a queue that decides whether a talent's own rule is enforced, that is not cosmetic. It now pages properly, the count is taken on the server, and a fix to the shared table control (it snapped back to the first page the moment a new page arrived) quietly repairs every other paged table on the employee console too.
- A visitor already signed in to Fiverr is now signed in to Mira without doing anything. Mira lives under the same web address family as Fiverr, so a visitor who is signed in there arrives carrying a sign that they are. Mira never reads what is in it, only that it is present, and answers by asking Fiverr quietly whether this person is known; if not, they simply stay the guest they were, and nobody is ever shown a login form they did not ask for. The careful part is signing out: that Fiverr sign survives our sign out, so without a guard this would sign somebody straight back in and make leaving impossible. Signing out now leaves a lasting marker that stops it, signing in again removes it, and a quiet attempt that fails cannot loop.
- One operator opening the experiment board set off three production alarms. The board drew a control per experiment and each one fetched its own setting, so a single page load fired ninety five requests in under three seconds, the admin service refused nineteen of them outright, and a second copy started up, served one request and then sat idle for sixteen minutes, which is what the alarms were about. Nothing was slow; each request took seventy two milliseconds. The board now uses the one snapshot it already had, fetching a control's live value only where someone is actually looking at it or moving it, so ninety six requests became one. And the admin service was sized to turn work away while doing none: it now queues the extra requests on its existing database connections instead of refusing them.
- The experiment read outs stopped leaning on the main database, and stopped asking the same question ninety seven times. Measured in production the day before, the safety check behind every experiment was the single biggest thing the application asked of the main database, more than half of all its time, while the read only copy built for exactly this sat nearly idle. It moved to the copy in the morning, and by lunchtime the whole register was being answered in three questions instead of one per experiment, with each experiment's list of issues limited separately so a noisy one can no longer crowd out the rest.
- Some turns had been quietly missing from every experiment. Since a change last week, the part of the worker that runs a client's turn does it in a separate lane so it can be cancelled, and that lane received a copy of the turn's experiment notes rather than the original. The notes were written into the copy and the record at the end read the empty original, so the turn was never recorded as part of any experiment. No error and no warning: a missing record reads as "this project was never in the experiment", which shrinks the count instead of emptying it and makes every rate a little too low without looking wrong. The turn now runs with notes the worker hands it itself. Three experiment alarms that looked as if they had failed to install were reinstalled with the explanation attached: they had installed fine and only became visible to the monitoring service fifty minutes later, and the obvious fix, trying again, would have deleted them.
- And the rest is words and a plan. The headhunting screen now speaks of talent, shortlists and candidates, and its top button says what it opens, the job description. The talent's own note on the client's waiting screen was taken out and put straight back, laid out differently so it can be carried onto the pre-release environment on its own without dragging anything else along. And a plan was written for asking Mira questions about the business data in plain words, cut down so the model describes a chart rather than writing its own database query, which lets every safety layer that already exists do the work.
A Wednesday of 19 commits, and most of the day was about the gap between what a talent said and what Mira wrote down. A hundred and ten saved boundaries read against the sentences behind them, a fifth of them wrong and most of those already approved. An empty save that looked exactly like a deliberate clear. Taking back one rule deleting every rule. Ninety euros stored as dollars and then offered back as a cut. Each fix moves the record closer to the talent's own words. Around it: a board whose single page load fired ninety five requests and three alarms, turns missing from every experiment without a single error, and Fiverr visitors signed in without being asked, with signing out still a real way out.