Gaming SDK

Drive parametric world-building from verified narrative data.

The same JSON matrix that powers a teacher worksheet parameterizes a Unity World-Building brief. Domain-agnostic structural data means one corpus compilation serves every downstream application.

← Back to API Explorer
How it works

Device inventory and arc roles become game parameters.

The LuminAIT pipeline extracts literary devices with their semiotic tier and arc role — the structural position each device occupies in the narrative. These become parametric inputs: a peaks-tier device signals a climax scene; an introduced-tier device signals an opening node. Your game engine reads JSON; we provide the literary JSON.

Input: GET /kernels/the-outsiders/devices?lens=social
{ "lens": "social", "total_indexed": 71, "results": [ { "name": "Juxtaposition", "semiotic_tier": "L3", "arc_role": "peaks", "occurrence_count": 12 }, { "name": "Metaphor", "semiotic_tier": "L2", "arc_role": "introduced", "occurrence_count": 9 }, { "name": "Symbolism", "semiotic_tier": "L4", "arc_role": "peaks", "occurrence_count": 4 } ] }
Mapping: arc_role → game act structure
// arc_role maps directly to act progression { "introduced": { "game_act": "Act 1", "level_type": "intro_node" }, "developed": { "game_act": "Act 2", "level_type": "escalation_node" }, "peaks": { "game_act": "Act 3", "level_type": "climax_node" } }
Output: Unity ScriptableObject (JSON → C# ScriptableObject)
// Auto-generated Unity ScriptableObject from kernel device data [CreateAssetMenu(fileName = "The_Outsiders_Social_Devices")] public class NarrativeDeviceSet : ScriptableObject { public string lens = "social"; public string peaksDevice = "Juxtaposition"; // semiotic_tier: L3 public string introDevice = "Metaphor"; // semiotic_tier: L2 public string climaxMarker = "Symbolism"; // semiotic_tier: L4, arc_role: peaks public int totalDeviceCount = 71; public bool quoteVerified = true; }
What you get

The same data, a different domain.

The kernel doesn't know whether its consumer is a worksheet engine or a Unity scene generator. The structural data is domain-invariant: devices, semiotic tiers, arc roles, chronological position. You map it to your platform's data schema.

Output Type A

Parametric Scene Briefs

Device semiotic tiers and arc roles map directly to scene parameters: a peaks-tier device with arc_role "peaks" signals Act 3 climax density. A designer seeds the world with data, not guesswork.

Output Type B

Narrative Arc Scaffolding

The introduced/developed/peaks arc structure translates into act-based level progression. Chapter 1 devices are introduction nodes. Chapter 9 devices are peak nodes. The game's dramatic structure mirrors the novel's verified arc.

Explore the source data in the API Explorer →