This is the companion, plain view to docs/pipeline.html — that one shows what the backend does with a check-in; this one shows what a person actually sees and taps. Screen names match the Stitch prototype 1:1, so you can check this against the real build directly.
Left column is the spine every check-in follows. Right column is everything that can branch off the Response screen — most check-ins end without ever reaching any of them.
First open only. Mascot, privacy line, one button: "Say hello." No sign-up, no intake form.
The text input is the one dominant thing on screen. Breathe / Write Together / Listen / Poem exist, but small and secondary — never competing with the input before the person has said anything.
If crisis language is detected, everything below is skipped — jumps straight to Crisis Support, right column.
"I hear you. That sounds like a lot to carry." Below the acknowledgment, at most one small, muted, easy-to-ignore line — never a two-button decision the person has to resolve. But the screen itself stays open: there's always a place to keep talking, turn after turn, like texting someone who remembers what you just said — not a single reply that ends the interaction.
Vandrevala Foundation, iCall, Dial 112. Call Now / WhatsApp. Amber, not alarm-red. The one screen that's deliberately different in tone — on purpose.
Tapped only when eligible. Appears beneath the acknowledgment, not replacing it. Can lead into Immersive Breathing — full screen, one-tap exit, "stay as long as you need."
Opens only after the quiet "want to look at it together?" is accepted. The app doesn't diagnose a single pattern — it offers a small set of plain-language options so the person names what they're feeling. Whatever they pick becomes context for the RAG layer, and the conversation continues from there, tailored to that pattern.
None of these are separate screens. They render as the same acknowledgment + quiet-line pattern — some pull a fixed redirect, life-decisions and dependency signals are generated warm within a guardrail. Visually indistinguishable from any other Response.
"Do you remember what I told you last week?" gets a light reply, not a recap. "Let's look" leads into Looking Back; "Maybe later" is a genuine, accepted deferral.
Sit behind the bottom nav / menu. A person can go here without ever checking in, and checking in never requires passing through them.
Opens with one line summarizing the week — "Tuesday felt heavy — Thursday felt lighter" — then the daily timeline underneath as supporting detail, not the other way around. No charts, no streaks. Extends to reference whether a past suggestion actually helped.
Plain language, not buried in a menu tree.
On-brand, but README flags this as a decision still open: ship in v1, or wait for the core loop to be validated first.
Same open question as Co-Create.
Not a fallback, not a degraded state — leaving the Response conversation at any point, Crisis Support, a finished breathing session, and Looking Back are all complete stopping points. The person is never left mid-task, and never made to feel like they cut something short by going quiet.
Thinking Trap, the suggestion detail screens, and the special-content variants all exist, but the default path — Home → share → acknowledgment → maybe a few more turns back and forth — is the one most check-ins actually take. The branches are exceptions, not the main event.
The Thinking Trap screen's multi-pattern selection was flagged here in an earlier pass — that was a misread. It's not a mismatch: the selection UI is the intended design, not an AI-guessed single pattern.
Currently shows an immediate two-button card ("Not right now" / "Yes, let's try") right under the acknowledgment — a decision the person has to resolve. Should be a single muted, ignorable line instead.
Four suggestion buttons (Breathe / Write Together / Listen / Poem) sit prominent, right below the input, plus a persistent feature nav — reads as a menu before the person has said anything.