FROM THE TEAM 237 ARCHIVE
Originally published on 12.03.2026
RECOVERING A PROJECT WE DID NOT BEGIN
By Mateo Ferro — Technical Engineering and Production
There is a reassuring fiction behind most development histories: a project begins with a clear intention, advances through identifiable stages and eventually reaches a version that can be called finished. Project Spooky did not reach us in that form.
The first build opened by the external developer was not a stable starting point. Some scenes worked in isolation. Others depended on systems that were absent, incomplete or no longer connected to the rest of the project. The folders contained executable builds, duplicated assets, notebooks and reports, but they did not constitute a single authoritative version. We therefore began by separating three layers.
The first contained what Álvaro had demonstrably completed: interactions and sequences that could be reproduced without interpreting his intentions. The second contained what he had indicated through notes, diagrams or unfinished implementations. The third contained what we could only infer from the relationship between those materials.
These layers still guide every intervention. When we restore a broken interaction, we record what was present, what was changed and why. When several solutions appear plausible, we do not quietly choose one and present it as Álvaro’s. Reconstruction requires decisions, but it also requires leaving those decisions visible.
This has practical consequences in the public demo. Some uncertainties are technical: whether an interaction fails, a subtitle disappears or a sequence behaves differently on another machine. Others concern communication. A puzzle may operate according to a recoverable rule and still fail to make that rule perceptible to a new player.
That distinction matters to us. If someone cannot proceed, the answer is not automatically to simplify the underlying idea. It may be necessary to change the way the house signals that an object, number or repetition deserves attention. Preserving a design does not mean preserving every obstacle created by incomplete implementation.
This is why feedback on the demo forms part of the reconstruction rather than merely its promotion. Reports of confusion, hesitation and mistaken interpretation help us distinguish intentional uncertainty from information the surviving build does not communicate adequately.
After playing, was there a moment when you understood what the house was asking you to observe or a moment when you felt the game had not given you enough information to understand it?
You can answer in the Steam discussions: https://steamcommunity.com/app/4712780/discussions/
The original Spanish archive entry remains preserved on the Team 237 website: https://team237.es
Play the free demo:
— Team 237
Investigate · Document · Recover