Map-First Operations for Expeditions (Map First Operations For Expeditions)

Map-First Operations for Expeditions

Expeditions work best when list and map share selection state; routing and GeoJSON support field decisions.

expedition list ↔ map selection ↔ detail

Liste ve harita aynı seçim gerçeğini paylaşmalı.

Concepts, defined where they first appear

📦 Control Plane
Surface that binds map, content, notifications, and integration edges.

📦 Ops Monolith
Broad panel — often CRA — living outside the federated estate.

📦 Push Admin
Admin for campaign/push notifications — not the snackbar remote.

📦 ERP Edge
Integration edge where ERP sync lives under unreliable boundaries.

Teams that blur these concepts confuse UI state with integration truth.

Shape of the problem

Expeditions work best when list and map share selection state; routing and GeoJSON support field decisions.

expedition list ↔ map selection ↔ detail

The split that works

Liste ve harita aynı seçim gerçeğini paylaşmalı.

expedition list ↔ map selection ↔ detail
        ↓
   explicit contract

Where production breaks

Incidents grow when radius, identity, or deploy assumptions stay implicit. Make the contract visible and reversible.

The mappings that get confused most often

❌ One app is always safer
✓ Without clear boundaries, one app is more fragile

❌ Keep config hardcoded
✓ Radius, remote URLs, and expose paths are operational contracts

❌ Vendor/API truth is UI state
✓ Vendor feed is evidence; ops state is a decision

A checklist for auditing your own system

1. Write the ownership boundary for this surface in one sentence.
2. If this contract changes, who deploys?
3. On timeout or vendor delay, what does the UI show?
4. Do you test embedded and standalone paths separately?
5. Deny-list check: any vendor/domain leakage in copy?

What to take away from this part

1. Contracts must be visible: expose paths, radius, ticket state, or remote URLs.
2. The gap between UI and external systems is a design choice, not a bug.
3. Independent deploy means independent rollback.

The boundary you hide will find you in production.