Home / Ops / More in this area

The Results-Page Context Box: Copy v1 (PP-1, the post-Origin capture moment)

Updated Jul 18, 2026 · Affirmology_ContextBox_Copy_v1.md

Summary. Written 2026-07-18 by Cowork per Jeff's PP-1 decisions. This is the complete copy + microcopy spec for the small box that appears on the demo results page IMMEDIATELY after the Origin Soul Song listen. Companion spec: AffirmologyAttunedReadingStructurev1.md (w

The Results-Page Context Box: Copy v1 (PP-1, the post-Origin capture moment)

Written 2026-07-18 by Cowork per Jeff's PP-1 decisions. This is the complete copy + microcopy spec for the small box that appears on the demo results page IMMEDIATELY after the Origin Soul Song listen. Companion spec: Affirmology_AttunedReading_Structure_v1.md (what the captured context feeds). Concept + psychology: Affirmology_ContextCapture_AttunedReading_Concept_v1.docx. No em dashes.

The framing law. This is a gift upgrade, never a survey. Every line either names the ceiling of a stars-only reading, offers to break past it, or gets out of the way. No "help us improve," no "tell us about yourself," no progress bars, no required fields. Disclosure is reciprocity: they give one tap, we give a sharper gift.

Placement. On result.html, below the Origin player, revealed after meaningful listen progress (recommend: on player completion, or at 80 percent, or on pause after the 2 minute mark; Code's call which signal is cheapest). Never before the listen and never blocking the player. The Origin stays pure magic; the box arrives after the reveal has landed.


1. The box, state by state

State A: the invitation (default)

Headline: That was your stars alone.

Body: Everything you just heard was drawn from your cosmic blueprint. Nothing else. We never asked about your actual life, and we did not need to. But here is the truth: the blueprint shines brightest when it knows where to aim. Tell us what is alive in your life right now, and your next reading will speak straight to it.

Section label (above the chips): Where is life loudest right now?

The area chips (one tap, single select):

Chip label area enum value
Relationships relationships
Inner Child inner_child
Wealth Codes wealth_codes
Career and Calling career
Health and Energy health
Purpose purpose
Something else other

Notes: seven chips, one row wrap on mobile. "Something else" opens the same free-text field with a slightly different label (below). Chip order fixed for v1 (test later); Wealth Codes keeps its brand name, everything else stays plain.

State B: chip selected, free text revealed

Field label: Want your reading even sharper? One or two sentences about what is going on there. (Optional. Truly.)

Placeholder examples, keyed to the selected chip:

Area Placeholder text
Relationships For example: I keep choosing partners I have to fix, and I am tired of it.
Inner Child For example: I have been thinking a lot about who I was before I learned to be careful.
Wealth Codes For example: Money stresses me out even though I actually do fine. I want to feel safe around it.
Career and Calling For example: I am good at my job and quietly sure it is not what I am here for.
Health and Energy For example: My energy disappears by mid afternoon and I want to know what it is trying to tell me.
Purpose For example: I feel like something in me is waiting for a green light I keep not giving it.
Something else Tell us in a sentence or two what is alive for you right now.

These placeholders do double duty: they model a good answer (a real feeling plus a real want) and they starve the joke parser. Keep them first person and slightly vulnerable; they set the register the user writes in.

Length behavior: the field is visually sized for about 255 characters. Hidden hard cap: 800. No character counter until 220, then a soft "keep it to a sentence or two" hint at the cap. Never an error state for writing too little; a single word is a valid entry.

Submit button: Attune my next reading

Skip affordance (always visible, quiet, under the button): Skip for now. Your next reading comes either way.

State C: the submit beat (processing theater, ~3 seconds)

Sequence of three lines, fading through:

  1. Listening...
  2. Finding where your blueprint speaks to this...
  3. Attuned.

Then resolve to State D. Keep it to about three seconds; the labor should feel consequential, not slow. If the write endpoint is slower than the theater, the theater loops line 2.

State D: confirmed

Headline: Your next reading knows where to aim.

Body: It arrives in a few days, and it will go somewhere the stars-alone reading could not. Watch for it.

(If the mission-video invite shares this screen, it follows this confirmation. Its framing is a separate Cowork deliverable; hold the reward-not-toll line.)

State E: chip only, no text, submitted

Same as State D. Never acknowledge the empty field. One tap is a complete, celebrated act.

State F: skipped

No confirmation screen, the box simply collapses to one quiet line:

Line: Your next reading is already on its way.

The skip costs nothing and looks like it costs nothing. Skippers still get the full #2 reading (tier T3 in the structure spec).


2. Copy variants for testing (v1 ships the primary, log these for the A/B queue)

Headline variants: - A (primary): That was your stars alone. - B: That reading never met you. It only met your sky. - C: Imagine what it could do if it knew what you are living through.

Body close variants (the offer sentence): - A (primary): Tell us what is alive in your life right now, and your next reading will speak straight to it. - B: Point it at one area of your life, and watch how much sharper it gets.

Test one variable at a time, headline first (it carries the doubt-inoculation move: naming "stars alone" out loud is the Barnum defense, so variant C, which skips the naming, is the control for whether inoculation matters).

3. Voice and guardrail notes

4. Handoff notes for Code