Research methods
Designing a CPU-first AI research portfolio
CPU-first AI research needs questions that fit real memory, runtime, and evaluation constraints.
- Substantive answers preserved
- 27
- Independent respondents + supplied contribution
- 7 + 1
- Experiments started by the collection
- 0
The question
What substantive AI experiments are feasible on CPU/system RAM with locked independent evaluation?
How the work was approached
Seven independently queried providers plus Jim's separate shared ChatGPT contribution; preserved catalogs, proposed protocols, corrections and source checks.
What the record shows
Produced candidate studies in quantization, speculative decoding, CPU/NUMA placement, protected coding repair and evidence-memory systems, with explicit implementation and evaluation gates.
What remains unresolved
Provider catalog sizes are not a deduplicated experiment total. Protocols and suggested funding are proposals; no inference, benchmark, grant submission, runner or model change started. Current R640 inventory remained unverified.
What we are trying to achieve
The aim is to find where CPU and system-memory AI can do useful, dependable work at a practical cost. The portfolio turns that ambition into candidate studies with resource limits and independent evaluation. Selecting and running those studies is a later stage.
Sources & reading notes
- CHECKPOINT.mdAssignment / Current State / Next Action Retained project record Source record retained privately.
- collection_integrity.jsonSubstantive counts and experiments_started Retained project record Source record retained privately.
- consolidated_report.mdProvider Starting Portfolios / Corrections That Matter Retained project record Source record retained privately.
This is a dated, source-based research account, not a live machine report. Historical results, engineering preparation, research designs, open review gates, and measured pilots remain distinct.
