Research Dossier ID-05 · Candidate · Updated 22 October 2026
A compact workstation built around two memory pools and an open-source engine. The useful question is what that combination lets a person finish — with what accuracy, waiting time and maintenance. The architecture is interesting; its everyday value remains a testable proposition.
Two distinct memory pools connected over PCIe. Capacity can be stated as a total, but bandwidth and access costs stay different. On desktop, select a node to inspect its role.
Revision: engine openness confirmed; expected deliveries now differ by memory size; vendor results include the 495/192 GB configuration. The 5 October cart is retained as a historical snapshot. Sources and scope ↓
Plate M1 — two pools, separately accounted for
| Published specification | What to check | |
|---|---|---|
| 128/192 GB + 32 GB | → | Separate Ryzen unified memory and R9700 VRAM, with published bandwidths of 273 and 640 GB/s. A combined capacity figure does not describe one uniformly accessible VRAM pool. Product specifications ↗ |
| OPEN-SOURCE ENGINE | → | Apache 2.0 is confirmed in the public repository. The engine supports hardware beyond Lucebox. That establishes source access; it does not prove the ease or performance of the complete appliance. License ↗ |
| MODEL WORK ACROSS BOTH | → | The engine coordinates computation across the processors. Large-model profiles may include an SSD tier. Record the actual model, quantization, placement and context before comparing a result. Memory hierarchy report ↗ |
| BROWSER SETUP + LOCAL API | → | The documented route uses Chrome or Edge on desktop or Android, followed by local browser management. Test the path from setup to a completed task, including recovery after an interruption. Platform ↗ |
| 340 × 110 × 320 MM · 6 KG | → | Approximately twelve litres: a compact workstation. Evaluate carrying it between locations separately from using it on the move. Published dimensions ↗ |
| ~40 W IDLE · ~500 W LOAD | → | Manufacturer estimates. At a continuous 40 W, annual energy would be approximately 350 kWh; multiply by your own tariff. Measure idle and sustained work separately. The 1,000 W PSU rating is not measured wall consumption. |
| £5,999 / 128 GB · £7,999 / 192 GB | → | Published UK base configurations, before optional storage and clustering, with VAT, duty and delivery included. Expected delivery: January 2027 for 128 GB; February for 192 GB. The £2,000 memory premium needs a workload-based justification. Current FAQ ↗ |
| VENDOR PERFORMANCE RESULTS | → | The DeepSeek V4.1 report now includes 495/192 GB results, while its 128 GB figures use the earlier 395 build. Its Framework comparison changes engine, quantization and prefill method. These results guide a test; they do not isolate the effect of the extra GPU. Read the conditions ↗ |
Plate C2 — proposed experiments, not demonstrated product capabilities
Our research interest extends to local agents that can explain which facts and permissions support an action. More memory alone does not establish better reasoning. A useful experiment needs a defined workload, a correctness check and a baseline.
| Proposed object in memory | Question to test |
|---|---|
| Model weights and experts | For the same task and quality target, when does placement across devices improve completion time compared with the available single-device baseline? |
| Facts, roles and relations | Can a structured representation reduce repeated context processing while preserving every relevant constraint and exception? |
| Conclusions and dependencies | After revoking a mandate, can the system invalidate affected decisions promptly and explain why, without retaining stale permission? |
| Alternative planning states | Can it compare a small set of changed assumptions and return a checkable explanation of which actions remain permitted? |
Start with one supported engine profile on hardware already available. Record setup effort, manual interventions and one completed task. Test the Zero 495 appliance separately if access becomes available; another GPU cannot establish its unboxing experience. Supported targets and harnesses ↗
For a tiered-memory run, disclose model files, quantization, engine revision, placement, SSD use, context, cache state and concurrency. Report time to first token, task completion and correctness. Compare 128 and 192 GB only with those differences visible.
The README identifies PFlash as lossy prompt compression. Begin exact-retrieval and authority tests with it disabled; then compare any compressed mode on cases with buried exceptions and revoked mandates. A faster answer counts only if the relevant constraint survives. README guidance ↗
Plate M3 — workload questions across two pools and one engine
CAPABILITY MAP: questions grouped by workload. The equal-width marks are visual dividers, not benchmark scores. Read the evidence label on each row.
HISTORICAL SNAPSHOT · 5 OCTOBER CONFIGURATOR INCLUDED TAXES, DUTIES AND DELIVERY AND DISPLAYED A JANUARY ESTIMATE. NOT AN ORDER OR RECEIPT. CURRENT VENDOR ESTIMATE: JANUARY 2027 / 128 GB; FEBRUARY 2027 / 192 GB. THE £9,048 TOTAL INCLUDES OPTIONAL STORAGE AND CLUSTER KIT.
Plate O4 — proposed acceptance checks; no hands-on result claimed
Plate K5 — what the evidence can and cannot establish
Plate Y6 — filed with interest, promoted on evidence
You have a defined local-model workload that benefits from the proposed memory layout, can wait for the relevant delivery window, and value an integrated setup. Establish whether the 192 GB premium improves that workload enough to justify its cost.
You need a machine immediately, routine backpack portability, or a measured return that current evidence cannot establish. If the workload already fits your GPU, compare the completed task on that hardware before paying for a new system.
Does the owner finish useful work reliably, with little maintenance? Measure the path from setup through a completed task, update and recovery. A convincing result should disclose the exact configuration and include the failures encountered.
CLOSING — RESEARCH RULE №1 · PLATE F
We want to understand what heterogeneous hardware adds to a real workflow: faster completion,
more usable context, predictable recovery or better control over local data.
Our authority-and-evidence experiments are proposals. They need software, test cases and a baseline;
they are not capabilities established by a large memory specification.
The next step is a small, reproducible test whose result changes a practical decision.
Reviewed 22 October 2026 · primary sources
This is a document and source review. No Zero 495 was tested for this revision. Source availability confirms what is published; it does not independently validate performance claims. Product pages and delivery estimates can change.
The cart section is the author's 5 October 2026 snapshot, retained for historical context. Corrections change the assessment when the evidence changes.