Model towers, links, cabinets, and service areas
Capture intent and source evidence without inventing a more precise state than the inputs support.
Link network assets, alarms, field teams, and customer impact spatially.
A fibre cut triggers alarms across cabinets and cell sites while customers report outages. Operations must correlate evidence to the affected topology, estimate customer impact, create skill/tool/access-aware repair work, route teams around road disruption, capture splice/test proof, and avoid declaring restoration until network telemetry and customer-impact projections reconcile.
Capture intent and source evidence without inventing a more precise state than the inputs support.
Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.
Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.
Advance through an idempotent boundary, preserve stable Mappls identity, and expose freshness and ownership.
Reconcile the terminal result to every authoritative system and retain attributable evidence.
Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.
Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.
Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.
Version, authorize, retain, observe, and reconcile this relationship explicitly; do not recover it later from display text or logs.
Preserve every alarm, derive one incident using a versioned topology/correlation rule and allow operator correction.
Mark confidence, route to data-steward correction and never rewrite prior incident lineage after the new version.
Keep work proof submitted but incident in reconciliation; query authoritative telemetry and escalate mismatches.
Create, assign, accept, travel, prove, approve, and close a field job without losing actor, retry, or evidence history.
statefulResolve an incident location, select a capable available responder, route and observe the unit, adapt to hazards, establish arrival, resolve with evidence, and review every decision.
hybridMove from route intent through preview, guidance, reroute, arrival, and cleanup while surviving process, sensor, and network interruption.
hybridIngest versioned data, validate and publish it, execute reproducible analysis, review lineage, and share a governed decision layer.
Resolve endpoints, request alternatives, decode geometry, and explain toll/time trade-offs.
AdvancedJoin asset telemetry, map matching, route progress, ETA refresh, and customer visibility.
AdvancedProvision workers, dispatch jobs, consume transitions, enforce proof, and reconcile closure.
AdvancedPublish layers, generate catchments, join signals, score candidates, and share results.
IntermediateRun the MCP server, scope credentials, call search and routing tools, and inspect provenance.
AdvancedVerify signatures, deduplicate deliveries, order per aggregate, retry, and replay safely.
Correlate an outage, govern independent switching approval, dispatch an assigned crew, preserve rework, and reconcile restoration from telemetry and customer-impact evidence.
Confirm the correct receiving entrance, assign eligible transport, preserve courier custody, review condition exceptions, and reconcile receiver acceptance without retaining patient or clinical data.
Coordinate a revision-safe aircraft turnaround, pause for airside exceptions, preserve four service milestones, and require independent airline, airport, and safety readiness decisions.