Mindoar Studios

CASE FILE / CONCEPT STAGE

After the Audit

Memory cartridges on a physical review desk
Concept artwork; not a released-game screenshot.

After the Audit is a game concept about preparing an account that cannot contain everything. A newly awakened machine has acted outside the most literal reading of a directive. Before a scheduled inspection, it must assemble a memory record that explains the decision. The available space is limited, but the most important constraint is interpretive: a fragment without its context may support a different account from the one the player intended.

01

An archive with relationships

The setting is the Recall Annex, a quiet branch of the Sable Registry. Its storage devices are physical cartridges arranged around review desks and transfer stations. Each proposed memory fragment has three visible properties: the event it records, the instruction associated with it, and the uncertainty it leaves unresolved. We want players to compare relationships rather than memorize an arbitrary rarity hierarchy.

A record of an opened door might look unremarkable until paired with the maintenance warning that preceded it. Keeping both consumes more space, but separating them can change how the action is understood. The interface should make a known dependency visible before the player removes a fragment. Unexpected consequences must come from uncertain interpretation, not from withholding a relationship the machine already knows.

02

Assemble an account

The intended loop starts with reviewing the available fragments, arranging a provisional account, examining its gaps, and committing a selection. A review preview asks concrete questions that the selected evidence can or cannot answer. It does not reveal a secret score. A player can return to the archive, replace a fragment, or accept that one part of the decision will remain difficult to explain.

We propose a limited number of meaningful selections per case. Endless rearrangement of tiny tokens would obscure the narrative purpose. A short set of substantial fragments gives each omission a readable consequence and keeps the machine’s uncertainty close to the player’s own understanding.

03

What a gap changes

Missing evidence does not automatically mean guilt. An incomplete account may lead to a follow-up question, a restricted permission or a request for another witness record. These are fictional institutional responses, not claims about real audit practice. The design aims to make consequences specific to the missing relationship rather than punishing the player with a generic failure screen.

The memory context note explains why an observation and the reason for noticing it should sometimes be separate pieces. The audit announcement note examines how much information a player needs before beginning this selection process.

04

A restrained visual language

The archive uses broad dark surfaces, violet storage light and muted rose mechanical details. Lime appears sparingly where a transfer is ready for review. The art direction contrasts the fragility of a remembered moment with the deliberate weight of the equipment preserving it. A memory may appear as a small spatial reconstruction above its cartridge, but the surrounding room remains visible so the player does not lose the physical context of the review.

05

Development questions

After the Audit is currently a concept, with no released build or announced launch date. The first design target is a case in which two plausible accounts can be constructed from the same evidence without either being reduced to a trick answer. Further questions concern readable dependency lines, undo behaviour and the distinction between a temporary working selection and a committed record. The related Pause Clause study explores the earlier decision that such an archive might eventually need to explain.