Recipes/Mining/stateful
durable operation2–3 hr5 stages8 code languages

Operating journey: Move material safely across a changing mine

Higher productive haulage with fewer route conflicts, stale-map movements, and unexplained cycle losses.

The real-world moment

A blast changes the active pit and closes a ramp midway through a shift. Dispatch must publish the newly approved road and exclusion-zone version, reassign compatible trucks and loaders, guide offline-capable cycles, distinguish telemetry delay from a stopped vehicle, preserve safety interventions, and reconcile production only from accepted load and dump evidence.

Make ownership visible before code.

Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.

Application state
stateful
Planning calls
0
Credentials accepted
No
Write authority
None
01
Mine plan and safety authority

Publish the approved pit, road, and exclusion-zone version

The mine system of record owns surveyed geometry, blast areas, geotechnical restrictions, road classes, equipment compatibility and operating authorization.

Mine map package ↔ survey/version, region, signature, compatibility and approval

GETGets The List Of Alarm Config(s)/alarm/alarmLog/This is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Record stage 1 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

A truck wakes with the previous pit map

Block the changed operating zone, retain the compatible prior slot for recovery, and require a qualified signed update before dispatch.

02
Versioned offline map release

Assign compatible equipment and operators

Approved pit, road, zone and configuration manifests move through signed dual-slot qualification and rollback before vehicles activate them.

Assignment ↔ equipment/operator capability, shift, plan version and expected aggregate version

GETGets the historical location events of a device./device/{deviceId}/eventsThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Record stage 2 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Telemetry silence looks like an idle vehicle

Separate freshness from motion state, show last verified evidence, and ask dispatch to reconcile rather than charging productive-time loss automatically.

03
Dispatch aggregate

Guide and observe offline-capable haul cycles

Application state owns shift, equipment/operator assignments, load/dump targets, priorities, expected versions and deliberate cancellation.

Cycle event ↔ source/content identity, event/receipt time, map version and stage

GETTo get the list of tasks and their details/tasksThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Record stage 3 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Duplicate dump evidence inflates tonnes

Deduplicate by source/content and cycle identity, reject conflicting replays, and reconcile against the authoritative scale record.

04
Haul-cycle evidence

Stop and review safety or geofence exceptions

InTouch observations and offline commands derive travel, queue, load and dump stages by event time while keeping raw source identity and freshness.

Record stage 4 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

A truck wakes with the previous pit map

Block the changed operating zone, retain the compatible prior slot for recovery, and require a qualified signed update before dispatch.

05
Safety and production reconciliation

Reconcile tonnes, cycles, maintenance, and shift closure

Geofence or route exceptions stop automatic progress and require human review; tonnes and cycles close only against authoritative scale and dispatch evidence.

Production result ↔ accepted load/dump identities, tonnes, shift and reconciliation status

GETGets the historical location events of a device./device/{deviceId}/eventsThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Record stage 5 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Telemetry silence looks like an idle vehicle

Separate freshness from motion state, show last verified evidence, and ask dispatch to reconcile rather than charging productive-time loss automatically.

Edit once. Generate eight trusted-runtime implementations.

The recipe starts from the normalized GET /alarm/alarmLog/ contract. Execute six deterministic fixture outcomes before an issued account is involved.

Local request composerCode stays local · fixtures are explicit
GETRequest inputs
4 editable · 0 protected
Generated in eight languages
Environment-backed credentials
GEThttps://intouch.mapmyindia.com/iot/api/alarm/alarmLog/?deviceId=1909%2C2545&alarmType=21%2C26&startTime=1700000000000&endTime=1700000000000
Credential-free sandboxExecute this contract without a provider call
How fixtures work
Generated from your inputs
curl --request GET \
  --url 'https://intouch.mapmyindia.com/iot/api/alarm/alarmLog/?deviceId=1909%2C2545&alarmType=21%2C26&startTime=1700000000000&endTime=1700000000000' \
  --header "Accept: application/json" \
  --header "Authorization: Bearer ${MAPPLS_INTOUCH_TOKEN}"

Credential-safe by constructionSet MAPPLS_INTOUCH_TOKEN only in your trusted runtime. Code generation stays local. Sandbox execution sends only bounded fixture inputs to this developer platform and never reads a credential or calls Mappls.

Break the journey before customers do.

These controls are required at this operating depth; deeper recipes add durable truth rather than merely more API calls.

Idempotent commandsOptimistic aggregate versionsEvent and receipt timeTransactional outboxUnknown-outcome reconciliationIndependent human decisionsRestart recoveryImmutable audit evidence

Definition of done

Every aggregate has an invariant, expected version, stable command identity, and attributable actor.

Duplicate, late, reordered, invalid, stale, timed-out, and restarted execution preserve one durable truth.

Unknown provider outcomes reconcile by original identity before replay or compensation.

Terminal decisions, human review, audit, outbox delivery, privacy, retention, and rollback remain independently evidenced.

Contracts, tutorials, and journeys stay linked.

Contract set

GETGets The List Of Alarm Config(s)/alarm/alarmLog/GETTo get the list of tasks and their details/tasksGETThis API will get all the alarm configurations for a user./alarmGETTo get all your client details/clientsGETGets The List Of Alarm Config(s)/alarms/alarmlogs/GETTo get the list of client category in an account/configurations/categoriesGETThis API will get all the alarm configurations for a user./alarmsGETTo get the form's Id and their details from your account./configurations/formsGETGets the historical location events of a device./device/{deviceId}/eventsGETGet users attendance details with travelled distance./reports/attendancesGETGets drive details of a device./device/driveGETTo get form based check in/out details/reports/forms/{formId}

Durable state machines

statefulField-service task lifecycle8 states · 8 transitionsstatefulConnected fleet trip6 states · 7 transitionsstatefulFleet geofence exception6 states · 5 transitionshybridGoverned spatial analysis7 states · 6 transitionsstatefulOffline automotive release7 states · 7 transitionshybridiOS geofence draft and publication boundary6 states · 6 transitionshybridiOS feedback report and review9 states · 9 transitionshybridConsent-bound location capture evidence8 states · 9 transitionsstatefulGoverned place contribution and publication7 states · 8 transitions

Airside Turnaround Desk

Coordinate a revision-safe aircraft turnaround, pause for airside exceptions, preserve four service milestones, and require independent airline, airport, and safety readiness decisions.

Source-grounded, not authority-granting

This recipe composes source-derived contracts, application architecture, fixtures, and maintained learning evidence. It does not prove package availability, provider payload shape, account entitlement, regional behavior, production compatibility, or release approval.