shipkit-architecture-map

# shipkit-architecture-map — Living Architecture Map **Purpose**: Maintain `.shipkit/architecture-map.json` — a continuously-refreshable, code-derived answer to *"what does the system currently look like?"* (applications, datastores, contracts, integrations). It is the **what-is** map. **This is distinct from `.shipkit/architecture.json`**, which is the **why** — the append-only decisions log. This skill never reads or writes `architecture.json`; the two artefacts coexist (decisions vs current-state). --- ## When to Invoke **User triggers**: - "Map the architecture" - "What does the system currently look like?" - "Refresh the architecture map" - "Show me applications / datastores / contracts / integrations" **Auto-suggested when**: - No `.shipkit/architecture-map.json` exists and the repo has real source code - The existing map is older than **14 days** (staleness) - A major structural change landed (new service, new datastore, new external integration) --- ## What This Map Contains | Section | What it captures | ID prefix | |---------|------------------|-----------| | `applications` | Deployable/runnable units: services, frontends, workers, CLIs, libraries | `APP-NNN` | | `datastores` | Persistence: postgres, redis, s3, sqlite, mongo, etc. | `DS-NNN` | | `contracts` | Interface/data shapes at boundaries: REST/GraphQL routes, events, RPC, shared types | `CON-NNN` | | `integrations` | External systems: third-party APIs, webhooks, queues, SaaS | `INT-NNN` | IDs are **...