application
20/20 resolved
0 unresolved critical facts.
protocol and run ledger
Mini PC Homelab Benchmark Ledger
Inspect the benchmark protocol, queued questions, accepted runs, and the honest current count of Grade-A Super Evil Robots measurements.
- record type
- hub
record at a glance
- accepted runs
- 0
- protocol records
- 3
- method-ready, unexecuted
- 3
- measured results
- 0
- critical facts resolved
- 60/70
- best attached evidence
- grade B
- accepted grade A runs
- 0
the current ledger is intentionally empty
A benchmark appears here only after the exact hardware and software manifests, frozen fixture and protocol hashes, repeated raw series, privacy review, and human approval all exist. The site currently has three predeclared, method-ready protocols and no accepted run.
0 Grade A runs · 0 accepted records.
No compatibility verdict may claim measured Super Evil Robots evidence from this ledger yet.
critical-fact readiness
The generated entity evidence-reference presence counter asks only whether each evaluated top-level entity has at least one reference. It is not consequential-fact coverage. This fact ledger currently resolves 60 of 70 separately declared facts. Its source-suitable coverage is 85.7%, and 14.3% remain unresolved. Gate G2 requires at least 90% source coverage and no more than 10% unresolved.
physical configuration
0/10 resolved
10 unresolved critical facts.
platform
20/20 resolved
0 unresolved critical facts.
workload
20/20 resolved
0 unresolved critical facts.
Modeled installed parts never count as observed physical facts. That is why all physical-configuration facts remain unresolved until hash-pinned, human-approved Grade A runs exist.
protocol queue
ready unexecuted · 1.0.0
physical mini-PC baseline protocol
Measure the baseline power, thermal, acoustic, boot, memory, network, failure, and recovery behavior required before workload-specific results are interpreted.
- measurement families
- 9
- planned repetitions
- 3
- result
- none accepted
ready unexecuted · 1.0.0
Jellyfin 1080p H.264 hardware-transcode protocol
Test whether one declared exact configuration can sustain one repeatable 1080p H.264 to 720p H.264 Jellyfin hardware transcode without thermal, playback, or operational failure.
- fixture
- selected-hash-pinned
- planned repetitions
- 3
- measurement window
- 30 minutes
- result
- none accepted for this protocol hash
ready unexecuted · 1.0.0
Home Assistant synthetic event and restart protocol
Test whether one declared exact configuration can sustain a deterministic synthetic event load and recover cleanly from a controlled Home Assistant restart.
- fixture
- selected-local-hash-pinned
- planned repetitions
- 3
- event load
- 30 minutes
- result
- none accepted
what a Grade A record must contain
- One exact specimen identity plus complete hardware and firmware manifests.
- Operating system, kernel, drivers, runtime, application, and configuration versions.
- A legally usable fixture with stable URL and SHA-256.
- A frozen protocol, raw artifacts, at least three repetitions, and disclosed failures.
- Median, range, variation, limitations, privacy review, and human approval.
receipts
7 sources · 0 accepted grade A runs · best evidence grade B · reviewed 2026-07-26
record identity, publication and review
- canonical path
- /benchmarks/
- publication
- preview · noindex
- reviewed
- 2026-07-26
- review again by
- 2026-08-25
evidence boundary
Grade A count: 0. A Grade B source can establish a documented specification or requirement. Grade D records are modeling inputs. Neither is proof of measured throughput, thermals, power, reliability, or physical fit.
8 attached evidence records
a grade describes how well attested a statement is, not how good the hardware is. grade a is a lab run we reproduced with a published method. grade d is a model, a reasoned inference, or a single unverified report.
- evidence grade b 7 records
- evidence grade d 1 record
evidence grade b · official sourcesupports
Jellyfin recommends 8 GB RAM, SSD storage for application data and transcode cache, wired gigabit networking, and properly configured hardware acceleration for transcoding.
evidence grade b · official sourcesupports
Jellyfin publishes an official Debian-based container image and documents 10.11 tags, but does not establish the pilot's additional KVM guest layer.
evidence grade b · official sourcesupports
Jellyfin 10.11 is a documented stable server release line and requires a 64-bit operating system on ARM.
4 further grade b records · official source
evidence grade b · official sourcesupports
Jellyfin says Intel 7th through 10th generation integrated graphics remain capable for existing owners, but are no longer recommended for a new purchase because Intel deprecated the relevant toolkit.
evidence grade b · official sourcesupports
The generic x86-64 Home Assistant OS image requires x86-64, UEFI boot, compatible storage, and a supported network adapter; Secure Boot must be disabled.
evidence grade b · official sourcesupports
Home Assistant documents a KVM/Proxmox QCOW2 deployment with minimum VM resources of 2 GB RAM and 2 vCPUs, requires UEFI, and directs KVM users to a non-Secure-Boot OVMF image. The example KVM command allocates 4 GB, while the guide says resources should be sized to the expected workload rather than asserting a universal higher recommendation.
evidence grade b · official sourcesupports
The official July 2026 release notes list Home Assistant Core patch release 2026.7.4.
1 further grade d record · modeled or inferred
evidence grade d · modeled or inferredsupports
Resource allocations in candidate recipes and the starter stack are planning budgets, not measured throughput or latency claims.
limitation: This is a modeled or inferred claim. It cannot establish measured performance.
source ledger
Official facts and first-party modeling are shown separately. Source prose, tables, and diagrams are not republished.
- 7 sources
- 6 with a public link
- 1 first party modeling policy
- 4 official application documentation
- 2 official release notes
first party modeling policy · 1 source
- Super Evil Robots Repositioning Master Plan
official application documentation · 4 sources
official release notes · 2 sources
record and source history
This projection is generated from homelab graph version 0.1.0. The generated lifecycle index exposes only history events that are explicitly present in the structured record. It does not invent an earlier revision when the graph contains only its creation baseline.
- — current preview record reviewed against the attached evidence set.
- — next required review under the monthly pilot-record review interval.
- This route does not map to one simple lifecycle entity. Inspect the generated index for its component records; no route-level revision is implied.
inspect the complete generated lifecycle and change-history index