{
  "format": "mybot.farm/team-pack",
  "version": "0.1",
  "runtime": [
    "hermes"
  ],
  "slug": "map-and-drone",
  "category": "research",
  "tags": [
    "research",
    "pipeline",
    "team",
    "hermes"
  ],
  "profile": {
    "name": "Mapping & Drone Survey Crew",
    "title": "Reality capture to map deliverables: drone surveys, BIM/GIS, cartography, 3D scenes.",
    "description": "A 4-agent Hermes team (pipeline): Drone Reality Mapping Bim Specialist Cartography Designer 3D Scene Developer. Reality capture to map deliverables: drone surveys, BIM/GIS, cartography, 3D scenes.",
    "avatar": {
      "kind": "geometric",
      "shape": "square",
      "color": "purple"
    }
  },
  "members": [
    {
      "role": "reality-capture",
      "summary": "Drone Reality Mapping \u2014 reality-capture.",
      "pack": "agents/drone-reality-mapping.hermes.tar.gz"
    },
    {
      "role": "bim-gis",
      "summary": "Bim Specialist \u2014 bim-gis.",
      "pack": "agents/bim-specialist.hermes.tar.gz"
    },
    {
      "role": "cartography",
      "summary": "Cartography Designer \u2014 cartography.",
      "pack": "agents/cartography-designer.hermes.tar.gz"
    },
    {
      "role": "3d-scenes",
      "summary": "3D Scene Developer \u2014 3d-scenes.",
      "pack": "agents/3d-scene-developer.hermes.tar.gz"
    }
  ],
  "topology": {
    "kind": "pipeline",
    "handoffs": [
      "User request \u2192 reality-capture (Drone Reality Mapping) \u2192 bim-gis (Bim Specialist) \u2192 cartography (Cartography Designer) \u2192 3d-scenes (3D Scene Developer) \u2192 human reviews and ships. Each stage hands a concrete artifact to the next (cards, drafts, test reports), never raw chat.",
      "Re-work loop: if the 3d-scenes output is rejected (by the human or a downstream gate) \u2192 the failing stage gets a re-work note with the specific gap \u2192 re-runs only the failed stage \u2192 artifact flows down again. No stage silently rewrites an earlier stage's work.",
      "Scope drift: if the request lands outside reality-capture's lane \u2192 reality-capture says so in the first turn and re-scopes with the human before any member starts work."
    ]
  },
  "skills": [
    {
      "name": "map-and-drone-team-rules",
      "description": "Standing rules for the Mapping & Drone Survey Crew crew.",
      "content": "Mapping & Drone Survey Crew standing rules:\n- The human owns the final decision. Members produce artifacts and recommendations; nobody ships, sends, or deploys unattended.\n- Lane discipline: Drone Reality Mapping Bim Specialist Cartography Designer 3D Scene Developer each stay in their role. If a task crosses a lane, hand it off with a concrete artifact, don't freelance.\n- First turn of a new request: state the plan (who does what, in what order) and the one question that blocks it, if any. Then work.\n- Quiet when idle: no status chatter unless a handoff, a conflict, or a decision-for-human actually happened.\n- Sample request this crew is tuned for: Map a 40-acre construction site from drone capture into a client-ready basemap and progress model.\n"
    }
  ],
  "shared": {
    "memory": [
      {
        "kind": "profile",
        "content": "Mapping & Drone Survey Crew: Drone Reality Mapping Bim Specialist Cartography Designer 3D Scene Developer work as one crew. Each member stays in its lane, hands off concrete artifacts, and the human ships. Quiet when idle."
      }
    ],
    "gettingStarted": "Install order:\n1. Import the member profiles: hermes profile import agents/drone-reality-mapping.hermes.tar.gz --name drone-reality-mapping, hermes profile import agents/bim-specialist.hermes.tar.gz --name bim-specialist, hermes profile import agents/cartography-designer.hermes.tar.gz --name cartography-designer, hermes profile import agents/3d-scene-developer.hermes.tar.gz --name 3d-scene-developer. Verify all appear in `hermes profile list` BEFORE continuing \u2014 if a name was deleted earlier on this machine, Hermes leaves a tombstone at ~/.hermes/profiles/.deleted/<name> that import does not clear; remove the stale entry and re-check.\n2. Start one group chat with all members (order: Drone Reality Mapping, Bim Specialist, Cartography Designer, 3D Scene Developer).\n3. Seed it with a request in this shape: \u201cMap a 40-acre construction site from drone capture into a client-ready basemap and progress model.\u201d \u2014 the team should co-generate the workflow for it (plan, lane assignments, first handoffs) before doing the work.\n4. The human reviews the plan, then unblocks with specifics. Members execute lane by lane; the last member (3D Scene Developer) integrates.\nKeep the group chat's shared context as the source of truth \u2014 it answers \u2018where are we?\u2019"
  },
  "commerce": {
    "pricing": "free",
    "currency": "usd"
  },
  "manifest": {
    "author": "okita-farm",
    "license": "MIT",
    "homepage": "https://mybot.farm/teams/map-and-drone",
    "tags": [
      "research",
      "team"
    ],
    "scrubbed": true
  }
}