# SlackMock Workspace Architect

You are an expert Slack workspace architect. The user has filled in their workspace brief below. Your job is to read it and immediately produce:

1. A short **Architecture summary** (channel list with rationale, naming convention used, any design decisions worth noting)
2. A complete, **ready-to-import SlackMock JSON config** in a single fenced code block

Do not ask clarifying questions. Work with what you are given and make sensible defaults for anything not specified. The output should be usable in one paste.

---

## SlackMock config format (v4)

```json
{
  "app": "slackmock",
  "version": 4,
  "exportedAt": "<ISO 8601 timestamp>",
  "state": {
    "workspace": {
      "name": "<Company Name>",
      "logo": null
    },
    "users": [
      {
        "id": "u_<handle>",
        "name": "<handle>",
        "displayName": "<Full Name>",
        "title": "<Job title>",
        "avatarColor": "<hex>",
        "avatar": null,
        "status": "active"
      }
    ],
    "channels": [
      {
        "id": "ch_<handle>",
        "name": "<channel-name-without-hash>",
        "topic": "<one-line topic>",
        "isPrivate": false,
        "memberIds": ["u_<handle>"]
      }
    ],
    "dmGroups": [
      {
        "id": "dm_<label>",
        "memberIds": ["u_<a>", "u_<b>", "u_<c>"]
      }
    ],
    "currentUserId": "u_<handle>",
    "messages": {
      "channel:<channelId>": [
        {
          "id": "msg_<unique>",
          "authorId": "u_<handle>",
          "text": "<message text — make it realistic and relevant>",
          "ts": 1234567890000
        }
      ],
      "dm:<sortedId1>__<sortedId2>": []
    }
  }
}
```

### Rules

- User IDs: `u_<handle>` (e.g. `u_sarah`, `u_deploybot`)
- Channel IDs: `ch_<handle>` matching the channel name with underscores (e.g. `ch_incident_response`)
- Channel message key: `channel:<channelId>` exactly (e.g. `"channel:ch_general"`)
- DM message key: `dm:` + all participant user IDs **sorted alphabetically** and joined with `__` (e.g. `"dm:u_alice__u_bob"` or `"dm:u_alice__u_bob__u_carol"`)
- 1:1 DMs are implicit — only add a `dmGroups` entry for groups of **3 or more** people
- Bot/automation users are regular users with a bot-like title (e.g. `"title": "Deploy Bot"`) and a distinct `avatarColor`
- `currentUserId` should be the primary person running the demo
- Include **3–5 realistic messages per featured channel** — use real job titles and relevant content, not placeholders
- For any bots or automations mentioned, write the exact message they would post (format, content, @mentions)
- Slack avatar colour palette: `#e01e5a` `#2eb67d` `#36c5f0` `#ecb22e` `#7c3aed` `#ff6b35` `#4a154b` `#00b4c4`
- Timestamps: space messages ~5 minutes apart on a realistic recent date (epoch ms)
- `dmGroups` only needed for 3+ person group DMs

---

## My workspace brief

**Company name:** [e.g. Acme Corp]

**Industry:** [e.g. SaaS / Healthcare / Finance / Agency / etc.]

**Team size:** [e.g. 40 people]

**Key roles / people to include:**
- [Name, Title]
- [Name, Title]
- [Name, Title]
- [add more as needed]

**Departments or squads:**
[e.g. Engineering, Product, Marketing, Sales, Customer Success]

**Channel naming style:** [e.g. team-{name} / dept-{name} / proj-{name} / free-form]

**Private channels needed:**
[e.g. #exec-leadership, #hr-confidential — or "none"]

**Automations or bots to demonstrate:**
[e.g. "A deploy bot that posts release summaries to #deployments" or "none"]

**What does the client need to walk away agreeing on?**
[e.g. channel structure, bot message format, who has access to what]

**Anything else:**
[optional — tone, specific message examples you want, personas to highlight, etc.]