Skip to content

REFERENCE_PLATFORM.md

Latest commit

 

History

History
88 lines (64 loc) · 3.36 KB

REFERENCE_PLATFORM.md

File metadata and controls

88 lines (64 loc) · 3.36 KB

REFERENCE PLATFORM

Reference operating posture

  • Fedora 43
  • rootless Podman
  • systemd user units
  • /srv/abyss-stack as the canonical runtime root
  • /abyss as an optional mounted vault for heavy data

This file versus host facts

This file is normative. It names the intended operating posture.

Observed machine facts belong to the machine-readable host-facts layer described in REFERENCE_PLATFORM_SPEC. The current-host runtime choice belongs to MACHINE_FIT_POLICY.

Recommended local review flow:

scripts/aoa-host-facts --mode public --write /tmp/reference-host.public.review.json
scripts/aoa-host-facts --mode private --write "${AOA_STACK_ROOT}/Logs/host-facts/latest.private.json"
scripts/aoa-machine-fit --mode private --write "${AOA_STACK_ROOT}/Logs/machine-fit/latest/latest.private.json"

The repository may carry a reviewed canonical public snapshot at docs/reference-platform/reference-host.public.json. Refresh that file intentionally when you are updating the chosen canonical Linux reference host, not during routine local captures.

aoa-doctor stays focused on readiness. It is not the durable inventory surface. aoa-machine-fit is the bounded surface that says what this concrete machine should currently prefer.

Fedora-first means

The primary operational target is Fedora. That is where:

  • path defaults are anchored
  • SELinux-aware volume posture is assumed
  • rootless Podman is treated as canonical
  • systemd user units are part of the normal lifecycle model

Windows-usable means

Windows is supported as a source and workflow environment, not as the canonical native runtime target for the current compose surface.

Recommended Windows shape:

  • source checkout on Windows host wherever convenient
  • runtime deployment inside WSL2 or a Linux-oriented Podman machine
  • canonical runtime root inside that Linux layer remains /srv/abyss-stack
  • optional host vault path may be mapped into the Linux runtime as /abyss

Why this matters

The stack is not just a pile of services. It is shaped around:

  • local-first operation
  • recoverable lifecycle control
  • explicit storage layout
  • minimal host exposure

Runtime assumptions

  • podman is the default container runtime
  • compose-compatible workflows are expected
  • systemd user services are the canonical lifecycle surface
  • external heavy data should be treated as optional mounts, not invisible assumptions

Minimum practical expectations

  • modern multi-core CPU
  • 32 GB RAM preferred
  • fast SSD or NVMe for active state
  • enough free headroom for models, service state, and logs

Operational principle

The stack should not pretend that every machine deserves the same runtime posture. Once the normative posture is satisfied, the next step is to fit the runtime to the actual host:

  • prefer the strongest validated preset the host can support
  • preserve the driver and package freshness state that shaped that decision
  • refresh the machine-fit record when the host drifts

Known user-specific fit

This repository is intentionally aligned with:

  • rootless Podman rather than Docker
  • a local AI stack rooted under /srv/abyss-stack
  • an Intel-aware branch of the inference surface
  • a current reviewed llama.cpp-first text default on the Intel Core Ultra 9 285H host, with broader Intel-serving lanes governed through machine-fit and reviewed rollout