Home / Product / Atlas and Studio

Atlas feedback, round 1 (Jeff's first live test, 2026-06-26)

Updated Jun 26, 2026 · Affirmology_Atlas_Feedback_Round1.md

Atlas feedback, round 1 (Jeff's first live test, 2026-06-26)

Jeff's first hands-on pass of native Atlas on phone + computer. Organized and prioritized so Code can act and we can track. Tone: he likes where it's going; these are refinements. Grouped by theme, with a clear "change" per item and a priority (P0 blocks the core loop or is confusing/costly, P1 important, P2 later).

Top themes (the big ones)

1. CREATION SHOULD NOT AUTO-RENDER. Talking to Hermes / the brief / "take it to the council" should be EXPLICIT before it spends time and credits making a script or audio. Separate "chat about this structure" from "create this."
2. CREATE FOR YOURSELF, NOT OTHERS. Making an audio FOR someone else does not make sense for one user. You make it for YOU, then PUSH it to others as a suggestion for feedback (tracked).
3. MUCH MORE STRUCTURE DETAIL + TWEAKABILITY. Each structure needs a rich, expandable info view (how it is built) and more adjustable dials (not just length): music bed, the metrics, format/type, time-of-day, pacing, tone.
4. FEEDBACK MUST BE RICHER. Written + voice-note feedback, a history of everyone's feedback per item/variant, viewable in the Listening Room and askable in Hermes.
5. PLAYER. Hitting play did nothing, confirm the in-app player works; gate feedback after play.

A. Hermes + the brief + "take to the council" (P0)

• The "brief / optional steer" box plus "take it to the council" was confusing: Jeff typed "tell me more about what we can tweak here" expecting a chatbot, but it went straight to Hermes and started CREATING a script (a few minutes). Make creation EXPLICIT, a clear confirm step, not a side effect of typing or one tap.
• Add a true CHAT-about-the-structure mode: ask Hermes questions about the active song/structure WITHOUT triggering a render. (Clarify what the "brief" field is for; right now it reads like a chat but acts like a creation directive.)
• Hermes must always STATE which song/structure is active, and announce when it changes ("now talking about [X]"). If you talk about a different song, it should move/confirm the structure.
• Hermes can also talk about things unrelated to the song; that is fine, but it should be clear when it is on-structure vs off.
• Bug/confusion: clicking into Hermes sometimes said "this conversation started fresh, nothing shared with me yet" (maybe after a structure change). Make the context handoff clear, do not silently reset.
• A note should POP into Hermes when the structure changes, so the chat reflects the current song.
• Let the user put MORE in before it creates (more brief/context), then an explicit "create."

B. Person / "create for someone else" (P0/P1)

• Default creation to YOURSELF. Rethink or remove the "create an audio FOR another person" target, it does not make sense for one user.
• Reframe "create for others" as PUSH-TO-OTHERS-FOR-FEEDBACK: you make it for you, then send it as a suggestion to specific people, and the system tracks their feedback.
• Clarify People tab vs the person-selector up top (Jeff did not know the difference). Recommendation: the top selector defaults to you; the People tab is a directory where clicking a person shows THEIR charts, notes, what they have uploaded, a bit of their blueprint, not a creation target.
• Making for "a few more people" at once is an edge case, better handled as a Hermes conversation ("create this for these people, how are their links, can we tie it together") than a default control.

C. Structure detail + tweakability (P1)

• Each structure needs an EXPANDABLE detail view (a minimize/maximize button) with LOTS more information: what the structure is, how it is constructed, what is going into it. This is the creation LAB, the detail is what gives others ideas to create their own.
• Example: the Soul Song detail should explain that it grabs the hottest, identity-laden, cross-chart-resonant material and weaves it into one recognition, etc. Pull from the existing notes/docs.
• More DIALS, not just length. Surface and make adjustable: the metrics (identity, transformation, energy, pacing, emotional tone, tools, etc.), the MUSIC BED (a selector, constrained by category), the FORMAT/TYPE (reading vs audio vs tapping/EFT vs bedtime, etc.), TIME-OF-DAY (daytime/midday/bedtime), pacing, tone.
• For type-defined structures (e.g. Gene Keys Activation), the structure dictates some of this, but the user should still be able to choose pacing/tone, or recast it (a tapping version, a bedtime version, etc.).
• A scrolling area on the structure showing this rich info + the adjustable dials.

D. Create-your-own structure (P1)

• Need a way to CREATE YOUR OWN structure / start a new one. Currently unclear where.
• This can also be initiated IN Hermes: inspiration hits while talking, Hermes spins up a new structure up top and keeps it in sync with what is being discussed.

E. Feedback system (P1)

• Beyond Love / Needs-work / Approve, add WRITTEN feedback and VOICE-NOTE feedback on items.
• VOICE-NOTE into Hermes too, with context: "here is my feedback on [version]" and Hermes routes/triggers it to the right place.
• A button on Listening Room items to view the FEEDBACK HISTORY, everyone's feedback (yours + others) on that item/variant/type, over time.
• See all feedback written about a certain TYPE or VARIANT.
• Ask Hermes "what feedback has anyone given about this?" and it pulls it up.
• Possibly gate feedback to AFTER play.

F. Listening Room / Compare (P1/P2, mostly working, he likes it)

• Likes: review + deliver, Love/Needs-work/Approve, push-to-person, the Compare A/B variants, approving variants, adding more variants. "This is cool."
• Add UNAPPROVE (he approved a Pearl Prosperity Variant A and wanted to undo).
• For pushed-to-others items: show how their links are doing, tie feedback back, see if it worked.
• Clean-out: ability to clear old test renders cluttering the room.

G. Player (P0)

• Hitting play did nothing, confirm the in-app player is actually wired in Atlas; if not, build/fix it. Core to reviewing.

H. Branding (P2, quick win)

• Put a text wordmark at the very top (placeholder until a logo): the words AFFIRMOLOGY AI, all caps, SMALL (~11 to 12px), letter-spaced wide (~0.35 to 0.42em), in gold (#c89b3c) on the emerald header, centered. Matches the brand wordmark in MEMORY (Cormorant Garamond 600 letter-spaced gold). Keep a clean slot so a logo graphic can swap in later.

I. Cost note (not a build item, FYI)

• Create failed with "too low on ElevenLabs credits." Jeff is topping up. Cost lever reminder: the readings already lean Fish (cheaper); consider a Fish female option for the Soul Song / affirmational voices to cut per-render cost as volume grows (A/B vs ElevenLabs).

Suggested build order (Code)

P0 first (the confusing/costly/core): A (explicit creation + Hermes chat mode + active-structure labeling), G (player works), B (default-to-self + clarify People). Then P1: C (structure detail + dials + music bed), E (written/voice feedback + history), D (create-your-own structure), F (unapprove). Then P2: branding slot, push-to-others link tracking, clean-out.