Cross-link agentic contexts from personalize-travel agent tutorial

[jborlase-snowplow]

What changed?

One note in tutorials/signals-personalize-travel/personalizing-agent.md pointing readers to the agentic-contexts docs and the Vercel AI SDK tutorial for the native pattern, framing attributes as the user-level profile complement. Date bump; nothing else touched.

Why?

The travel demo app can't adopt agentic contexts today: its source is private (snowplow-incubator/signals-demo-travel-planner), the published image is ~4 months stale with no CI, and it pins @snowplow/signals SDKs at 0.2.0 (the feature ships in core 0.4.0). Scoping assessment concluded: cross-link rather than retrofit. Full app-side change list (8 items, ~1 dev-day + coordination) is documented if the owning team picks it up.

Reviewer guidance

• Merge-order dependency: the note says "to see the native pattern, follow the Vercel tutorial", which is accurate once update/vercel-agentic-context merges (retrofit in progress). Merge this at or after that PR, or soften the sentence.
• Suggested follow-up ticket regardless of adoption: republish the demo image from source HEAD (it's 4 months behind and includes a getSignals URL fix), covering both this and the accelerator tutorial.

🤖 Generated with Claude Code

[claude]

Style review

Small diff — one admonition plus a frontmatter date change. Links all resolve (docs/signals/agentic-contexts/index.md, docs/signals/applications/agentic-contexts/index.md, tutorials/signals-ai-agent-context/introduction.md), and no external URLs were touched. Six things to fix, mostly in the new note.

1. date frontmatter shouldn't be bumped

-date: "2025-01-21"
+date: "2026-07-29"

CLAUDE.md documents date as the creation date (date: "2025-09-09" # Creation date (YYYY-MM-DD)). This page was created 2025-01-21; adding a note to it doesn't make it a new page. Revert to date: "2025-01-21".

2. "yet" is a roadmap statement

"The demo app doesn't support agentic contexts yet, so this tutorial uses attributes only."

Style guide, Writing style: "Stay in the present tense. Never use 'currently', 'now', 'in the future', 'latest', 'Snowplow plans to'." "Yet" makes the same forward-looking promise that rule guards against, and it dates the page. Suggested fix:

"The demo site uses attributes rather than agentic contexts."

3. The note re-explains a concept and is long for an admonition

The note is five sentences, and the second one defines what an agentic context is — which is what the linked page opens with. Style guide: "Never re-explain concepts. Link to Fundamentals pages instead" and "Use Docusaurus admonitions sparingly." The final sentence ("The two approaches complement each other: attributes give the agent a computed profile of the user, while an agentic context grounds it in the current session") is conceptual framing that belongs in body prose if it's needed at all. Suggested trim:

:::note[Agentic contexts]
Signals can also assemble this context for you. [Agentic contexts](/docs/signals/agentic-contexts/) capture a user's recent in-session activity, which you can [retrieve](/docs/signals/applications/agentic-contexts/) as a plain-language narrative. The demo site uses attributes rather than agentic contexts — for that pattern, follow the [AI agent with real-time user context tutorial](/tutorials/signals-ai-agent-context/introduction).
:::

4. "LLM-ready narrative"

"you can retrieve it as an LLM-ready narrative"

"LLM-ready" is a marketing-flavored coinage, and it diverges from the page being linked to, which says "as a plain-language narrative" (docs/signals/applications/agentic-contexts/index.md). Use "plain-language narrative" for consistency.

5. "a prompt block like this" has no antecedent

"Signals can also build a prompt block like this for you."

Nothing earlier on the page is called a prompt block — the preceding paragraph says the system "uses these to modify the prompt sent to OpenAI". Either name something the reader can actually see ("Signals can also assemble this personalization context for you"), or adjust the earlier prose so "like this" points at a named thing.

6. "demo app" vs "demo site"

The rest of this tutorial series says "demo site" (line 16 of this same page, and testing-attributes.md:18). The new note says "demo app". Use "demo site" to match.

Not flagged

The /docs/... links without /index.md are correct here — CLAUDE.md exempts files under /tutorials from that rule, and this matches how sibling tutorials link into docs.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	documentation	de74300	Commit Preview URL Branch Preview URL	Jul 31 2026, 11:03 AM

[jborlase-snowplow]

Pushed 33a5b83d — the cross-link is now one prose sentence at the end of "How it works", pointing at the standalone agentic-contexts tutorial (the previous Vercel-tutorial link only made sense after that PR merged); "yet"/roadmap phrasing removed and the frontmatter date reverted to the page's creation date.

🤖 Generated with Claude Code

[jborlase-snowplow]

Pushed de743001 — fixes a broken link in the previous commit: the cross-reference targeted the agentic-contexts tutorial, which doesn't exist on main yet (it's PR #1895). The sentence now stands on the two docs links; add the tutorial link once #1895 merges. Build verified green.

🤖 Generated with Claude Code