preservation lab // public signal
BucketComps recovers aging games into readable, verifiable, native builds. The public record stays honest: proof classes remain distinct, holds stay visible, and “playable” means gameplay with working save and load.
the cabinet
Each game gets its own public repository, voice, theme, and devlog. Shared machinery stays behind the curtain.
A clean-room native PC rebuild focused on two parallel tracks: a readable source recovery and a new graphics consumer. The finish line is verified playable gameplay with save and load—not a screenshot.
The 2003 game already has a native Windows release. A future effort would target maintainable source and modern cross-platform builds—not pretend to invent its first PC port.
status: source-recovery research queue
routing diagram
A small public surface is a feature. Private evidence never becomes a web root.
The cross-project map: mission, active cabinets, honest headline numbers, and public links.
Static project devlogs, methods, proof vocabulary, milestones, and game-specific visual identity.
Dynamic telemetry stays locally generated and separately hosted. Static sites link to it but never ingest it at build time.