Every product with a published durable application journey.
Stateful systems · operating model planner
Design the journey that survives the request.
Select any journey-bearing Mappls product and receive its exact state-ownership boundary, aggregates, actors, lifecycle blueprints, runnable apps, source contracts, eight implementation controls, and production release gates.
132 states and 140 guarded transitions.
Detection and recovery remain part of the contract.
Runnable, downloadable evidence for every selected track.
Three state boundaries
Attribute every state to the system that owns it.
A stateless Mappls call can participate in a durable application journey. A provider-stateful product still does not replace your business aggregate, audit, or reconciliation model.
Provider + application state
Mappls exposes durable resources. Mirror provider identity and evidence while retaining an independent business lifecycle.
Hybrid state boundary
Request/response calculations coexist with sessions, workspaces, releases, or reviews. Persist both boundaries explicitly.
Application-owned journey
The Mappls boundary is stateless; consent, selection, inspection, and publication state belongs to the application.
Workmate
Workmate exposes durable operational resources. Mirror provider identity and lifecycle evidence in an application aggregate; an accepted request is not a completed business outcome.
- Aggregates
- task
- Platforms
- REST · Android · Web
- Authentication boundary
- Organization and user-scoped access
- Credential rule
- The planner accepts no credential, token, secret, precise location, media, or provider resource identifier.
Complete coverage matrix
Nine products. No hidden state ownership.
Every row resolves to complete journey, sample, tutorial, contract, and source evidence where the corpus establishes it.
Search & Placesaddress verification
Application-owned journey1 blueprints1 verified apps9 states · 11 transitions
4 failure plans2 contracts · 1 guides
18 tutorials
Routes & Navigationincident · navigation session · trip itinerary · route planning session
Hybrid state boundary4 blueprints3 verified apps27 states · 31 transitions
17 failure plans6 contracts · 10 guides
16 tutorials
InTouch Telematicstrip · geofence case · geofence draft
Provider + application state3 blueprints3 verified apps18 states · 18 transitions
12 failure plans11 contracts · 10 guides
9 tutorials
Workmatetask
Provider + application state1 blueprints1 verified apps8 states · 8 transitions
4 failure plans5 contracts · 2 guides
5 tutorials
GIS & Analyticsanalysis run
Hybrid state boundary1 blueprints1 verified apps7 states · 6 transitions
4 failure plans0 contracts · 3 guides
3 tutorials
App Widgets & Deep Linkswidget selection session · remote visual inspection
Application-owned journey2 blueprints2 verified apps17 states · 19 transitions
11 failure plans0 contracts · 7 guides
7 tutorials
Offline & Automotivedevice release
Provider + application state1 blueprints1 verified apps7 states · 7 transitions
4 failure plans0 contracts · 0 guides
3 tutorials
AI & Locationagent run · vision evidence case
Hybrid state boundary2 blueprints2 verified apps15 states · 14 transitions
10 failure plans7 contracts · 3 guides
3 tutorials
Capture & Feedbackfeedback report · location capture attempt · place contribution
Hybrid state boundary3 blueprints2 verified apps24 states · 26 transitions
14 failure plans2 contracts · 9 guides
6 tutorials
Eight implementation controls
Build the control plane around the API.
Each layer asks one design question, defines the implementation boundary, and names the proof required before production.
Identity and aggregate boundary
Use stable business and provider identifiers for task; never infer identity from display text or the latest coordinates.
Actor authority
Authorize every command against the named journey actors: Dispatcher, Field worker, Supervisor, Integration service. Persist the attributable actor, tenant, purpose, and policy decision.
Commands and concurrency
Require a command idempotency key and expected aggregate version. Cache the canonical result, reject key reuse with different intent, and reconcile ambiguous timeouts before retry.
Evidence and durable records
Persist immutable receipts and revisions around these catalog records: Task snapshot, Audit event, Evidence manifest, Transactional outbox. Keep event time, receipt time, source identity, hashes, and retention policy separate.
Events and side effects
Commit aggregate state, audit, and a transactional outbox together. Sign deliveries, bound retries, dead-letter exhaustions, and preserve delivery attempts without changing business history.
Recovery and reconciliation
Treat timeouts as unknown outcomes, poll or consume authoritative evidence, compare versions, append a reconciliation decision, and use compensation instead of destructive history edits.
Privacy and human control
Minimize precise location and media, scope retention, redact derived data deliberately, and require attributable approval for dispatch, publication, access, closure, and destructive change where consequential.
Operations and release
Expose state age, source freshness, stuck commands, retries, reconciliation lag, outbox depth, terminal outcomes, and per-aggregate audit. Roll out behind explicit acceptance gates.
Selected lifecycle evidence
Workmate: every published aggregate.
Open the detailed state machine or run the linked full-stack reference application. Empty contract or guide collections remain visible as evidence boundaries—not invitations to invent behavior.
Field-service task lifecycle
Create, assign, accept, travel, prove, approve, and close a field job without losing actor, retry, or evidence history.
- States
- 8
- Transitions
- 8
- Failures
- 4
- Signals
- 6
Implementation evidence
Start with exact contracts, then follow the journey.
5 endpoint contracts, 2 repository guides, 5 tutorials, 8 real-world solution blueprints, and 1 verified apps support this selected track.