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, and infra glue. It does not own the authored meaning of the specialized AoA layers.

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
• security, runbook, backup, and restore posture
• infra 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

Relationship to the ecosystem

• Agents-of-Abyss is the ecosystem center.
• Tree-of-Sophia is the knowledge architecture counterpart.
• aoa-* repositories own their specialized meaning.
• abyss-stack owns the body those layers can run on.

Start here

1. Read CHARTER.
2. Read BOUNDARIES.
3. Read docs/ARCHITECTURE.
4. Read docs/SERVICE_CATALOG.
5. Read docs/PROFILES.
6. Read docs/PROFILE_RECIPES.
7. Read docs/RENDER_TRUTH.
8. Read docs/INTERNAL_PROBES.
9. Read docs/PATHS.
10. Read docs/STORAGE_LAYOUT.
11. Read docs/DEPLOYMENT.
12. Read docs/FIRST_RUN.
13. Read docs/DOCTOR.
14. Read docs/SECRETS_BOOTSTRAP.
15. Read docs/LIFECYCLE.
16. Read docs/MIGRATION_FROM_OLD.

For the shortest next route by intent:

• if you need the ecosystem center, layer map, or federation rules, go to Agents-of-Abyss
• if you need the knowledge world and authored architecture, go to Tree-of-Sophia
• if you need reusable practice, go to aoa-techniques
• if you need bounded execution workflows, go to aoa-skills
• if you need portable proof surfaces, go to aoa-evals

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-skills	bounded agent-facing execution workflows	you need executable workflows rather than deployment posture
aoa-evals	portable proof surfaces for bounded claims	you need evaluation and quality checks rather than runtime services

Repository shape

abyss-stack/
├─ README.md
├─ CHARTER.md
├─ BOUNDARIES.md
├─ ROADMAP.md
├─ AGENTS.md
├─ docs/
├─ compose/
├─ config-templates/
├─ scripts/
├─ systemd/
├─ env/
└─ .github/

Module layout

The stack is organized around explicit compose modules rather than one swollen file:

• 10-storage.yml
• 20-orchestration.yml
• 30-local-inference.yml
• 31-intel-inference.yml
• 40-llm-gateway.yml
• 41-agent-api.yml
• 42-agent-api-intel.yml
• 50-speech.yml
• 51-browser-tools.yml
• 60-monitoring.yml

Lifecycle surfaces

The repository now includes:

• profile files under compose/profiles/
• deployment helpers under scripts/
• config-template bootstrap helpers under scripts/
• first-run and profile-introspection helpers under scripts/
• host-doctor and bootstrap-rehearsal support
• profile endpoint recipes and endpoint introspection helpers
• internal-only probe helpers for hidden services
• render-truth helpers for actual composed runtime output
• human-facing wrappers under scripts/
• a systemd user unit skeleton under systemd/user/
• a repository validation workflow under .github/workflows/

Current status

The bootstrap skeleton is in place, the first real services have been migrated from abyss-stack_old, and the first profile-aware scripts and unit scaffolding now exist. The current hardening pass adds render-truth helpers so the effective composed runtime can be inspected directly, not just described narratively.

License

Apache-2.0