Orchestrator Interface

Ported from the full pack; payloads reflect gist's disclosure-profile + correlation fields.

Boundary

flowchart LR
    GIS[GIS Portal: spatial fact]
    ORCH[Orchestrator: coordination decision]
    APP1[Transport App]
    APP2[Mining App]
    APP3[Environmental App]
    APP4[Utility App]
    GIS -->|RP-2026-001 intersects ML-1032 - idempotent EventDelivery| ORCH
    ORCH --> APP1
    ORCH --> APP2
    ORCH --> APP3
    ORCH --> APP4

The GIS portal supplies a spatial fact and contextual references. The Orchestrator determines routing, coordination, approvals, obligations and follow-up.

Outbound endpoint

POST http://orchestrator:8000/api/v1/events
Content-Type: application/json
X-Event-ID: EVT-2026-000101

Envelope defaults (config/orchestrator.yaml): source_system: gis_tenancy_portal, schema_version: "1.0", correlation_id from the event.

Example payload (seeded EVT-2026-000101)

{
  "event_id": "EVT-2026-000101",
  "event_type": "gis.spatial.relationship_detected",
  "schema_version": "1.0",
  "source_system": "gis_tenancy_portal",
  "tenant": "transport",
  "correlation_id": "gist-corr-RP-2026-001",
  "rule_code": "ROAD_INTERSECTS_MINING_LEASE",
  "severity": "warning",
  "disclosure_profile": "coordination_basic",
  "source": { "external_ref": "RP-2026-001", "name": "Northern Connector Upgrade" },
  "target": { "external_ref": "ML-1032",     "name": "Example Mining Lease 1032" },
  "relationship": { "type": "intersects", "distance_m": null, "overlap_area_m2": 1120000.0 }
}

Example response

{ "accepted": true, "orchestration_ref": "ORC-00451" }

Required behaviour

acknowledgement · retry · idempotency · correlation · replay · audit · health checks (GET /api/v1/integrations/orchestrator/health).

Data minimisation

Do not send complete GIS records by default. Send identifiers and the minimum relationship information needed for routing — bounded by the event's DisclosureProfile (page 05).

Reconciliation

Compare GIS relationship status with Orchestrator coordination status. A closed case over an active spatial conflict — or, as seeded in RECON-2026-0012, an Orchestrator that still lists a ceased relationship as active — becomes a ReconciliationCheck exception (STALE_RELATIONSHIP) for review.