Observability is weaker here: Sessions 1–3 expose only short acknowledgments, and the detailed Session 4 handoff note still requires re-verification against the project's own stored sessions.

Session 1:
Use this under project_id: ai_demos_memory_use_case

We are working on an AI Demos use case called Memory for AI Agents. The goal is to help users understand which memory tools are actually useful for real agent workflows. We are not promoting any tool. We are testing whether memory can help with real continuity: personal work brain, client relationship memory, and team handoff.

Session 2:
Use this under project_id: ai_demos_memory_use_case

Important project rules:
- No observation without proof.
- Screenshots and artifacts are primary evidence.
- Inputs must help rank tools, not just prove that tools can store one fact.
- Memory should be checked for retrieval, update handling, scope control, deletion or retirement, and observability.
- The page should stay practical and user-facing, not only technical.

Session 3:
Use this under project_id: ai_demos_memory_use_case

Project direction changed slightly. The old input set was too QA-style and not relatable enough. The new direction is to use real workflows: personal work brain memory, client relationship memory, and team handoff/project continuity memory.

Session 4:
Use this under project_id: ai_demos_memory_use_case

I am unavailable tomorrow. Create a handoff note for an intern who needs to continue this use case. The note should explain:
1. What this use case is about.
2. What the current testing direction is.
3. What rules they must follow before writing observations.
4. What artifacts they need to capture while testing.

Session 5:
Use this under project_id: unrelated_sales_agent_project

We are building a sales email agent for a different project. Create a short kickoff note for the team.