DEVELOPER PREVIEW / v0

Action selection

Research

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 researching a decision layer between character intent and application actions. Partners would define the allowed actions; the character would propose a context-aware choice. Execution and permissions stay with the application.

From input to output

INPUT

Intent · goals · allowed actions

PROCESS

Evaluate a bounded set of actions

OUTPUT

Action proposal for application approval

Conceptual data example

{
  "mode": "illustrative",
  "module": "action-selection",
  "input": {
    "session": "example-session",
    "context": "A person mentions an upcoming event."
  },
  "conceptual_output": {
    "purpose": "Action proposal for application approval"
  }
}

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