one deliberately bounded stack

Candidate Homelab Stacks

Inspect the one intentionally bounded multi-app stack in the pilot and every assumption that prevents it from being called verified.

record type
hub

record at a glance

candidate stacks
1
verified stacks
0
primary deployment patterns
1
best attached evidence
grade B
accepted grade A runs
0

a stack is more than a list of applications

The stack record combines deployment topology, resource allocations, passthrough conditions, storage placement, recovery assumptions, and every workload recipe it contains. A mini PC can satisfy each application in isolation and still fail the combined plan.

The pilot maintains one stack. That narrow scope is intentional: it proves the model and review process before expanding the state space.

primary deployment pattern

Proxmox host with isolated appliance and application guests. The pilot's maintained topology for one exact mini PC: Proxmox VE on bare metal, Home Assistant OS in its own KVM virtual machine, and containerized applications inside a separate Debian KVM virtual machine. It is an architecture contract, not a performance or resilience result.

  1. virtualization host: The exact mini PC runs Proxmox VE directly; no nested host hypervisor is modeled.
  2. Home Assistant appliance guest: Home Assistant OS keeps its supported appliance environment inside a dedicated KVM virtual machine.
  3. container application guest: Jellyfin runs in Docker inside a separate Debian KVM virtual machine; device passthrough remains an explicit condition.

stack ledger

3 workloads · 12 combined checks

Home automation + media starter stack

Proxmox VE on bare metal, Home Assistant OS in a KVM VM, and Jellyfin in Docker inside a small Debian VM.

Combined prerequisite and allocation fit. It does not claim measured transcoding, VM latency, thermals, power, uptime, or backup integrity.

  • Proxmox VE 9.x
  • Home Assistant Core 2026.7.4
  • Jellyfin Server 10.11.x
inspect the combined fit model →

why this is not yet a verified stack

  • No exact physical machine has run the complete deployment.
  • No hostile-peak fixture has exercised the workloads together.
  • GPU passthrough, storage placement, backup, and recovery remain assumptions.
  • Power, thermal, acoustic, and sustained-load behavior remain unmeasured.

Verified stack count: 0. The stack can still be useful as a transparent planning model because its unknowns are first-class output.

receipts

4 sources · 0 accepted grade A runs · best evidence grade B · reviewed 2026-07-26

record identity, publication and review

canonical path
/stacks/
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.

4 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.

  1. evidence grade b · official sourcesupports

    For production, Proxmox VE documents Intel 64 or AMD64 with hardware virtualization, at least 2 GB for host services plus designated guest memory, fast redundant storage with SSDs preferred, and redundant multi-gigabit network interfaces. Its separate evaluation-only minimum is not a production recommendation.

    source: Proxmox VE Administration Guidechecked 2026-07-26claim: claim-proxmox-base-requirements

  2. 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.

    source: Home Assistant OS generic x86-64 board supportchecked 2026-07-26claim: claim-haos-generic-x86-requirements

  3. 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.

    source: Jellyfin hardware selection guidechecked 2026-07-26claim: claim-jellyfin-hardware-requirements

1 further grade d record · modeled or inferred
  1. evidence grade d · modeled or inferredsupports

    Resource allocations in candidate recipes and the starter stack are planning budgets, not measured throughput or latency claims.

    source: Super Evil Robots Repositioning Master Planchecked 2026-07-26claim: claim-ser-workload-budget-model

    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.

  • 4 sources
  • 3 with a public link
  • 1 first party modeling policy
  • 3 official application documentation
first party modeling policy · 1 source
  1. Super Evil Robots Repositioning Master PlanSuper Evil Robots · first party modeling policy · checked 2026-07-26 · docs/super-evil-robots-repositioning-plan.md
official application documentation · 3 sources
  1. Proxmox VE Administration GuideProxmox Server Solutions · official application documentation · checked 2026-07-26
  2. Home Assistant OS generic x86-64 board supportOpen Home Foundation · official application documentation · checked 2026-07-26
  3. Jellyfin hardware selection guideJellyfin Project · official application documentation · checked 2026-07-26

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.

  1. — current preview record reviewed against the attached evidence set.
  2. — next required review under the monthly pilot-record review interval.
  3. 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