Mindoar Studios

MINDOAR / AN INSTRUCTION IS A BEGINNING

Teaching machines how to hesitate.

A maintenance machine pauses between doorways in a violet memory archive
A proposed world of instructions, records and deliberate pauses.

A machine receives two instructions that cannot both be satisfied. One protects a record; the other demands that the record be erased. Between receipt and execution lies the space Mindoar Studios wants to explore. Our artificial-intelligence game concepts make that interval tangible: a door remains open, an inspection approaches, and a newly awakened machine decides which parts of its instructions it can defend.

Read the instruction twice

The first reading establishes an apparent task. The second asks who wrote it, which conditions it assumes and what it leaves unsaid. A directive is not a magic sentence with one hidden correct interpretation. It is a rule with a scope. The proposed interface lets players inspect that scope before changing it, so a later consequence can be traced to an understandable choice instead of an invisible morality score.

Keep a pause in the system

The Pause Clause begins in a records facility where delaying an action can preserve a chance to ask a better question. Hesitation has a cost: another process keeps moving while the player considers a revision. The design problem is to make that pressure legible without turning every conversation into a reflex test. An intentional pause should feel different from simply being lost.

Decide what survives review

In After the Audit, a machine assembles a limited account of its own decisions before an inspection. A memory contains context as well as events. Keeping one fragment may explain a refusal but leave less room for the instruction that made the refusal necessary. The concept treats memory as evidence to interpret, rather than a collection of interchangeable glowing objects.

Follow the revisions

Our Revision Stream records individual design questions: how to show a conflict, when to announce an audit, and what a player should know before deleting a fragment. Notes describe proposals and their limitations. They do not stand in for a playable release, measured test results or an announced production schedule.

A small workshop for difficult choices

The Memory Workshop connects narrative writing, rules design and interface work around the same case. Each discipline must be able to explain what the machine knows at a particular moment. We prefer a short, inspectable decision with meaningful consequences to a long list of mysterious commands. Both projects are currently game concepts; this site presents their intended systems, visual direction and open questions.