abyss-stack

abyss-stack is the infrastructure substrate of the AoA and ToS ecosystem. It is Fedora-first in deployment posture while remaining Windows-usable for source work, path mapping, and hybrid workflows. It owns runtime, deployment, storage layout, lifecycle, security, reference-platform posture, and infrastructure glue. It does not own the authored meaning of the specialized AoA layers or ToS.

Start here

Read in this order:

1. CHARTER
2. BOUNDARIES
3. docs/ARCHITECTURE
4. docs/SERVICE_CATALOG
5. docs/PROFILES and docs/PRESETS
6. docs/PATHS
7. docs/DEPLOYMENT, docs/FIRST_RUN, docs/RUNBOOK, and docs/SECURITY
8. ROADMAP

Then branch by need:

• Windows host and WSL bridge: docs/WINDOWS_BRIDGE, docs/WINDOWS_SETUP, docs/WINDOWS_PERFORMANCE
• host posture and machine facts: docs/REFERENCE_PLATFORM, docs/REFERENCE_PLATFORM_SPEC, docs/MACHINE_FIT_POLICY, docs/PLATFORM_ADAPTATION_POLICY
• runtime benchmark and local-model posture: docs/RUNTIME_BENCH_POLICY, docs/LLAMACPP_PILOT, docs/LOCAL_AI_TRIALS, docs/MODEL_PROFILES, docs/CONTEXT_BUDGET_POLICY
• branch and recurrence posture: docs/BRANCH_POLICY, docs/RECURRENCE_RUNTIME_POLICY
• runtime-side AoA seams: docs/MEMO_RUNTIME_SEAM, docs/EVAL_RUNTIME_SEAM, docs/PLAYBOOK_RUNTIME_SEAM, docs/KAG_RUNTIME_SEAM

What this repository is for

This repository is the right home for:

• local and hybrid runtime topology
• rootless Podman and systemd user orchestration
• storage and mount contracts
• service modules and deployment profiles
• versioned helper-service build contexts
• security, runbook, backup, and restore posture
• normative host posture and machine-readable host-facts contracts
• current-machine fit policy and bounded machine-local tuning guidance
• platform-adaptation policy and public-safe/private tuning record contracts
• infrastructure helper services that support AoA and ToS

What this repository is not for

This repository should not absorb:

• technique canon
• skill canon
• eval canon
• routing truth as such
• memo objects as primary truth
• agent role contracts as primary truth
• playbook meaning as primary truth
• ToS authored corpus and philosophical source material
• AoA constitutional truth

Quick path rule

• source checkout: ~/src/abyss-stack by default, or ${AOA_SOURCE_ROOT} if intentionally relocated
• deployed runtime root: /srv/abyss-stack
• deployed config tree: /srv/abyss-stack/Configs
• do not edit /srv/abyss-stack as if it were the source repository

The deployed runtime mirror under /srv/abyss-stack/Configs is intentionally narrower than the source checkout.

Quick route table

repository	owns	go here when
abyss-stack	runtime, deployment, storage, lifecycle, and infra glue	you need the body the system runs on
Agents-of-Abyss	ecosystem identity, layer map, federation rules, program-level direction	you need the center and the constitutional view of AoA
Tree-of-Sophia	living knowledge architecture for philosophy and world thought	you need the knowledge world rather than the runtime body
aoa-techniques	reusable engineering practice	you need durable techniques rather than infrastructure modules
aoa-kag	derived retrieval, reasoning-handoff, and regrounding packs	you need KAG-side advisory retrieval surfaces rather than live runtime services
aoa-skills	bounded agent-facing execution workflows	you need executable workflows rather than deployment posture
aoa-memo	memory objects, recall contracts, and memo-side writeback meaning	you need memory-layer authority rather than runtime export plumbing
aoa-evals	portable proof surfaces for bounded claims	you need evaluation and quality checks rather than runtime services
aoa-playbooks	playbook doctrine, authored execution bundles, and playbook-owned meaning	you need playbook authority rather than runtime advisory mirrors

Current posture

abyss-stack is a live multi-service runtime with stateful storage, local and Intel-aware inference paths, monitoring, host-facts capture, machine-fit capture, platform-adaptation logging, and landed federation advisory seams for sibling AoA repositories.

The current bounded local-worker posture is llama.cpp-first on 5403, with Ollama retained on 5401 as the control and rollback path. LangGraph is the adopted execution layer for bounded long-horizon and autonomy-focused local-worker flows. Federation seams remain bounded and explicit: they can enrich runtime behavior, but they do not replace source-owned meaning.