HelloStranger

From Definitions to a Playable Prologue

The first implementation sequence turned a broad design corpus into one narrow, playable path.

The project established strict runtime content types, an authored JSON schema, a deterministic compiler, generated bundle validation, immutable runtime loading, and a situation engine before adding the learner-facing SwiftUI presentation.

That ordering made content, state, and presentation separate authorities. Dialogue and assistance live in authored files. The compiler produces stable runtime documents. The engine accepts typed actions and emits deterministic transitions. The app decides how those values appear without duplicating the story rules.

By 30 July, the app could present two Prologue situations in text mode. A player could meet Luz, respond to Hola, ask for increasingly direct help, provide a bounded display name, correct or confirm it, and reach an explicit end of the available Prologue.

It was a small slice, but it established a durable principle: the story can remain authored while the mechanics around interpretation, assistance, and presentation evolve independently.

← Back to HelloStranger