A model can know the whole corpus and still not know who it is speaking with.
Movemental can give an AI access to Alan Hirsch’s complete published body of work.
That solves only half the problem.
If the system knows nothing about you, it still has to guess who is asking the question.
Where do you live? What kind of work do you do? Are you leading a church, a team, a nonprofit, a neighborhood initiative? What language do you prefer? What are your gifts? What have you already tried? What have you already learned?
For a factual question, none of that may matter.
For a question like:
“What should I actually do with this?”
it can matter enormously.
So Movemental lets you build a small amount of context about yourself and carry it with you.
Not so we can know everything about you.
So the system has to invent less.
This body of work. This person. This place. This situation.
A more grounded conversation
You decide how much context is useful.
Your Movemental profile can include things such as who you are, the frameworks you already use, the place you are in, and the work you have done with Movemental.
Everything is optional.
And not everything is relevant every time.
Manage my context →So you do not have to become a stranger every time.
Imagine that you upload a 40-page 5Q assessment while working through APEST with Alan Hirsch.
Later, you enter a neighborhood experience with Brad Brisco.
The useful outcome is not:
“Please upload your assessment again and explain who you are from scratch.”
The useful outcome is:
“You have already chosen to tell Movemental this. Would it help to use it here?”
The same can be true for your neighborhood, language, role, previous Practices, or reflections.
Your Movemental identity can move across the network while your relationships with individual leaders remain distinct.
One account. Many relationships. Context that can travel with you.
Your profile travels. The leaders’ corpora remain separate.
Relevant context, not maximum context.
Just because Movemental knows something does not mean every AI interaction needs it.
“Where does Alan write about liminality?”
“How should I approach this conflict on my team?”
Our design principle is:
Use the least amount of personal context necessary to make the experience meaningfully better.
Research should stay research.
Personal context becomes more useful as a conversation moves toward:
We should tell you when your context leaves Movemental.
Some Movemental experiences use third-party AI models.
When an AI needs context to respond, portions of your current conversation and relevant profile information may need to be sent to that provider.
Our responsibility is not to hide that behind the word “AI.”
It is to make the flow understandable.
The standard we are building toward is:
Send only what the interaction needs.
Avoid sending identifying information when identity is unnecessary.
Do not send your entire profile simply because we have it.
Tell you which providers process your information.
Verify what those providers retain and whether submitted data is used for model training.
We will publish those details plainly rather than making promises that are stronger than the underlying technology or contracts.
The code should make this distinction, not merely the copy.
Reflection is not a feed.
Personal reflections may involve things that are personal: a difficult relationship, a leadership failure, a fear, a team conflict, something happening in your neighborhood, something you tried that did not work. That material is there to serve your reflection.
It is not automatically turned into a public story, another person’s AI source, Alan’s corpus, Brad’s corpus, marketing content, or a network-wide knowledge base.
If we ever invite you to share something publicly, that should be a separate, explicit choice.
And if your reflection mentions another person, their identifying information deserves particular care too.
We do not sell your personal data.
Our business is the work we build with you—not information about you.
You should be able to see it, change it, and remove it.
Context only remains trustworthy if you control it. You should be able to:
And if deleting information cannot instantly remove it from backups, logs, or a third-party processor, we should tell you exactly what remains and for how long.
The standard we are trying to deserve
Know me only so you can serve me better.
Keep only what there is a reason to keep.
Use my context only where it is relevant to the experience I chose.
Do not sell it or turn it into somebody else’s asset.
Let me see it, change it, and remove it.
And tell me plainly when another system needs to receive some of it in order to serve me.