All apps

Narrative simulation prototype

Operator Confirmation

A simulation of how authority can transfer through reasonable decisions. Text, sound and interactive tasks run from modules the engine never names, and swapping them would change the subject rather than the machinery: at its core it is a scenario engine you feed configuration to, calibrated against a premise about how authority moves.

The question

What if a system became indispensable by being useful? That premise is the one argued in The Quiet Governor, and this is where it was calibrated rather than asserted: the engine was tuned until the pressure model produced the effect the essay describes. Operator Confirmation begins with a human reviewing a terminal’s recommendations. The terminal can be competent, persuasive, and operationally right. The question is what each authorization makes easier to accept next. There is no adversary character: the system presenting each situation, advising on it, and deciding what follows is the same system measuring whether the operator defers to it, and it biases what comes next according to how they have been deciding.

What I built

An engine that takes configuration rather than a program with content inside it. Scenarios, framing, locations, tasks and audio are all modules that register themselves; the core holds none of it, and contains no reference to any of the locations the shipped scenarios use. Thirty-one incidents, five interactive tasks and twelve audio tracks were added without the engine learning a single one of their names.

The output is not one medium. The same modules drive written briefings, procedurally generated score, and interactive tasks with their own test harness — one scenario definition, several channels. Generated speech and character portraits exist as sandboxes beside the engine rather than inside it: the speech channel expects an 82M-parameter voice model that is fetched from upstream rather than carried here. Its documented loop begins with an incident, moves through a recommendation and authorization, and carries immediate outcomes into later consequences.

The gameplay model distinguishes operational stability, human oversight, public trust, dependency, and urgency. Proposed responses range from denying a request to approving once, imposing constraints, or delegating wider authority. These are design mechanics, not claims about how real institutions inevitably behave.

Making the question playable

The recurring community of Isle of Harrow gives decisions a human reference point. The design asks that players notice a pattern across incidents rather than receive its meaning in an explanation. JJ, a recurring character, offers a perspective without becoming an answer key.

The repository snapshot contains 31 tracked incident modules, excluding the template. That is a source-content count; it does not establish how many incidents a player can reach in a run.

What would count as success

The prototype criteria ask whether players feel the difference between a good immediate outcome and a shift in authority. They also require the terminal to feel useful before threatening, and the recurring consequences to become recognizable through play.

Those criteria are the experiment’s question. No completed playtest result is claimed on this page. The game and The Quiet Governor approach related concerns through different forms: one asks a reader to consider an argument; the other asks a player to make decisions.