Area
The consumer app, the Atlas creator studio, and where the product is going.
Home / Product
The player-first Affirmology app: the architecture decision, build briefs, delivery and onboarding plans, the experience north star, and the beta install path.
Status: DECISION DOC for Jeff, written in response to your questions on the overview. This supersedes the "just wrap everything in Capacitor" framing in AffirmologyAppDeliveryPlanv1.md where they conflict. The short version: you are right to want native for th
Purpose: everything Claude Code needs to build, through the night, (A) the lean scale-ready backend, (B) the Atlas wrap with magic-link, and (C) the Affirmology consumer app in React Native. Jeff pastes the KICKOFF block below into a Claude Code window on the
For the Founding Constellation (the first beta testers of the Affirmology app). Sol and Colin follow the same steps to install Atlas; just swap the app name. iPhone only for now. Paste-ready; lightly personalize the bracketed bits. No em dashes used, on purpos
Status: PROPOSED. This is the consumer-facing app, distinct from Atlas (the team app) and the Studio (the creation workbench), but riding the SAME cloud system (Render + R2 + Cloudflare). It is the place we send the inner orbit to actually listen, react, and t
Status: PLAN for Jeff to revise. The Apple Developer account is active, which unlocks everything below. This doc covers two shipments on the same account: ATLAS (the team app, for Jeff, Sol, Colin) and the AFFIRMOLOGY app v1 (the beta-team listening app). It a
Jeff's seed, 2026-06-20: the end-user app's audios should keep playing when the user leaves the app, should loop/repeat, and should be a full player. "I need to get the Apple subscription to build that part." This spec starts v1, led by the player (the heart o
The app version of the system. Atlas is the app; Hermes is the assistant inside it. Built on the cloud Studio (Render + R2). Status: DESIGNED, build when Render + R2 are up.
The internal creator tool where audios are made: Atlas and the Studio. Specs, UI iterations, the live change list, the build brief, and the reports hub.
The live Studio is Claude Code's earlier build (compose by person + structure, script then audio, library, result). The approved mockup CLAUDE OUTPUTS/Affirmology/AffirmologyStudioUIv3.html and the council design added a lot on top. This is the gap, prioritize
A place on the Hermes / Atlas side where Sol and Colin can look through the reports we push them and easily give ideas back, by text now and by voicenote once that's enabled. Email goes out in parallel as a nudge, but the real loop lives
GREENLIT by Jeff 2026-06-20 (Hermes flagged it can't create a Studio entry / trigger a render from chat). This closes the gap that makes Hermes a writing assistant instead of a production assistant. Same family as C16 (cross-chat push) and C15 (field-briefing
Per your note, Atlas's default look uses the clean non-hooded robes, not the cowl. The locked anchor plus four fresh front-facing takes in the open-shoulder robes, glowing gold eyes. The hood stays as a secondary variation only.
Bald is now Atlas's primary look, with the hood kept as a variation. Full 4K model sheet below, plus the bigger-kintsugi tests you asked for.
The two locked heroes, each as a reusable Higgsfield character Element, shown from multiple angles and in both eye states (glowing at rest, real when speaking), with their bible. Drop these into any scene, report, or the investor video and they stay consistent
This is the working overview of Atlas, the app version of the Affirmology system. It builds on the original AffirmologyAtlasAppSpecv1.md and fleshes it out into a buildable v1. Mark it up freely. The companion how-to (AffirmologyActivationHowTov1.md) holds the
How to get the Studio live at studio.affirmology.ai, and how to stand up a safe knowledge repo for Sol and Colin that never contains equity or share documents.
Pick whose chart you're composing for, see what the team has been creating, and start something new.
A private workbench for creating Sacred Audio. This guide updates as the Studio does, the changelog at the bottom tracks every version.
This is the authoritative brief for rebuilding the Studio front-end and wiring it to the real engine. Jeff has approved the design. Build THIS. Do not improvise a different shape.
The internal tool where Sol and Jeff (later Colin and an inner circle) create, test, version, rate, and curate audios across many categories. Lives at studio.affirmology.ai, password protected. Goal: empower endless testing, keep what lands, drop what does not
Date: June 15, 2026. For: The Claude Code session building the cloud studio. Purpose: A complete handoff. Everything below was decided with Jeff. Build from this. Where it says "inspect the existing code," do that before assuming signatures.
Where the product is heading: the Living Profile customer-intelligence layer, the personal knowledge base and golden tier, the Hermes creation experience, companion audios, and membership pricing.
This is a LIVING document. Edit it in place as the thinking evolves; do not make a v2. It holds the running conversation on membership tiers and pricing: prior ideas, present ideas, decisions, and open questions, all in one place. Newest decisions go in the DE
The vision in one line: a creator talks to Hermes like a brilliant studio partner, the council composes from the real chart, the script unfolds in the chat, the creator shapes it by talking, then says "render it" and it lands in the listening room and the pers
Status: living, started 2026-06-21 (Cowork). What it is like to BE an Affirmology facilitator, designed so in-person demos land hard. This is the experience-design and runbook doc. Companion to AffirmologyAudioSuitesBuildQueuev1.md (the audios), AffirmologyGro
Jeff's vision, 2026-06-20: "Beyond the Structures we need a customized knowledge base, person-specific chatbot audio creation. That's what the golden tiers will use, and what people ultimately want. Credits to buy things like that. We need it now, for me and S
Jeff's idea (2026-06-20), captured: run deeper analyses on each person's chart through different lenses (prosperity, relationship, career, and more), look for trends, and build a richer customer profile. Then use that profile in many ways: customize the app ex
Jeff's north star, 2026-06-20: "The chat should be a place of epic delivery and interaction, a cheat code superhighway into all of our systems. At least for me; Sol and Colin's accounts should have a few limitations."
The single-person Sacred Audio is solved and now rendering on the Mac through the Studio. This spec designs the missing capability: an audio for two people (and later a whole team) that speaks to them as a unit AND to each of them individually, all from their
Midsummer, the year after.