Interactions

Interactions are the source records your application publishes after an agent turn. Reflexio stores them as evidence, groups them into requests and sessions, and uses them to extract profiles, playbooks, and evaluation signals.

What to Publish

Publish the complete turn that matters for learning:

• The user's message or action
• The agent response
• Any follow-up correction, confirmation, or outcome
• A stable user_id and session_id
• A meaningful source, plus agent_version when comparing agent behavior

Text is the common case. An interaction may also carry an image, an action such as a click or purchase, expert-provided ideal content, or shadow content used for evaluation.

Requests and Sessions

A request is one published batch of interactions. A session groups related requests into one user journey or conversation. Use the same session_id for every turn that should be evaluated or inspected together.

Session
├── Request 1: user question → agent response
├── Request 2: user follow-up → agent response
└── Request 3: user correction → agent response

See Requests and Sessions for lifecycle and cleanup details.

How Learning Uses Interactions

1. Reflexio validates and stores the published records.
2. Extraction runs when the configured window and stride allow it.
3. Durable user facts can become profiles.
4. Behavioral corrections and successful procedures can become user playbooks.
5. User playbooks may later aggregate into reviewable agent playbooks.
6. Session-level evaluation measures outcomes independently of extraction.

Publishing is asynchronous by default. The request is durable before background learning finishes; use the returned request ID to inspect learning status when needed.

Design Guidance

• Publish complete context, but do not duplicate the same turn in multiple requests.
• Keep role names consistent: User, Agent, System, or Expert as appropriate.
• Reuse session_id only for genuinely related requests.
• Use source for stable product or traffic categories, not free-form descriptions.
• Include user feedback explicitly; it is stronger learning evidence than an inferred outcome.

For payload examples, see Publishing Interactions. For every field and client method, see the Interaction API Reference.