Legacy Intel / OCLP
Older, constrained compatibility conditions.
Cleverfeets / Development Lab
Real hardware.
Real storage.
Real-world compatibility.
Cleverfeets is designed to understand digital estates built up over years or decades of computers, disks, backups and storage systems. Software trusted with that history needs to be tested against the real thing.
01 / The reason for the Lab
A clean, current development Mac tells only part of the story. Real digital estates span Intel and Apple silicon, different generations of macOS, removable storage, bridge hardware, network storage and migrations that do not always go to plan.
Software that understands old data needs to understand old computers.
COMPUTE × STORAGE ESTATE — compatibility is a matrix, not a benchmark.
Compute generations
The storage estate
02 / Current Lab
The Lab is organised by capability: the environments Cleverfeets can test today, and the ones still being added.
A capability is covered when the Lab has a suitable resource for it. Personal hardware can support development, but it does not replace dedicated Lab infrastructure.
Compute
Older, constrained compatibility conditions.
A distinct native x86_64 reference remains wanted.
A constrained M1 baseline remains wanted.
Modern Cleverfeets development can currently use a personal Apple-silicon Mac, but the Lab still lacks a dedicated system for this role.
Storage / Connectivity
Real media, enclosures and controller diversity.
Existing TrueNAS coverage and real SMB behaviour.
Bridges the past to systems customers retain.
Future public record
CF-MAC-001 · Legacy Intel ReferencePhysical equipment → documented Lab role.
Public asset records
Added as equipment is formally documented.
03 / Coverage gaps
The Lab tracks the capability first, then the hardware that can provide it.
Missing capability: Native late-generation Intel / x86_64 testing independent of legacy/OCLP conditions.
Why it matters: It separates genuine late-Intel behaviour from conditions specific to much older unsupported hardware.
Missing capability: First-generation M1 testing under constrained memory and performance conditions.
Why it matters: It exposes assumptions that current hardware can hide.
Current state: Modern Cleverfeets development still relies on a personal Apple-silicon Mac rather than dedicated Lab infrastructure.
Why it matters: A dedicated system provides a stable environment for Xcode, native builds, signing, sandbox qualification, sustained testing and current macOS compatibility—without tying the Lab to a personal computer.
04 / Programme taxonomy
Each Lab domain adds a different kind of real-world evidence to Cleverfeets testing.
Mac systems selected to fill specific compatibility, development and qualification roles.
Active procurementHDD, SSD, NVMe, DAS, docks, enclosures, removable media and controller diversity.
Active / expandingThunderbolt, FireWire, SATA, IDE/PATA and useful bridges.
ExpandingWrite protection, ESD safety, labelling and powered USB data hubs.
Active / expandingSMB authentication, permissions, discovery, disconnects and vendor behaviour.
Covered / lower priorityOptical, old USB, Zip/Jaz, floppy, IDE/PATA and unusual archival interfaces.
Opportunistic05 / Current procurement
The immediate priority is a dedicated current Apple-silicon development and qualification node. Late Intel and M1 reference systems remain important compatibility gaps, while storage and interface coverage continues to expand.
Stable modern development and qualification infrastructure.
A native x86_64 reference cell.
A constrained first-generation Apple silicon cell.
More storage and interface diversity.
The live wishlist carries the equipment currently being considered, along with current availability and pricing. This page explains the engineering role behind each requirement.
06 / Support
The wishlist carries the Lab's current equipment requirements, availability and live procurement options.
Old Macs, drives, adapters and unusual media can add useful coverage. A public hardware-donation route will be added when the intake process is ready.
07 / Stewardship
Every item should add a meaningful compatibility, development or qualification role.
Supporting the Lab does not buy control over Cleverfeets product decisions.
Older equipment can provide testing conditions that new hardware cannot.
Published Lab equipment should have a clear role.
Equipment stays in service while it continues to add useful coverage.
Public contributor recognition is optional.
08 / Accountability
As the Lab grows, its public record can show when equipment enters service, what role it fills, what testing it enables and what that testing changes.
Cleverfeets / Development Lab
They accumulate across machines, disks, backups, migrations and years. The Development Lab exists so Cleverfeets can meet more of that history before it asks anyone to trust it with theirs.