Authority in the guise of evidence

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