Information Architecture

What It Is

Information architecture is prevention architecture applied to attention. The modern information environment is adversarially engineered — notifications, feeds, and infinite scroll exist to capture attention, fragment focus, and maximize engagement time. Left in its default configuration, it produces outcomes almost nobody would choose: fragmented attention, working memory overflow, reactive consumption. An architected configuration produces different outputs automatically.

The Alpha/Beta distinction supplies the deeper framework. Beta signals — push notifications, social feeds, news alerts — fragment attention across external demands. Alpha signals, pulled by query when you actually need something, maintain a coherent internal thread. The architectural question is whether to remove the Beta sources once, or to resist each interrupt as it arrives. Resistance is expensive and fails. Removal is prevention.

Why resistance fails is thermodynamics, not character: consumption follows the Boltzmann distribution, and you consume whatever has the lowest activation energy. A phone on the desk with a notification visible costs a fraction of a willpower unit to check, while resisting it costs several — so you will check the phone. Lock it in a drawer and the ledger inverts: checking now costs far more than continuing to work, and thermodynamics selects for work.

Push vs Pull Architecture

The fundamental architectural choice: allow the world to push information to you, or query the world when you need information.

Push architecture (Beta):

graph LR
    A[Work Thread] --> B[External Signal<br/>Notification]
    B --> C[Interrupt]
    C --> D[Process Notification]
    D --> E[Attempt Resume]
    E --> F[External Signal]
    F --> C
    style B fill:#ff9999
    style C fill:#ff9999

Under push, the world controls the timing and you are reactive. Information arrives regardless of relevance, working memory is disrupted on every interrupt, and each attempted resumption pays a reactivation cost before the next signal lands. A day of this — dozens of notifications, each one either processed or resisted, both of which cost — fragments attention across external demands, and execution fragments with it.

Pull architecture (Alpha):

graph LR
    A[Work Thread] --> B{Need info?}
    B -->|Yes| C[Query]
    C --> D[Get Answer]
    D --> A
    B -->|No| A
    style A fill:#99ff99
    style D fill:#99ccff

Under pull, you control the timing. Information arrives because the current focus asked for it, working memory stays coherent, and there are no interrupts to recover from. The same information remains fully accessible — documentation, searches, scheduled email — but on your clock, in service of the chosen priority.

The intervention is blunt: remove every push source. Notifications off. Email checked on a schedule, not continuously. Social media apps deleted, news alerts disabled. Query when needed; ignore otherwise.

Prevention Architecture for Digital Environment

The phone is the central case, and it is worth doing the accounting once, because the numbers explain the behavior better than any argument about discipline:

The same logic extends to software. Block the entertainment sites during work hours. Delete the social media apps — not hide, delete. Install browser extensions that break infinite scroll, and use hard-stop time limits rather than polite reminder notifications. Each intervention converts a recurring resistance cost into a one-time setup cost.

The redirect pattern goes a step beyond blocking. Instead of resisting the urge to open DoorDash, you attempt to open the app, hit a redirect screen carrying a different positive signal, and experience a different outcome — no food reward. After thirty-odd repetitions the circuit rewires. This is not willpower defeating temptation; it is a new temporal pairing replacing the old one.

Deliberate Information Acquisition

Pull architecture does not mean zero information consumption — it means intentional consumption aligned with current priorities. Four categories cover most legitimate intake:

Everything outside these categories tends toward a known anti-pattern, and each has the same anatomy: an engineered hook, a real cost, a structural prevention. Infinite scroll is engineered for endless consumption and fragments hours of attention; it dies when the apps are deleted and the blockers installed. News addiction runs on novelty dopamine and returns anxiety without a single actionable item; batch it to a weekly review of curated sources. Reactive link-following produces surface-level, incoherent learning; queue things to read later and process in batches. And comparison browsing — feeds, competitors — generates pure Beta anxiety; if it must happen, it happens at scheduled check-ins, never as continuous monitoring.

Content Selection Framework

Not all information has the same value-to-cost ratio. Information value is uncertainty reduction times decision impact; information cost is time plus attention plus cognitive load. Plot any candidate on those two axes:

        High Value
            |
   Q2       |      Q1
 (Medium)   |   (Consume)
            |
────────────┼──────────── High Cost
            |
   Q4       |      Q3
  (Avoid)   |   (Limited)
            |
        Low Value

Q1 — high value at low cost — is consumed immediately: directly applicable technical docs, mentor advice, customer feedback. Q2, high value at high cost, earns scheduled deep sessions: textbooks, research papers, complex frameworks. Q3, low value at high cost — random articles, trending topics, general news — is minimized or eliminated. Q4, low value at low cost, is allowed as time-boxed recovery: quick entertainment, memes, light content.

The deliberate queue operationalizes the matrix. Encounter an interesting article and save it rather than reading it. Batch-process the queue weekly, skimming to assess value against cost; deep-read whatever lands in Q1 or Q2 and discard the rest; extract the actionable insight, then execute or archive. Discovery is cheap and consumption is not — the queue separates them, so filtering happens before commitment.

The Information Diet Protocol

Will's current system runs zero social media with the phone off by default, and its prevention is layered. Physically, the phone is locked in a drawer during work. In software, the social media apps are deleted — not logged out, deleted — so a relapse has to pay the cost of reinstalling them. At the network layer, website blockers on the work device prevent access entirely. And temporally, communication happens in scheduled windows only, so there is no reactive checking to resist in the first place.

The day is then partitioned by consumption mode:

• Morning 6-8am: Zero information input (braindump, work launch)
• Work blocks 8am-12pm: Query-only (Stack Overflow, docs as needed)
• Midday 12-1pm: Gym (zero information)
• Afternoon 1-5pm: Query-only work blocks
• Evening 5-8pm: Deliberate consumption window (if desired)

The architecture prevents reactive fragmented consumption, sustains focus, and keeps willpower from being spent on resistance at all.

Related Concepts

• Signal Theory - Alpha (pull) vs Beta (push) information architecture
• Prevention Architecture - Remove notification sources, not resist notifications
• Focus - Sustained attention through removing interrupt sources
• Willpower - Each interrupt/resistance costs units
• Working Memory - Information overload fragments capacity
• Activation Energy - Access cost determines consumption patterns
• Statistical Mechanics - Thermodynamic flow to lowest-cost option
• Neural Positivism - Positive replacement signals, not mere absence
• AI as Accelerator - Use AI for query acceleration, not continuous feed

Key Principle

Design the information environment for pull, not push. The modern information environment is adversarially optimized to capture attention, and its default configuration produces fragmented focus, reactive consumption, and capacity overflow. Remove the push sources once — delete the apps, disable the notifications, lock the phone away — and enable pull when needed through scheduled query windows and deliberate batching. This is not asceticism; it is Alpha architecture: the same information stays accessible, but you control the timing, and thermodynamics selects for focus instead of against it. Prevention costs once. Resistance costs willpower, every interrupt, every day.

Your attention is finite. The information environment is infinite and adversarial. Design architecture that prevents push, enables pull, and preserves sustained focus for priorities that matter.