itwo.
Admin
Narrative control layer

You don't watch the story.
You're in it.

Open-feeling conversation, closed narrative architecture.

The layer between the model and the messaging app — built to keep AI inside an authored story.

SMS · Case 01Live
Open feel · closed rails
Why now

The conversation got solved. The structure didn't.

Fluent modelsUbiquitous messagingAI-native audiencesIP hungry for interaction

Every input arrived at once. The layer is the missing piece.

Positioning

The structured middle.

Open chat

Loops, never ends.

Fixed narrative game

Rigid, app-bound.

itwo

Conversational and structured. The ending holds.

Architecture

Carrier in, engine out.

Signed in, orchestrated, authored out.

Player
SMS
Telephony
Twilio · MessageBird
/sms-webhook
signed POST
itwo engine
Pipeline
onboarding · GM · restart
LLM Client
pluggable
Repos
players · messages · metrics
Datastore
state · audit · cost
Outbound SMS
TwiML / API
Moat

Anyone can wire a carrier to an LLM. That isn't the product.

Nine coordinated systems sit between the model and the message. Four of them:

Story state & memory

What the player knows, missed, unlocked.

Character constraints

What each character can say, must hide, will refuse.

Clue logic & rails

Gates reveals; returns players from dead ends.

Pacing & resolution

Times tension; protects the authored ending.

Where this goes

When the credits roll, the story doesn't have to.

From one case to a category — the narrative control layer beneath conversational entertainment.

Contact

Talk to us about integrating itwo.

Reference implementation: an interactive mystery. The engine itself is genre-agnostic.

Email