Leverage AI

Publishing architecture · Attention · Canon

Attention-Native Publishing — The Article Compiled for an Interrupt

📖 This article has an expanded ebook edition — read the full ebook.

Under attention scarcity, the quote-sized idea becomes the primary public unit and long-form becomes the proof surface. The job is not to post more. It is to design a gate that compiles a canon into scarce, honest interruptions — and lets everything else go dark.

Scott Farrell · LeverageAI · Design essay companion to the Attention-Native Publishing ebook

In brief

Something odd happens when you take a finished ebook seriously enough to extract the lines that can travel on their own. You put those lines on cards. You ship them into the feed. And — if you have done the work — the cards can become more interesting to publish than the original book.

That is not a claim that short is always better. It is a claim about jobs. The ebook has several: establish the argument, explain the mechanism, handle objections, preserve nuance, provide evidence. The quote has one: spend a tiny amount of someone’s attention so well that they voluntarily spend more.

That constraint forces a different — and sometimes better — piece of thinking. It is the article recompiled for an interruption.

A quote card is not a fragment of an article. It is the article compiled for an interrupt.

The problem is not “nobody reads long-form”

People still read when the interruption earns the descent. What fails is the old carrier hierarchy: treat the long piece as the product and the short piece as a promotional scrap. In a world where drafting is cheap, that hierarchy floods the feed with complete arguments nobody asked to receive yet — and with hooks that cannot survive a double-click.

Human attention on the open web is brutal about first contact. Readers often leave pages in the first 10–20 seconds unless a clear value proposition lands quickly.1 That is not an argument for dumbing down. It is an argument for staging: the first unit must create useful unresolved tension without lying about what the full argument will later prove.

Meanwhile, the same scarcity language now appears on the machine side. Model builders talk about an “attention budget” for context: every additional token depletes a finite account; good engineering finds the smallest high-signal set that still produces the desired outcome.2 Readers are not transformers. But the economics rhyme. Both systems punish undifferentiated volume.

The reframe

You are not managing a content calendar. You are adjudicating petitions against someone else’s interrupt budget.

Attention event versus proof surface

The clean architectural move is to stop asking one artefact to do both jobs.

ArtefactPurpose
Ebook / long-formDurable worldview, evidence, qualifications, falsifiability
ArticlePublic, readable expression of the thesis
Quote cardAttention event
CaptionJust enough orientation to make the interrupt intelligible
LinkPermission to descend into greater resolution

A summary tries to save the reader from reading. A well-compiled quote tries to make the reader want to read. Those are opposite optimisation targets. The earnest TL;DR often loses because it resolves the tension. The card wins when it leaves a load-bearing edge intact: an inversion, a contradiction, an unexpected equivalence, a sentence that changes the reader’s representation of the problem.

This is productive incompleteness — the same family of idea as compression that reveals structure rather than merely discarding detail. The card may withhold explanation. It must not withhold truth.

The publishing analogue of silent-handle / interrupt / don’t-tell

If you have built agents that protect a human’s attention, you already know the doctrine. A state change is not an attention event. Something has to adjudicate whether it becomes one. The branches are roughly: silent-handle, interrupt, or don’t-tell.3

Map that onto publishing:

That is attention sovereignty applied outward. You behave as though the reader’s attention is not a public API. Each interrupt debits a trust ledger. Silence afterward is not laziness — it is how you keep the account solvent. The closing move is familiar from IP routing work: surface the intersecting idea, and shut up.4

A sentence existing in an ebook does not make it worthy of entering somebody’s feed.

“Interesting” is not inside the quote

Interestingness is a relation, not an adjective. Something becomes interesting when it collides with what a particular reader already believes — a contradiction, a convergence, a genuine novelty, or a naming of something they already felt.5

That is why the strongest cards are rarely the most representative summaries of the book. They are the lines with the greatest potential to produce a reader-side diff:

If your selector is optimising for “fair summary of chapter three,” you are building a table of contents with better fonts. If it is optimising for a clean, honest attention event, you are compiling.

The carrier hierarchy flips

Here is the inversion most teams have not named yet.

You used to think of the quote as promotion for the ebook — the teaser, with the book as the product. Under attention scarcity, the quote is the product and the ebook is the receipt. Its job moved from being-read-first to being-provenance. A quote card floating alone is a fortune cookie. A quote card with a timestamped, multi-chapter argument behind it is a claim with a receipt, and the reader can double-click if the interrupt earned it.

The long-form did not lose value when the quotes started outperforming it. It changed kind. It became the bronze layer of public presence: the falsifiable territory from which future compilations are cut.

Myth

Short-form is inherently superior; long-form is dead.

Reality

Short-form is the interface under scarcity. Long-form is the proof surface that keeps the interface honest.

The publication gate

A quota without a gate still spends budget on noise. The gate is what makes this a framework rather than a workflow of “post more snippets.”

Publication gate (minimum viable)

  1. Extract candidates from a real proof surface using stable scopes (not free-floating paraphrase).
  2. Judge for attention event, not for summary fairness: does this create useful unresolved tension?
  3. Truth-detachment test: if the line is removed from its surrounding qualifications, does it remain true? If not, go dark or re-scope.
  4. Provenance: exact source text, stable ID, path back to the full argument.
  5. Human gate: a named person can reject a high-scoring falsehood and approve a quieter true tension.
  6. Publish once as a single clean interrupt — then stop. No five bullets, no three engagement questions, no self-paraphrase.
  7. Go dark. Silence is part of the design.

Truth-detachment test (worked)

Publish (honest incomplete): “The ebook contains the idea. The quote spends it.” — The full system still holds; the proof surface exists; the claim does not smuggle a false absolute.

Go dark (or rewrite): a line that only works because three paragraphs earlier you restricted the domain, and the card drops that restriction. That is not productive incompleteness. That is a different, false claim.

Unsupported hook: a tension-bearing sentence with no path to evidence. It may win a scroll-stop and still fail the architecture, because there is no receipt. You have spent trust you cannot redeem.

Worked path: from source to interrupt

Here is the publishing path this essay argues for, grounded in a real selector toolchain pattern: deterministic structure first, model judgment second, combinations allowed so meaning is not false-atomised.

deep worldview / finished argument ↓ deterministic disassembly (HTML scopes, headings, boxes) ↓ stable IDs + exact recoverability ↓ model judges isolated units + permitted combinations ↓ human gate + truth-detachment test ↓ attention-sized artefact (card + caption + link) ↓ interrupt once → go silent ↓ proof surface remains available for voluntary descent

Code finds the pieces. AI judges what the pieces can mean. The human remains responsible for whether the interrupt is honest. That is not “AI content.” It is a compiler toolchain for attention.

One more consequence: the quote-generation pass is not only marketing. It is another evaluation pass over your thinking. It discovers which sentences actually hold the argument, which framings travel, and which ideas have enough density to survive outside their scaffolding. Those discoveries should flow back into the next long-form. The ebook produces the quote; the quote teaches you what the ebook was really saying.

The same economics in a one-line message

The architecture is not limited to social cards. The high-context / low-attention pattern shows up wherever machine attention is abundant and human attention is not.

Imagine extensive private research on a prospect — history, public statements, timing, your own product, your own prior doctrine on attention budgets — all compiled backstage. The external message that survives might be almost embarrassingly short: something like asking what they are building in year two, timed to an anniversary and a commercial gap, without making an unsupported accusation. The shortness is not evidence of shallow work. It is evidence of high context density: a narrow external message backed by a wide internal field of cognition.

That is the marketing extension of the same idea. Not “write fewer words” as a style tip. Do enough backstage cognition that every word presented to the recipient earns its interruption.

What this is not

Design the gate, then earn silence

When generative systems make content volume free, justified silence and proof-backed interruption become the scarce quality signal. The people who still feel like adults in the feed will not be the ones who posted the most. They will be the ones whose rare interrupts were expensive in the good sense — load-bearing, true when detached, backed by a receipt, and followed by quiet.

The ebook contains the idea. The quote spends it. Silence keeps the account solvent.

After this, you should be able to design a publication gate that compiles a canon into scarce, honest attention events and lets everything else go dark. That is attention-native publishing.

Field guide

The full ebook expands this into a worked selector path, publish-versus-go-dark examples, failure modes, and variants of the same doctrine beyond quote cards — always with long-form as the falsifiable receipt.

Related prior coverage: Personal Agents: Three Jobs, A Newsfeed That Hunts Its Own Blind Spots, Don’t Vault Your IP, Route It.

References

  1. Nielsen Norman Group. "How Long Do Users Stay on Web Pages?" — Users often leave web pages in 10–20 seconds; value proposition must land within ~10 seconds. https://www.nngroup.com/articles/how-long-do-users-stay-on-web-pages/
  2. Anthropic. "Effective Context Engineering for AI Agents." — Context is a finite resource with diminishing marginal returns; LLMs draw on an “attention budget.” https://www.anthropic.com/engineering/effective-context-engineering-for-ai-agents
  3. Scott Farrell / LeverageAI. "Personal Agents: Three Jobs." — Attention routing: a state change is not an attention event until adjudicated (silent-handle / interrupt / don’t-tell). https://leverageai.com.au/wp-content/media/articles/112-personal-agents-three-jobs.html
  4. Scott Farrell / LeverageAI. "Don’t Vault Your IP, Route It." — Surface the intersecting idea and shut up; publishing as edge creation under attention constraints. https://leverageai.com.au/wp-content/media/articles/117-route-your-ip.html
  5. Scott Farrell / LeverageAI. "A Newsfeed That Hunts Its Own Blind Spots." — Interestingness-as-diff: interesting is a relation to prior worldview, not a property of the item. https://leverageai.com.au/wp-content/media/articles/76-a-newsfeed-that-hunts-its-own-blind-spots.html