# Proposed relationship-to-follow-up story — unproduced final cut

1. **Find context.** Show the actual `Rowan` search and `workshop` tag result, with a large `FICTIONAL SOURCE-RUN` label outside product pixels. Both states are separate filters, not combined search-and-tag behavior.
2. **Recall the interaction.** Move across the real Cedar Rowan detail image; annotate the fictional `.example.test` address, note and meeting entry without implying a real contact or live service.
3. **Review a date, not a push notification.** Show the saved reminder and the real edit fields. An on-screen note must say “dated item inside Contactly; no external alert.” Avoid interpreting the UI's observed “just now” badge as a correct countdown.
4. **Close at the access boundary.** State that the API has no owner authentication and must stay inside a trusted local/deployment boundary. The public Pages site is a static source overview only.

The paired poster studies combine a legible **actual** contact-detail crop and reminder-edit control crop with the release-specific headline “Remember the conversation. Review the follow-up.” They include `FICTIONAL LOCAL FIXTURE` and a thumbnail-size proof band reading `NO HOSTED APP · NO OWNER AUTH` and `EDIT NOT SAVED · NO EXTERNAL ALERT`. Review the full 1600×900 pair and 384×216 thumbnails before approval; the illustrative static-site card is not used as product pixels.

The poster studies are review candidates. The separate silent `workflow-edited-{light,dark}.webm` pair trims both raw captures at 1.44 seconds and shows only the genuine contact-detail → reminder navigation; it is awaiting playback review and is not a final film. Search/tag remain separate actual PNG states. Cartesia narration, Remotion animation and synchronized captions do not exist yet. The original `workflow-{light,dark}.webm` files retain a loading-state start and a dark transition canvas artifact and remain diagnostic provenance.