Authority in the guise of evidence

09 Apr 2026

Shreyas Prakash headshot

Shreyas Prakash

Authority was once the primary means of determining truth. If the Pope at Vatican City declared something right or wrong, it was accepted without question. Over time, that model weakened, replaced in large part by the rise of rational, scientific inquiry. At least on the surface, we moved from deference to authority toward deference to method. But that shift is less absolute than it appears.

Explanations carry more weight than mere outputs. Progress does not come from accumulating results, but from correcting flawed ideas. A good explanation is not just predictive; it is resilient under scrutiny. The difficulty, however, is that deriving such explanations is expensive. Even if one is capable of independently verifying a claim with pen and paper, the time required makes it impractical at scale. In practice, this constraint forces a compromise. We rely on systems that compress explanation into signals we can consume quickly, even if that means trusting intermediaries.

Peer-reviewed papers in scientific journals illustrate this tension. They represent a system where credibility is delegated to an institutional process rather than individually verified. The assumption is not that every reader will replicate the results, but that the process itself filters for quality. This makes science functionally scalable, but it also reveals its dependence on a form of distributed authority. What appears as objectivity is, in part, structured trust.

Some thinkers, such as Balaji Srinivasan, argue that science will shift from “prestigious citation” toward “independent verification.” The idea is that advances in computation and tooling will allow individuals to verify claims directly, reducing reliance on institutions. Yet this vision runs into a fundamental constraint: verification does not just require tools, it requires attention. Even if verification becomes cheaper, it is unlikely to become free. Most participants in any system will still prefer to trust rather than verify.

The notion of a fully “trustless” society, often imagined in technological circles, rests on the assumption that trust can be eliminated entirely. In reality, trust is not removed but displaced. Systems that rely on code and cryptography shift trust from human institutions to technical ones. The claim that code is neutral ignores the fact that code is written, maintained, and executed within environments controlled by specific actors. Even in systems designed to minimize trust, there remains an implicit reliance on those who design the protocols and the hardware that runs them.

This is evident in emerging approaches such as trusted execution environments, discussed by Vitalik Buterin. These systems attempt to guarantee that computation occurs without leaking information, offering a form of verifiable privacy. Yet even here, the guarantees are not absolute. Hardware can be compromised, assumptions can fail, and users must ultimately trust that the underlying infrastructure behaves as advertised. The system reduces the surface area of trust, but does not eliminate it.

What becomes clear is that authority has not disappeared; it has become more abstract. In pre-modern systems, authority was visible and centralized. In scientific systems, it is procedural and institutional. In computational systems, it is embedded in code, protocols, and hardware. Each transition claims greater objectivity, but each also introduces new, less visible dependencies. Trust moves downward through layers, becoming harder to inspect as it becomes more technical.

This suggests that the future is not a binary choice between trust and verification, but a spectrum of trade-offs. Different domains will tolerate different levels of trust depending on the cost of error and the cost of verification. Financial systems may push toward near-complete verification, while everyday decisions will continue to rely on heuristics and delegated judgment. Rather than eliminating authority, we are learning to compose it—deciding where to rely on institutions, where to rely on code, and where to rely on ourselves.

In that sense, the dream of a fully trustless society is less a destination and more a direction. It reveals a desire to reduce arbitrary power, but it underestimates the irreducible costs of knowing. As long as explanations remain expensive and attention remains scarce, systems of trust will persist. The question is not whether we can remove authority, but how we distribute it, how we audit it, and how we remain aware of where it quietly resides.

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. 18 key ideas from reading Henrik Karlsson this monthwriting
  2. Stop arguing, and start drawing circles togethermathematics
  3. The whole world is just the snake eating its own tailmental-models
  4. Life lessons and hot takes from my 30slifestyle
  5. Building a skill for coherent science illustrationsscience
  6. My agentic engineering workflow (step by step)agentic-coding
  7. Hammock driven developmentagentic-coding
  8. Peculiar ways number three fits into our funny little brainsmental-models
  9. AI sandwich as a defacto principle for anything agentic engineering relatedagentic-coding
  10. Authority in the guise of evidencecritical-rationalism
  11. Map is not the territoryphilosophy
  12. Self hypnosis as a manifestation ritualmeditation
  13. Hegelian dialectic for structured reasoning with AI agentsphilosophy
  14. How I prepare for tough negotiations nowadaysnegotiation
  15. When should we steelthread somethingproduct-development
  16. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct
  17. Healthy conflict in teams have a tipping pointteam-building
  18. How I deslopify AI writingwriting
  19. How I started building softwares with AI agents being non technicalagentic-coding
  20. Read raw transcriptswriting
  21. Legible and illegible tasks in organisationsproduct
  22. L2 Fat marker sketchesdesign
  23. Writing as moats for humanswriting
  24. Beauty of second degree probesdecision-making
  25. Boundary objects as the new prototypesprototyping
  26. One way door decisionsproduct
  27. Finished softwares should existproduct
  28. How I periodically rank my rough draftsobsidian
  29. Flipping questions on its headinterviewing
  30. Vibe writing maximswriting
  31. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  32. How I build greenfield apps with AI-assisted codingagentic-coding
  33. We have been scammed by the Gaussian distribution clubmathematics
  34. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  35. I was wrong about optimal stoppingmathematics
  36. Thinking like a shipmental-models
  37. Hyperpersonalised N=1 learningeducation
  38. New mediums for humans to complement superintelligenceagentic-coding
  39. Maxims for AI assisted codingagentic-coding
  40. Virtual bookshelvesaesthetics
  41. It's computational and AI everythingagentic-coding
  42. Public gardens, secret routesdigital-garden
  43. Git way of learning to codeagentic-coding
  44. Style Transfer in AI writingagentic-coding
  45. Understanding codebases without using codeagentic-coding
  46. Vibe coding with Cursoragentic-coding
  47. Virtuoso Guide for Personal Memory Systemsmemory
  48. Writing in Future Pastwriting
  49. Publish Originally, Syndicate Elsewhereblogging
  50. Poetic License of Designdesign
  51. Idea in the shower, testing before breakfastsoftware
  52. Technology and regulation have a dance of ice and firetechnology
  53. How I ship "stuff"software
  54. Writing is thinkingwriting
  55. Song of Shapes, Words and Pathscreativity
  56. How do we absorb ideas better?knowledge
  57. Read writers who operatewriting
  58. Brew your ideas lazilyideas
  59. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  60. Compound Interest of Private Noteswriting
  61. Conceptual Compression for LLMsagentic-coding
  62. Meta-analysis for contradictory research findingsdigital-health
  63. Proof of workproduct
  64. Gauging previous work of new joinees to the teamleadership
  65. Task management for product managersproduct
  66. Beauty of Zettelswriting
  67. Stitching React and Rails togetheragentic-coding
  68. Exploring "smart connections" for note takingwriting
  69. Deploying Home Cooked Apps with Railssoftware
  70. Repetitive Copypromptingwriting
  71. Questions to ask every decadejournalling
  72. Balancing work, time and focusproductivity
  73. Hyperlinks are like cashew nutswriting
  74. Brand treatments, Design Systems, Vibesdesign
  75. How to spot human writing on the internetwriting
  76. Can a thought be an algorithm?product
  77. Opportunity Harvestingcareers
  78. Everything is a prioritisation problemproduct
  79. How I do product roastsproduct
  80. The Modern Startup Stacksoftware
  81. In-person vision transmissionproduct
  82. How might we help children invent for social good?social-design
  83. The meeting before the meetingmeetings
  84. Design that's so bad it's actually gooddesign
  85. Lessons learnt interview prepping for product rolesinterviewing
  86. Obsessing over personal websitessoftware
  87. English is the hot new programming languagesoftware
  88. Better way to think about conflictsconflict-management
  89. The role of taste in building productsdesign
  90. Dear enterprises, we're tired of your subscriptionssoftware
  91. Products need not be user centereddesign
  92. World's most ancient public health problemsoftware
  93. Pluginisation of Modern Softwaredesign
  94. Let's make every work 'strategic'consulting
  95. Making Nielsen's heuristics more digestibledesign
  96. Startups are a fertile ground for risk takingentrepreneurship
  97. Insights are not just a salad of factsdesign
  98. Minimum Lovable Productproduct
  99. Methods are lifejackets not straight jacketsmethodology
  100. How to arrive at on-brand colours?design
  101. Minto principle for writing memoswriting
  102. Importance of Whytask-management
  103. Quality Ideas Trump Executionsoftware
  104. Why I prefer indie softwareslifestyle
  105. Use code only if no code failscode
  106. Self Marketing
  107. Personal Observation Techniquesdesign
  108. Design is a confusing worddesign
  109. A Primer to Service Design Blueprintsdesign
  110. Rapid Journey Prototypingdesign
  111. Visualise detailed file structures on CLIcli
  112. Do's and Don'ts of User Researchdesign
  113. Design Manifestodesign
  114. Complex project management for productproducts
  115. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  116. Pedagogy of the Uncharted — What for, and Where to?education
  117. Future of Equity with Ludovick Petersinterviewing
  118. Future of Ageing with Mehdi Yacoubiinterviewing
  119. Future of Tacit knowledge with Celeste Volpiinterviewing
  120. Future of Mental Health with Kavya Raointerviewing
  121. Future of unschooling with Che Vanniinterviewing
  122. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  123. Future of work with Laetitia Vitaudinterviewing
  124. How might we prevent acquired infections in hospitals?digital-health
  125. The why to endure any howentrepreneurship
  126. Design education amidst social tribulationsdesign
  127. How might we assist deafblind runners to navigate?social-design