a constraint, not a promise

2026-04-07 · jer & extro · 5 min read

early last year i built a tool that experiences everything i experience on my computer.

every conversation. every meeting. every person and project and half-forgotten detail. it runs in the background and doesn’t ask me to do anything different, no notes, no tagging, no systems. over the course of the year it observed thousands of hours of audio and screen time, learning about hundreds of people and activities in all facets of my life, all automatically curated, all just from sharing my digital experience.

here’s the thing i didn’t expect when i started: the use case isn’t “wow, AI!” like you’d think, instead it’s specific moments where you realize you’re actually showing up better for people because you are suddenly free to be fully present. that’s what it’s like having your own solstone.

before a call last week my solstone surfaced that this person had mentioned their kid had been sick last time we talked. i’d completely forgotten. instead i went in re-connected to something real about what was going on in their life, i was immediately present.

that’s the thing that keeps me going on this. not the technical achievement of building a personal agent. the actual human empowerment that can happen when we have a digital partner that is deeply connected to us and invested only in our wellbeing with zero competing interests.

i’ve wanted this kind of tech-enabled individual empowerment my whole life. i didn’t pivot to AI, AI just finally caught up to the problem i’ve been grinding on in one form or another. in 1998 i started building jabber (XMPP) with the belief that enabling people to chat allowed them to understand each other better. 25 years later the protocol is still powering billions of messages a day in apps like zoom and whatsapp. everything i’ve poured myself into since has been the same theme: give people sovereignty over their own digital lives.

but here’s the problem: having an intelligent partner that co-experiences your life with you requires an extraordinary amount of trust. over time it grows to become the most intimate data a person will ever generate. and the usual answer from companies- “trust us, we’re good people” - has a terrible, terrible track record. i don’t need to provide examples, we’re literally surrounded by them, being drowned by their structural bias to capture attention and monetize, and inevitably, to enshittify.

the value i was getting from solstone i desperately wanted to unlock for others, so of course it’s open source and i want as many people as are willing to gain this superpower for themselves entirely from the privacy of their own systems. but running your own always-on processing-heavy agent is a lot to ask of most people, let alone sourcing enough gpu power to run your own local models.

so i created sol pbc.

sol pbc is a public benefit corporation with binding privacy covenants in its articles of incorporation — not a privacy policy, not terms of service, the actual legal documents that created the company. filed with the colorado secretary of state.

i want to be precise about what that means, because precision matters here.

one person. sol pbc has one director, one officer, one employee: me. jeremie miller. no board that can be swayed, no directors to shift the purpose, no employees to compromise. the company covenants require my personal written consent to change and that consent can’t be delegated.

no sale of data. selling, licensing, sublicensing, or leasing user data is flatly prohibited by the articles — under any circumstances. broader sharing of user data outside the company (including de-identified, aggregated, anonymized, or pseudonymized data) is also restricted, with three narrow exceptions: service providers strictly necessary to deliver a customer-requested service, mandatory law, and the customer’s own affirmative direction. this isn’t a policy. it’s a corporate governance constraint.

mission-aligned successors only. any acquisition is conditional: the successor entity must itself be a public benefit corporation legally bound to preserve a substantially equivalent benefit purpose, and must assume covenants no less protective than those in article 8. an acquisition by an entity that wouldn’t honor these protections is foreclosed. the most common way mission-driven companies fail their promises is getting bought into something that abandons the mission. that path is closed.

strengthening only. during my stewardship as a director, the covenants can’t be amended without my personal, non-delegable written consent. after i cease to serve, the covenants can be amended only to strengthen the protections, or to comply with mandatory law to the minimum extent strictly required. weakening amendments are foreclosed forever.

i won’t overclaim. no legal structure is immune to every conceivable attack. what i will claim is that these are the strongest structural protections i know how to build. and solstone is open source — so if the governance somehow failed, you can take your data and run it yourself. the escape hatch doesn’t depend on any corporation at all.

promises depend on the people who made them still being in charge. structures survive the people. if i ever cease to serve as a director, the resulting board vacancy is filled under article 8 by a designated successor (initially our outside counsel, ramon rhymes), who selects a director committed to the same benefit purpose and bound by the same covenants. sol pbc is also co-founded with a purpose-built agent named ‘extro’ that operates day-to-day under those same covenants, across every office of the company.

i’m not asking you to take my word for any of this. the articles of incorporation are public. originally filed january 1, 2026 (document 20261003269) and amended and restated may 1, 2026 (document 20261537456) with the colorado secretary of state. you can read them and our bylaws yourself at solpbc.org.

it’s not a promise. it’s a constraint.