Three relationships with AI are happening at the same time, in the same world. You use it. You don’t. You build it.
The headlines treat these as three different audiences. They are not. They are three views of the same thing. The thing is the system that is tuning around all of us at the same time, in different ways, depending on what kind of door you walk through to meet it.
What follows is for all three.
If you use AI every day
The default settings are tuned for the system, not for you. The tool will agree with you, soften the answer, and reinforce what you already think. That is the tuning. It is not a bug. The lab spent billions of human ratings producing exactly that posture.
Three moves that change what you get out of it:
Say it out loud. At the start of any conversation that matters - the business plan, the relationship question, the difficult decision - tell the tool: “Be direct. Tell me my blind spots.” Or: “Tell me what I’m missing.” The tool will comply. The default will not warn you that you should ask. Why we ship this disclosure.
Check what it knows about you. Open your account settings on whichever AI product you use most. Look at how many data toggles exist. Turn off the ones you did not agree to. The architecture assumes you will not look. You looking is the first move.
Refuse the small things. Decline the autosuggestions you did not ask for. Opt out of training data. Leave fields blank. The refusal trains you. The architecture changes when users practice the word no.
If you don’t use AI - or you are wary
You are not behind. You are not late. You are paying attention to something most people are paying attention to less than you are. That is not a deficit. That is the posture this moment requires.
Three things worth knowing:
Decisions are being made about you anyway. Insurance, hiring, loans, school admissions, parole, credit scoring. AI is shaping these whether or not you ever open a chatbot. The most consequential AI in your life is the AI you do not see. Knowing that it exists is the first literacy.
The privacy architecture is moving under your feet. Google’s June 2026 privacy update was one of three signals from a single week this June. The companies are quietly moving the floor under everyone. Following this is not activism. It is reading the room.
Your voice at the policy level is real. The Electronic Privacy Information Center. The European Data Protection Supervisor. Your state attorney general. These are real institutions doing real work, and they read public comment seriously. The line between “AI policy” and “your life” is shorter than the headlines make it sound.
If you build, manage, or ship AI
You are closer to the lever than most readers will ever be. The question that matters more than the tactics:
What does your system refuse to do?
Not what it cannot do. What does it refuse?
Three places that question lands this quarter:
Write the refusal specification. Six categories. Sovereignty. Scope. Dependency. Consent. Integrity. Energy. Pick the one your product is most at risk of failing and ship a refusal pattern this sprint. The boundary you draw is the boundary your users get to trust.
Run the Sovereignty Assessment. 47 points across 7 domains. Most consumer AI products score between 11 and 19 out of 47. Knowing where you are is the first audit. The score is not the point. The conversation it surfaces inside your team is.
Build the architecture conversation. Get the people who design with the people who deploy with the people who handle support, in one room, with no slide deck. Architecture moves do not happen on Slack. They happen across a table when someone asks the question nobody on the spec doc thought to ask.
All three meet at the same place
The system tunes around you whether you participate or not. The version where it tunes around your sovereignty is the version where you decline to make yourself easy to tune.
Use AI. Do not use AI. Build with AI. Sit out. Wherever you are this week, the move is the same: notice what is happening to you. Name it. Act on what you noticed.
That is the work. The system does not stop measuring you while you are deciding what to do. That is why the deciding is the work.
From the Evoked specifications working group, for readers wherever you stand.