/srv/abyss-stack— active deployed runtime root/abyss— optional mounted vault for heavy data
See also: PATHS for the distinction between source checkout paths and deployed runtime paths.
Expected live structure under /srv/abyss-stack:
/srv/abyss-stack/
Configs/
Secrets/
Services/
Models/
Knowledge/
federation/
Logs/
diagnostics/
eval-exports/
host-facts/
memo-exports/
rpg/
tos-graph/
platform-adaptations/
runtime-benchmarks/
.codex-home/
generated/rpg/— source-managed public-safe RPG transport collections for SDK loading, review, and runtime parity checksConfigs/— deployed stack repo material such as compose modules, profiles, scripts, docs, config templates, and runtime config files bootstrapped from those templatesSecrets/— real env files, API keys, and secret-bearing runtime materialServices/— persistent state for databases and runtime services, plus source-seeded build contexts and service-local inputs for lightweight helper services such aslangchain-api,litellm,docs-api,route-api,tos-graph,qwen3-tts-api, andtts_routerModels/— local model weights and related serving artifactsKnowledge/— local knowledge corpora, helper inputs, and runtime-local mirrors of public-safe federation surfaces such asKnowledge/federation/aoa-agents/,Knowledge/federation/aoa-routing/,Knowledge/federation/aoa-memo/,Knowledge/federation/aoa-evals/,Knowledge/federation/aoa-playbooks/,Knowledge/federation/aoa-kag/, and the source-owned companionKnowledge/federation/tos-source/Logs/— logs and generated runtime artifacts, including diagnostic spine sessions, diagnosis companions, reviewed diagnosis refs, repair handoffs, andlast_goodanchors underLogs/diagnostics/, local private host-facts captures underLogs/host-facts/, memo export candidates underLogs/memo-exports/, eval export candidates underLogs/eval-exports/, RPG runtime copies underLogs/rpg/, ToS graph helper artifacts underLogs/tos-graph/, platform-adaptation records underLogs/platform-adaptations/, and runtime benchmark artifacts underLogs/runtime-benchmarks/.codex-home/— isolated agent or codex-style runtime home
/abyss must not be assumed to exist just because it exists in the architecture.
Before heavy operations, check whether it is actually mounted.
Recommended checks:
findmnt /abyss
ls -la /abyss | headIf /abyss is not mounted, heavy writes may spill onto the system disk.
Not every runtime subtree is source-managed yet.
Current intentional seam:
Services/aoa-browser/ms-playwright/remains runtime-only browser payload- the
aoa-browserservice now uses a source-managed build context, but its browser payload remains machine-local runtime state
Never commit or publish real runtime material from:
/srv/abyss-stack/Secrets- live
stack.env - any secret-bearing mounted file used by services
- private host-facts captures under
/srv/abyss-stack/Logs/host-facts/ - diagnostic spine artifacts under
/srv/abyss-stack/Logs/diagnostics/ - private memo export candidates under
/srv/abyss-stack/Logs/memo-exports/ - private eval export candidates under
/srv/abyss-stack/Logs/eval-exports/ - public-safe RPG runtime copies under
/srv/abyss-stack/Logs/rpg/ - private platform-adaptation captures under
/srv/abyss-stack/Logs/platform-adaptations/