Chapter 3 · 3 of 6

A worked autopsy — a Director piece, taken blind

One real run, kept anonymous. A work built in Macromedia Director — the multimedia authoring tool behind much of the CD-ROM era — arrived as a 2.4 MB Mac archive with no documentation. The mechanical pass fixed the substrate and named exactly what it could not resolve; the AI analyst opened the work up and found the dead dependency nothing in the files announced. This is the whole argument in miniature.

Abstract claims are cheap; here is one actual run. A Macromedia Director piece was handed to the tool as a single Mac StuffIt archive — a compression format common on 1990s Macs — 2.4 MB, taken as found, no accompanying notes. The tool was given nothing but the archive. Everything below is what it reported back. The work is kept anonymous; what matters is what the autopsy found, not whose piece it was.

What the deterministic pass established

Unpacking yielded three components: an entry-point application (the program that starts the work), a Director cast file (.dcr — the work’s media and scripts), and a resource fork (.rsrc — the hidden second half a classic-Mac file keeps its structured data in). Format identification recognised the classic-Mac AppleDouble carrier — the format that preserves those two halves when a Mac file travels through non-Mac systems — and typed the entry point as a classic Mac application: deterministic, high confidence. From that alone the substrate was fixed:

Base machine

Mac OS 9.

Runtimes

Classic Mac OS + Director / Shockwave.

Network

A Director net-Lingo capability — Lingo is Director’s scripting language, net-Lingo its network commands — with eight places in the code that perform network operations, but the destination reported honestly as “computed at run time — not statically resolved.”

The static pass did not guess and did not stay silent. It named the gap and flagged the next move: decompile with ProjectorRays — an open-source Director decompiler — for the full computed paths.

What the analyst added

The AI analyst took that lead, decompiled the compressed (afterburned, in Director’s terms) cast, and read the net-Lingo calls. The eight sites resolved to a small set of real endpoints: the plugin-era download.macromedia.com and fpdownload.macromedia.com, and — the one that matters — the work’s own back-end on a university server, reached through getNetText / gotoNetPage. The verdict is the whole point: if that server is unreachable, the work breaks. All three hosts are long dead.

The fidelity risks it flagged

The autopsy also named the identity-defining risks a curator must respect — the difference between “it launches” and “it is the work”:

Pacing

It runs too fast on a modern CPU — the pacing was authored into period hardware timing.

Stage

The fixed-pixel stage must not be rescaled.

Colour

The black-and-white dithering is tuned for a CRT monitor.

The argument in miniature Nothing in the work’s files announced that it phones home to a university server that stopped answering years ago — the dependency lived inside compiled Lingo, as an address assembled at run time. Only opening the work up surfaced it. And surfacing it is exactly what turns a dead bundle into a conservable one: name the dead host, ask the Wayback Machine what it once served, and have it ready to replay before first run, so the piece has a chance of running again.