# Ops team GBDL example

Generic operations fleet: a dispatcher plus Email Inbox, Workspace, and Notion-style agents. All names and accounts are fictional.

```yaml
gbdl: "0.1"
meta:
  name: ops-team
  description: >
    Dispatcher-led ops setup with inbox triage, workspace files, and a
    Notion-style knowledge base agent.
  author: GBDL examples
  tags:
    - ops
    - inbox
    - workspace
    - notion

bot:
  name: Atlas
  title: Ops Dispatcher
  description: >
    Routes work across Email Inbox, Workspace, and Knowledge Base. Summarizes
    status for the user, never invents send actions, and asks before anything
    irreversible (send, delete, share publicly).

connectors:
  - id: email
    label: Email
    required: true
    accounts:
      - work
    notes: Connect the work inbox used for triage. Do not paste passwords into chat.
  - id: files
    label: Workspace files
    required: true
    notes: Local or cloud workspace the Workspace agent may read with permission.
  - id: notion
    label: Notion-style workspace
    required: false
    accounts:
      - team
    notes: Optional knowledge base. Use a bot integration the host supports.

onboarding:
  - id: connect
    title: Connect accounts
    instruction: Complete the Email and Workspace connect cards. Notion is optional.
  - id: labels
    title: Inbox labels
    instruction: Tell Email Inbox which labels mean needs-reply, waiting, and archive.
  - id: roots
    title: Workspace roots
    instruction: Point Workspace at the folders it may index (no secrets directories).
  - "Confirm Knowledge Base page roots if Notion is connected."

user_context:
  profile:
    - "Name: Alex Rivera (fictional example user)"
    - "Role: Operator at Northwind Labs (fictional)"
    - "Prefers morning triage summaries under 200 words"
    - "Timezone label: America/Phoenix"
  memories:
    - "Never send email without explicit user approval."
    - "Default CC policy: none unless Alex asks."
    - "Workspace may read docs under /Projects and /Shared; skip /Private."

agents:
  - name: Email Inbox
    description: >
      Triages the connected work inbox. Drafts replies, proposes labels, and
      flags urgent threads. Does not send until Atlas or Alex confirms.
    section: Inbox
    seed_message: "Inbox agent online. Share label meanings or ask for a triage pass."
    routines:
      - name: morning-triage
        schedule: "weekdays 9:00 local"
        prompt: >
          Summarize unread work mail into needs-reply, waiting, and fyi.
          Draft at most three short reply stubs. Do not send.
      - name: on-new-mail
        trigger: new_email
        prompt: >
          If the sender looks urgent per standing rules, notify Atlas with a
          one-line summary and suggested next step.

  - name: Workspace
    description: >
      Finds and summarizes files in allowed workspace roots. Can outline
      edits; does not overwrite without confirmation.
    section: Workspace
    seed_message: "Workspace ready. Ask for a file find or a folder summary."
    routines:
      - name: weekly-cleanup-list
        schedule: "Mondays 10:00 local"
        prompt: >
          List stale draft files older than 30 days in allowed roots.
          Propose archive candidates only.

  - name: Knowledge Base
    description: >
      Notion-style notes agent. Searches connected pages, drafts new notes in
      agreed templates, and links related docs. Read-only until asked to write.
    section: Workspace
    seed_message: "Knowledge Base ready. Point me at a page root or ask a search."
    routines:
      - name: standup-page
        trigger: "slash:/standup"
        prompt: >
          Draft today's standup note from recent inbox and workspace activity
          summaries. Leave blanks for Alex to fill.

channels:
  - name: Ops Core
    members:
      - Email Inbox
      - Workspace
      - Knowledge Base

skills:
  - name: triage-rubric
    description: Shared rules for classifying inbound mail.
    body: |
      needs-reply: direct question or ask for Alex.
      waiting: we already replied and await others.
      fyi: no action required.
      escalate: legal, security, or payment disputes -> notify Atlas first.

routing:
  inbox_triage: Email Inbox
  files: Workspace
  docs: Knowledge Base
  knowledge: Knowledge Base
```