Personalization on AIBussin — AI applications, systems and books

The Personal Experience

Thu, 01 Oct 2026 09:00:00 +0100

A few weeks into using the Radar, Priya notices that it behaves differently from the first day. Library updates no longer interrupt her. Papers arrive with the conclusion first and the method behind a click. Comparisons come as tables. Contradictions of her protocol arrive with the evidence attached, never as a bare verdict. None of this surprises her entirely, and most of it she likes. (Priya and the sessions in this part are constructed for illustration, as in the last part. Where research is cited it is attributed, and nothing here reports a measurement of the book’s own.) But when she asks why a particular item was shown the way it was, the answer is not clear. Some of it she told the system. Some of it she did, and the system noticed. And some of it the system concluded for itself, from the way she had behaved, in ways she cannot now reconstruct.

There Is No Universal Best Interface

Thu, 01 Oct 2026 09:00:00 +0100

The previous chapter ended with a temptation. Priya’s behaviour is leaving traces. She opens tables more often than prose, expands the mathematical detail, ignores diagrams. A system that remembers could draw the obvious conclusion: this person is a certain kind of reader. Diagram people get diagrams, detail people get detail, and the interface learns her type and stops asking.

This chapter takes that shortcut apart. It does not do so by saying that people are all the same, which they plainly are not. The target is exact:

From Observation to Policy

Thu, 01 Oct 2026 09:00:00 +0100

Memory can be right and still make the present wrong

In March, Priya tells the system something important about a payments service.

The old replication path is gone. Writes now go through a new quorum path. She is explicit because the distinction matters to an incident review they are doing that afternoon.

The system remembers it.

Three months later, the service changes again. The quorum path is replaced during a larger architecture migration. The March statement remains perfectly good evidence about March. Priya really said it. At the time, it was correct.

The Person Changes During the Day

Thu, 01 Oct 2026 09:00:00 +0100

Priya opens the system on her phone before an architecture review and says: I have five minutes before the meeting. Just tell me what can break.

Her standing policy asks for implementation detail and equations when they affect the decision. Yesterday, at her desk, that meant a full account of the recovery path. Today the same account would consume the time she has before the meeting. But a short answer that hides the decisive qualification would also fail her.

Sometimes the Best Interface Adds Friction

Thu, 01 Oct 2026 09:00:00 +0100

At the start of an evening study session, Priya says: For this session, I want to finish this paper first. Remind me before I open another one. Twenty minutes later, a new result arrives through her semantic subscription. She reaches to open it.

The channel shows a line beside the action: You asked for a reminder before opening another paper. She can continue with the paper in front of her or open the new result immediately. The reminder makes the choice visible without taking it away.

Protection That Travels

Thu, 01 Oct 2026 09:00:00 +0100

Priya has asked her reading tool to remind her before she opens another paper. She has separately asked it to keep unrelated recommendations out of the reading view during the study session. Neither instruction governs her news or video services. When she moves to one of those, the recommendations return.

She now gives another instruction: For this evening’s study, keep new consensus-research recommendations out of the recommendation feeds in these two services. Leave search and direct opening available. End the rule when I finish the paper or end study, and by eight this evening in any case. She selects the services and accepts the scope.

What the System Believes About You Must Be Visible

Thu, 01 Oct 2026 09:00:00 +0100

Priya opens a talk about a consensus algorithm she has not used. The channel shows the algorithm’s steps and a diagram. An introductory section is folded away. When she asks why, it answers: Consensus foundations treated as already known, inferred from earlier architecture reviews.

Priya knows the field. But the folded section states which failures this particular algorithm assumes. Familiarity with consensus does not establish that she knows this talk’s assumptions, and even knowing them would not make their role in the argument dispensable. The inference has changed the communication at the point where its scope mattered most.

The Personal AI

Thu, 01 Oct 2026 09:00:00 +0100

At twenty past nine, Priya begins an architecture review. The channel has a standing policy she declared, observations from earlier reviews, an inference about derivations, and the means to apply temporary instructions and carry boundaries to selected services. It could use all of them.

Priya says: I have ten minutes. In this review view, show material that bears on the decision. Keep the decisive equations and assumptions visible; fold the supporting steps, with the full calculation available.