Information Retrieval on AIBussin — AI applications, systems and books

Too Much Information

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

Return to the incident manager from the last chapter, now with a Semantic Browser that works. She opens the report on Tuesday’s outage, and the system has found a good deal more than the report. There are forty earlier incidents that look similar. There is service telemetry for the hour in question. There is documentation for three dependencies, and a runbook that has not been updated since the migration. The record has turned up three possible contradictions between the report and other sources. The system has drafted seven diagrams of the causal story, each from a slightly different angle. There are fourteen relevant excerpts from the team’s chat, the change history for the week, and a handful of external write-ups of the same failure mode.

A Video Is Not an Hour

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

A person has one hour of video and ten minutes to decide whether it contains the answer she needs. (She, her colleagues and the talk are invented for this book, as are the examples that follow in this part.) It is a conference talk about a new consensus protocol, recorded last spring. She cannot watch it. She could scrub through, catching a few seconds here and there, or read the auto-generated transcript, fourteen thousand words of speech. The honest options the interface gives her are two: watch, or don’t. That is too coarse. The question she has is not “is this video worth an hour?” but “does it say whether this protocol survives the kind of failure we have?”

Important to Whom?

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

The talk on the consensus protocol has been broken into units, with the definition at minute 4 and the qualification at minute 53 joined where they belong. Three colleagues now ask the same system about it, each for a different reason. Priya has to decide whether the protocol is safe when network delays are unbounded. Tom is writing the history of consensus algorithms for a literature review. Mina wants to reproduce the demonstration.

Don't Tell Me What I Already Know

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

Priya asks about the consensus protocol, and the system knows something about her. She has worked on consensus systems for two years. She has given talks on the subject. So when it prepares her digest it leaves out the speaker’s definition of partial synchrony as something she plainly knows, and shows her the parts that look new. It is a considerate thing to do. It is also a mistake, because the speaker uses the term in a narrower sense than the one Priya works with. Her usual definition allows delays whose bound is unknown. In this talk the bound is known to the protocol, and everything the speaker later says about safety rests on that. Priya reads the digest, meets the claim about bounded delays, and concludes the talk contradicts what she knows. The system had removed the one piece of information she needed in order to read the rest.

From Channels to Semantic Channels

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

Priya follows fourteen conferences, nine labs, thirty authors and four preprint feeds on distributed consensus. In March, a result appears that undermines the assumption her team’s design rests on, the one about bounded network delay. It is in none of her feeds. It is a paper on distributed databases, from authors she has never heard of, and it never uses the word “consensus”. It shows a mechanism that works without the delay bound she has been treating as essential. She finds it in June, by accident, cited in a thread about something else. Three months of work stood on the old assumption.

Compression Has Levels

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

At three in the morning Priya’s semantic subscription fires. A new paper from a database group has appeared, and the system judges that it qualifies: it may weaken the assumption her protocol’s safety result rests on. The item is relevant to her purpose, new to her, and matches a relation she asked to be told about. All of that has been settled. What has not is how much of it she should see first.

When Should the AI Speak?

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

At 14:40 a candidate arrives: a new paper that may contradict an assumption in the code Priya has open in her editor. The system’s account of it is solid. The match is plausible, the evidence is attached, a brief is the right resolution, and the item is new to her. It also knows something else. She is presenting in a design review until 15:30, and the deployment the paper might affect is not until 18:00.

The Personal Information Radar

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

Priya’s afternoon, as seen from inside the system, begins at 14:40. She is in a design review that runs until 15:30. The Radar, which is what this chapter will call the system that has been assembled over the last seven chapters, the same layer as before now attending to a stream and not a single document, has four candidates waiting to reach her.

A  a new paper that possibly weakens the bounded-delay assumption
B  a major update to a library she uses often
C  an interesting new survey of consensus protocols, mostly material she knows
D  an incident report affecting tonight's deployment

Part I ended with a Semantic Browser, a renderer that treats a source as something to interpret and present. This chapter is the equivalent for attention. It asks: what does the whole attention architecture look like when information is continuously competing to reach one person? The metaphor is chosen with care. A radar watches continuously, signals enter and leave range, some are uncertain, they differ in significance, and not everything becomes an alarm. What the metaphor must not become is surveillance, and the chapter will say what prevents that.