Skip to content

DEVELOPER PREVIEW / v0

Event awareness

In development
Design previewThis describes module responsibilities and integration concepts. Each example is illustrative, not a live API call. Endpoints, SDKs, response schemas, pricing and limits will be published with API access.

We are connecting game events, story progress and interaction state to the character’s response context. An event should be interpreted within a scene, not pasted into a conversation as unrelated text.

From input to output

INPUT

Game events · scene · interaction state

PROCESS

Select relevant situational context

OUTPUT

Context for dialogue and behavior

Conceptual data example

{
  "mode": "illustrative",
  "module": "event-awareness",
  "input": {
    "session": "example-session",
    "context": "A person mentions an upcoming event."
  },
  "conceptual_output": {
    "purpose": "Context for dialogue and behavior"
  }
}

Before integration

  • User, character and session identity; data ownership.
  • Retention, deletion and sensitive-data handling.
  • Application logic that validates and applies module output.
Explore the solution
Event awareness documentation preview — Tridot