atlas-seedlisted

# Atlas seed — initial zone bootstrap from code **Goal:** turn a scaffolded vault into a usable map after `atlas init`, without lying about verification. This is the **first pass**, not recollection. Cards stay honest: | Field | Required value | |-------|----------------| | `status` | `seeded` | | `verifiedAt` | `unverified` | | `type` | `zone` | Never promote to `active` or stamp a SHA in this skill. Only a later human (or explicit `atlas stamp` after review) does that. ## When to run - Vault exists (`map/zones/` empty or only stubs) - `atlas status` shows `0 zones` (or 1–2 toy cards) - After `atlas-fleet ensure-all` / `atlas init` on a new repo - Re-seed only if the old seed was wrong *and* still `seeded` / never verified Do **not** run as a substitute for `atlas-recollection` after product work — that skill updates touched zones; this one creates the first partition. ## Inputs to read (order) 1. Repo `README.md` / `AGENTS.md` / `package.json` (or Cargo.toml / pyproject) — thesis 2. Top-level tree (`ls`, not whole monorepo dump) 3. Entry surfaces: `bin/`, `src/`, `lib/`, `packages/`, `app/`, `cli/` 4. Tests / CI if present — good `enforcedBy` candidates later 5. Existing vault `map/overview.md` if any Skip: `node_modules`, `dist`, `.git`, huge generated assets. ## How to partition (4–8 zones) Prefer **coherent ownership** over fine-grained files: | Typical zone | Owns (examples) | |--------------|-----------------| | `core` / `engine` | main lib, domain logic |