Home / Ops / More in this area
Updated Jul 13, 2026 · Affirmology_CodeBuildQueue_v1.md
Copy-paste tickets the code chat can build without waiting on Jeff. Each is self-contained: copy one ticket, or the whole block, into the code chat. All of these are settled UI/behavior with prototypes to build against. Note: code is on Fable, so this queue runs after Fable resets (~11am). Cowork's parallel work is at the bottom.
Prototype references (in CLAUDE OUTPUTS/Affirmology/Prototypes/): Affirmology_Wheel_Prototype_v4.html, Affirmology_Blueprint_Prototype_v1.html, Affirmology_InnerFeatures_Preview_v1.html.
Build the Explore wheel from WheelConcepts/Affirmology_WheelAlignment_FINAL_v1.json (per-constellation figure transform + code-star anchors + effective links). Data manifest per star/constellation with states owned | available | testing | locked, a per-constellation unlock field (null | premium | prereq:aries), and a per-star listen counter (7 to fill; a star may hold multiple audios that all count). Sun = home holding favorites inside it (Origin Soul Song, The Mirror); swipe up to the ring of 12; focused constellation named by what it REPRESENTS (Wealth) with the sign small (Taurus); star pattern only shows once scrolled up; interface tray under the constellation; no star names, a star is identified by its audio when tapped. Reference: Affirmology_Wheel_Prototype_v4.html.
(a) Brightness: lift the app base toward emerald and raise figure/nebula luminance so silhouettes are not pure shadow; try a code luminance filter on the art layer first. (b) Rotated-plate edges (Pisces, Virgo): alpha-feather each figure plate with a radial mask so edges fade to transparent; one mask fixes all 12 at every rotation. Publish any re-render under a NEW versioned R2 key, never overwrite.
Build the You hub and the Current Context editor exactly as in Affirmology_InnerFeatures_Preview_v1.html: nickname with edit (wires to the existing pronunciation system), Current Context modal (belief-being-busted, what-is-alive-now, what-is-coming-this-week), Blueprint link, "What We Understand" highlights view, Birth-Time card. Context fields persist to the person and feed the script generator's context input.
From the preview, plus a new third mode Jeff added: - MODE A "their chart": name, relationship, birth date, birth time+place (optional). Enables synastry/relationship audios. - MODE B "just describe": name, relationship, free-text about them. No chart; context only, so the user's own audios can hold that person. - MODE C "link in-app" (NEW): connect to another real Affirmology user by a SHARE CODE, consent-based. Flow: user A generates a code (or link), user B enters it, both get a consent prompt ("X wants to connect for relationship features"), on mutual accept they are linked. Include a simple INBOX for pending link requests, and allow a PROFILE PHOTO upload per person/user. Linked users can later opt into shared relationship audios (the two-chart Relationship Mirror). Keep consent explicit and revocable.
The card-deck bottom sheet from the preview: 3 to 5 sequenced open questions, one per card, progress bar, free-text answer, "Next/Finish". Answers append to the person's Understanding. Reusable component; each track/journey supplies its own question deck. Model the sheet on the Uber Eats bottom-sheet pattern (rounded top, grip, single focused action).
For tracks needing deeper context than a survey: the track screen shows a progress state ("2 of 5 answered"), a "Continue with Sophia" button that deep-links into the Oracle chat carrying the track context, the chat conversationally completes the remaining questions, then hands the user BACK to the track screen and asks whether to keep adding context or make the audio now. Resume must work if they leave mid-conversation. Reference: the Wealth Claim card in the preview.
2-tap rating per audio at end (landed / didn't) with a celebration micro-moment; block-intensity 1-to-10 asked at intake and day 7 on the user's own named block; voice-note reply channel. Each rating attaches to the audio ID so it maps back to the build report's craft entries.
UI shell only (the engine method exists per Affirmology_BirthTimeRectification_Spec_v1.md): the Birth-Time card routes into an Oracle conversation that asks 3 to 5 either/or life questions and pins the time. Gate: no audio renders off an unverified noon default. On success, offer a fresh Origin Soul Song.
Paste tickets 1-8 into the code chat after Fable resets (~11am). They are ordered by leverage; 1, 3, 4 are the highest. Nothing here needs a Jeff decision. The items that DO need him (star counts, greenlights, Gemini tools, nav icon refs, the 4 journey-structure decisions) live in the Google Docs and are not in this queue.