There is no shortage of books arguing that the information environment is broken. This column is written on the working assumption of one specific book, Flooding the Space, out from Prometheus Books / Globe Pequot in November: that the breakage is engineered rather than incidental, and that the engineering has variables you can name. The book does the naming. The column does the showing: a case a week, twenty-four weeks, sourced at the foot. Before the case files start arriving in earnest, the method deserves a note of its own.
Scope. A finite series. Twenty-four posts, on Tuesdays, running out to the book’s publication. Every post carries its format at the top (Field Note, Source Reading, Margin Note, Case File, or Correspondence) and its number in the series at the bottom. Nothing is padded to length or stretched to a schedule beyond the twenty-four. When the last one posts, the column ends.
What each post owes the reader. A dated byline, a specific claim or reading, and a Sources block at the foot with the primary material named: author, title, publisher, year, and, where the source lives online, a link. Where a piece leans on a secondary reading of a primary document, both are cited. Where a claim comes from a book chapter rather than an article, the chapter is named. The rule for keeping a source in that block is simple: it stays if removing it would have changed a claim in the piece above.
The shape of the column. Case files here are chosen for demonstrative value rather than recency, which rules out running commentary on the day’s news and the hot-take register generally. Nor are these chapter extracts. The posts stand on their own reading, and none of them previews the book in the sneak-peek sense.
The framework, in one line. The book proposes that the effect a flooded information environment has on a public can be read against seven variables: five that describe the pressure (Volume, Frequency, Emotion, Contradiction, Amplification) and two that act as brakes (Time, meaning the exposure window, and Rational Deliberation). Their compact form is (V·F·E·C·A) / (T·R), the FTSeffect. The equation is shorthand for a reading practice. It earns its keep only if it lets you look at a live situation and say which lever is being pulled. Chapter 10 introduces the Entropy Engine, which the column will return to.
The code. The book’s reference code is published on this site as two chapter snippets, the Digital Notary (Code Snippet 10.1) and the Circuit Breaker (Code Snippet 10.2). The Notary checks a file’s C2PA manifest and returns one of four statuses: VERIFIED, WARNING, TAMPERED, or UNSIGNED. The Circuit Breaker is the Entropy Engine in code. It scores a stream of social signals on four inputs: how fast they spread, how close their sentiment runs to rage, what share lacks C2PA credentials, and how much of the text repeats near-identical wording. It squashes the total to a score between zero and one, and above 0.90 it trips a circuit breaker that throttles algorithmic boost until verification can catch up. Its weights are defaults written into the code, such as the 1.5 penalty that treats unsigned content as 50 percent more chaotic than signed content of equal reach. When a later note uses one of those numbers, it treats the number as a design choice in a reference implementation and says so.
Corrections. If a claim in a future Note turns out to be wrong, the correction will appear here, dated and signed, with the original text preserved above it. That is the deal, and it applies retroactively to anything already posted.
Next week: V is for Volume: Brasília, January 8. The storming of the Praça dos Três Poderes as the cleanest single-event demonstration of the first variable in the equation.
— J.W.B.
Note 06 of 24