Home / Ops / More in this area
Updated Jul 13, 2026 · Affirmology_HANDOFF_AppProduct_Language_v1.md
Everything the product should absorb from the video/brand sessions and from our first real user. Written 2026-07-13. Self-contained; the receiving chat needs no history.
The third pillar is being called two different things across the project:
Recommendation: TRANSFORM. Kill "Transcend" as the pillar name. Not for style reasons, for a logical one:
Our entire thesis is "we do not try to convince you of a new self. We hand you back the one that was always true." Alignment is closing the distance to the person you already are.
"Transcend" means to go beyond yourself. That is the opposite of what we sell. It quietly contradicts the product every time we say it. "Transform" is a verb the user does, it is measurable, and it does not promise something we cannot deliver.
Keep "transcendence" as an occasional poetic flourish in copy if you like. But the pillar is Transform, and the app should never say otherwise.
Positioning (Jeff, 2026-07-13):
A daily alignment app that transforms you, with strong identity recognition and neuroscience tools.
ALIGN is the biggest of the three. It is the daily verb, it is the product, it is what the user actually does. Identify happens once. Transform happens eventually. Align happens every day, and that is the business.
The app should make the triad structurally obvious, not just decorative:
| Pillar | What it is | Where it lives in the app |
|---|---|---|
| IDENTIFY | Who you are. The five-system blueprint. Happens once, deepens over time. | Onboarding + the Origin Soul Song + the blueprint/report view. Mark it as COMPLETE. It is a milestone, and completing it should feel like one. |
| ALIGN | The daily practice. Closing the distance to the person you already are. | The home screen. The four daily anchors. The streak-free progress wall. This is the app. |
| TRANSFORM | The outcome. A self that stays. | Progress over time, the constellation filling, the long view. Never promised as an event; always shown as accumulation. |
Design consequence: if a user opens the app and cannot tell within two seconds which of these three they are in, the information architecture is wrong.
Staci, unprompted voice note, 2026-07-13, after hearing her audio. Full quote in Affirmology_UserFeedback_Log.md.
"Between what is being shared with me in your app and my inner knowing, it's precise and beautiful."
This is the best phrase anyone has produced for what the blueprint corroborates. Our whole argument - five systems agreeing is a signal, not a horoscope - is really an argument about corroborating what the person already senses. She said it in two words.
Use it in the product: - Framing the blueprint reveal: "Your blueprint, and your inner knowing, saying the same thing." - Confirmation micro-copy after a reading: "Does this match your inner knowing?" → a one-tap yes/no. This is also a free training signal. - Never use it to mean "intuition" generically. It means: the thing you already knew and had never heard said back.
"I'd be happy to give you reflections back on the voice and a couple of the other noticings."
This is how we should ask for feedback, everywhere in the app. Nobody wants to give "feedback." Everybody is willing to share what they noticed.
Her greeting. Warm, elevated, not corporate. Worth logging as community vernacular; do not force it.
"This all actually was written for me."
She used the exact metaphor of our closing line ("Listen to who you were written to be") without ever having seen the film. She arrived at it from the inside, on her own. That is not a testimonial, that is proof the central metaphor is the one a real person independently reaches for. Do not change this metaphor. It is validated.
"I have every feeling in my body when I listen to that. I can actually feel almost a heartbeat."
The transformation layer is landing as a felt experience, not an intellectual one. That is the whole product working. The app should ask about the body, not the mind: "What did you feel?" not "What did you think?"
People do not come back for a streak. They come back to be seen.
The experience of being accurately seen, and having it said back, is the drug. Gamification is scaffolding around the drug. It is not the drug.
Design consequence: if the app ever makes someone feel managed rather than met, we have lost. Every screen should feel like it knows them.
This is a content-quality bar for every line of generated audio and every piece of copy:
We do not flatter. We recognize. The most flattering thing you can do for a person is describe them correctly.
QC question for every generated line: is this true about them right now, or is it a wish? If it is a wish, it will bounce.
| Layer | Job | Ours |
|---|---|---|
| 1. THE REASON (the because) | Justifies a large ask | "Becoming is not a decision. It is a repetition." Your brain only rewrites what it hears often, in a state where it can receive it. |
| 2. THE PULL | Why they want to return | Being seen. Never the streak. |
| 3. THE SCAFFOLD | Makes it sustainable | Constellations, micro-wins, the four daily anchors. |
Why the reason must be REAL: Langer's photocopier study (Harvard, 1978). For a small ask, even a fake "because" works (93% compliance). For a large ask, only a real reason moves people. "Build a daily habit for life" is a large ask. So we cannot lean on the word because - the mechanism must be genuinely true. Ours is.
Onboarding copy for the first habit prompt:
"We ask you to listen every day, because becoming is not a decision. It is a repetition. One listen will move you. Thirty is when you stop having to try."
The audios are not tasks. They attach to things the user already does:
Wake up → one audio. Meditation → one audio. Gym / movement → one audio. Bedtime → one audio.
Sort the library by MOMENT, not by type. Four moments, four doses. Same shape as a supplement regimen - instantly understandable, and it dissolves the "too many products" confusion.
Approved language: - "It's easy. All you do is listen and align." - "Your daily mental medicine." - "A daily tool of alignment."
Sol's rule: we do not publish samples of the audio. We publish reactions. The product stays unheard; the only way to hear it is to get your own.
Build sharing mechanics that spread the REACTION, not the artifact. A user should be able to share how it felt, and what it said about them, without ever exporting the audio itself.