memorb-conventionslisted

# Memorb Conventions (Single Source of Truth) > **This skill is the SSOT for memOrb's folder structure, filename formats, YAML schemas, and naming rules.** > Every write operation and every initialization (`/memorb-born`) must follow it. Workflows belong to the individual sub-skills; this file governs only *where things go and what shape they take*. > It assumes nothing about the name or existing layout of the user's vault — memOrb operates through the non-invasive `memorbs/` namespace and leaves everything else alone. ## Resolving VAULT Do not assume a fixed root folder name. The presence of `memorbs/HQ/identity.md` is what marks a vault as initialized: ```bash VAULT=$(find . -maxdepth 4 -type d -name memorbs 2>/dev/null -exec dirname {} \; | head -1) ``` If nothing is found, `/memorb-born` has not run yet — route there first. ## Folder structure **The one boundary rule: memOrb may read anything the user points it at, but it writes only inside `memorbs/`.** No exceptions; this binds extensions too. Reading is safe — no state change, no surprise. Conditional *writing* is where the trouble lives. The moment a skill says "write to the reference folder if it exists", the same operation produces three different outcomes depending on a coincidence of folder naming: it writes for one user, silently skips for the user who numbered their folders, and does nothing for the user who has none. That is worse than either owning the folder or never touching it. So memOrb grows exac