Skip to content

Scenario: MQ-9B Mission Block v0.2.0

This scenario illustrates how the Node Manifest mission block in schemaVersion 0.2.0 is used for a realistic Arctic patrol. It uses the manifest fixture examples/mq9b-mission.node-manifest.0.2.0.json and builds directly on the MQ-9B thread used in the envelope and tenancy scenarios.

In this schema line the mission block is descriptive. It records mission identity, a planned execution window, and a declarative region, while the envelope continues to determine whether the manifest is eligible. The mission block does not change selection; it provides context that later receipts and analyses can reference.

Context: Arctic maritime domain awareness

An RCAF MQ-9B-style remotely piloted aircraft identified as ca.rpas.mq9b-001 is tasked with a maritime domain awareness patrol in the eastern approaches of the Canadian Arctic. The sortie supports defence sovereignty, civil surveillance, and coast guard missions within a single flight window. The manifest describes the mission slice in time and space without prescribing tactics or sensor tasking.

The manifest

The manifest below extends the earlier MQ-9B example with a mission block and adds profile and contracts identifiers to make the compilation context explicit. It keeps the same envelope and tenancy structure while adding mission identity, a mission window, a WGS84 region, and profile/contracts metadata:

{
  "schemaVersion": "0.2.0",
  "kind": "node-manifest",
  "manifestId": "urn:example:manifest:ca.rpas.mq9b-001:2025-01-10T12:00:00Z:mission",
  "nodeId": "ca.rpas.mq9b-001",
  "issuedAt": "2025-01-10T12:00:00Z",
  "validity": {
    "notBefore": "2025-01-10T12:15:00Z",
    "notAfter": "2025-01-10T16:15:00Z",
    "graceSeconds": 300
  },
  "tenancy": {
    "tenants": [
      {
        "tenantId": "ca.dnd.cjoc",
        "displayName": "Canadian Joint Operations Command",
        "notes": "Lead defence tenant for Arctic patrol."
      },
      {
        "tenantId": "ca.tc.nasp",
        "displayName": "Transport Canada NASP",
        "notes": "Pollution and shipping surveillance."
      },
      {
        "tenantId": "ca.ccg",
        "displayName": "Canadian Coast Guard",
        "notes": "Ice, SAR, and environmental response."
      }
    ]
  },
  "profile": {
    "profileId": "amoep.v0",
    "runtimeAbi": "sov.mission-domain.v0"
  },
  "contracts": {
    "contractsDigest": "sha256:0000000000000000000000000000000000000000000000000000000000000000",
    "lensCatalogDigest": "sha256:1111111111111111111111111111111111111111111111111111111111111111"
  },
  "mission": {
    "missionLabel": "Arctic MDA Patrol - Eastern Approaches",
    "operationId": "op-nanook-2025",
    "sortieId": "sortie-2025-01-10-01",
    "missionWindow": {
      "start": "2025-01-10T12:30:00Z",
      "end": "2025-01-10T16:00:00Z"
    },
    "region": {
      "frame": "wgs84",
      "polygon": {
        "points": [
          { "lat": 70.25, "lon": -65.5 },
          { "lat": 71.0, "lon": -60.0 },
          { "lat": 73.5, "lon": -62.5 },
          { "lat": 72.75, "lon": -67.0 }
        ]
      }
    }
  }
}

The mission window is strictly inside the envelope validity window, as required for operational well-formedness. The region is expressed in WGS84 and defines a patrol box in the eastern approaches. The manifest does not require a specific flight path or sensor plan; it declares a mission slice that later evidence and analysis can be measured against.

Relationship to envelope and tenancy

The envelope fields still determine whether the manifest is in force, and the tenancy block still records which principals the sortie is intended to serve. The mission block does not change selection or eligibility. It provides a stable mission identity and a concrete space-time footprint that other systems can use for correlation, receipts, and reporting.