Higher Self
All notes
Lessons from the field Two-minute read October 2026

What a bell taught me about software

Lessons from a field test in the high Andes that apply to any system people depend on.

David Bentley Higher Self
Based on
The first field test of El Hilo que Persiste, a programme with UNSAAC and its LAAD lab, documented in a public field report.
Not claimed
That the prototype is an emergency service, or that the area is covered. It’s a research prototype.

In July 2026, at about 4,300 metres in the Cusco region, we tested a prototype for offline community communication: a call for help sent by radio from a trail, received in a village plaza, logged, and announced by a bell. The message arrived. The bell rang. And the day taught us more about people than about radio.

The first lesson: arriving isn’t the same as being noticed. The bell rang, but it wasn’t loud enough to wake someone asleep at night, in the cold. A message that reaches the system but not a person hasn’t really arrived. In a business, that’s the order alert nobody sees, or the customer email that lands in a shared inbox nobody owns.

The second: the failure that matters most is locking out someone who’s trying to help. During the test, a responder left the app and couldn’t get back in while the alarm kept ringing. They ended up searching their browser history to find it. It’s now a question I ask of every system: if the person responding loses their place, how quickly can they get back?

The third: a record is only as good as its clock. Back from the field, we found the node’s clock was ten days behind. We could still read the order of events from the log, but not when they happened. A hash can prove a record hasn’t changed; it can’t prove when it was made. In business systems, timestamps quietly decide refunds, disputes and audits, so it’s worth knowing where yours come from.

And one lesson from before we went. Our letter to the community began, “Today we install nothing.” We came to show, test and listen, and to build only if they decided it was useful. Most software arrives the other way round. Asking first is slower, and it’s the only way I know to build something people will own rather than tolerate.

The bell rang. Everything else was what we learned.

Written by David Bentley

I build AI assistants and check the systems behind purpose-driven e-commerce brands. Based in Peru, working New York hours.

More notes

All notes
Telling the truthYour mission is a claimFor a purpose-driven brand, every sentence about the mission is a promise someone can check. That should change how AI is allowed to write. Telling the truthYour store and your email platform disagree about your customersTwo numbers that should roughly match, and what it means when they don’t. AI you can trustLearning should change guidance, never permissionsHow an AI assistant can learn from your edits without quietly giving itself more power. AI you can trustYour inbox is the AI interface you’re not usingWhy I build assistants into the email you already have, not another app to check. AI you can trustWhy AI drafts sound almost rightSounding like you is the easy part. Knowing what you’d never say is the work. AI you can trustTreat your AI like a bright new internIt has read everything and met none of your customers. The nuance is where the value is.