Live Conformance Center
Prove the exact read. Nothing adjacent.
Turn an approved non-production account into a bounded, credential-safe observation report. Choose only allowlisted reads, keep inputs and provider bodies inside your trusted runner, inspect the JSON locally, then hand its exact digest to independent release review.
Run-plan generator
One explicit account contract. One bounded observation.
The command names environment variables, never their values. Run it only in a trusted process attached to an approved non-production account.
MAPPLS_LIVE_CONFORMANCE=1 MAPPLS_LIVE_OPERATIONS=autosuggest,route MAPPLS_CONFORMANCE_REGION=IND npm run live:verifyAdd the required values through your approved secret provider: MAPPLS_STATIC_KEY · MAPPLS_CONFORMANCE_QUERY · MAPPLS_CONFORMANCE_ORIGIN · MAPPLS_CONFORMANCE_DESTINATION. Never paste them into this page, a prompt, a ticket, or the report.
Autosuggest
search.autosuggestThe runner-owned current path and the acquired legacy source operation are compared as separate generations; a passing probe proves only the issued account contract.
Route
routes.planA route response proves only the selected locations, profile, account, generation, region, and observation time.
Local-only report inspector
Validate the boundary before review sees the artifact.
The inspector parses and hashes the exact file inside this browser. It refuses unexpected fields, credential-like values, request URLs, input locations, device identities, inconsistent counts, or weakened authority statements.
All product families
Eight reads are useful. They are not the whole platform.
Every product remains visible, including the seven families that require dedicated SDK, widget, sovereign, AI, contribution, or stateful journey qualification instead of a generic HTTP probe.
Maps
No generic live probe is claimed. Use the product-platform qualification plan and its exact SDK, widget, sovereign, AI, or stateful journey evidence.
Search & Places
4 bounded read probes are implemented. SDK, widget, write, callback, quota, commercial, privacy, and production behavior remain separate evidence.
Routes & Navigation
2 bounded read probes are implemented. SDK, widget, write, callback, quota, commercial, privacy, and production behavior remain separate evidence.
InTouch Telematics
2 bounded read probes are implemented. SDK, widget, write, callback, quota, commercial, privacy, and production behavior remain separate evidence.
Workmate
No generic live probe is claimed. Use the product-platform qualification plan and its exact SDK, widget, sovereign, AI, or stateful journey evidence.
GIS & Analytics
No generic live probe is claimed. Use the product-platform qualification plan and its exact SDK, widget, sovereign, AI, or stateful journey evidence.
App Widgets & Deep Links
No generic live probe is claimed. Use the product-platform qualification plan and its exact SDK, widget, sovereign, AI, or stateful journey evidence.
Offline & Automotive
No generic live probe is claimed. Use the product-platform qualification plan and its exact SDK, widget, sovereign, AI, or stateful journey evidence.
AI & Location
No generic live probe is claimed. Use the product-platform qualification plan and its exact SDK, widget, sovereign, AI, or stateful journey evidence.
Capture & Feedback
No generic live probe is claimed. Use the product-platform qualification plan and its exact SDK, widget, sovereign, AI, or stateful journey evidence.
Authority boundary
A passing probe is evidence—not permission.
It must join account, entitlement, product-owner, security, privacy, hostile-path, operations, release, deployment, and post-release evidence in their authoritative systems.
- 01
Planning is credential-free and makes no provider request; live execution requires MAPPLS_LIVE_CONFORMANCE=1 in an approved non-production account.
- 02
Only the eight allowlisted read operations are executable. No write, trip mutation, geofence mutation, task transition, upload, contribution, or durable provider command is exposed.
- 03
Reports exclude credentials, request URLs, query text, addresses, coordinates, device identifiers, provider bodies, and arbitrary error messages.
- 04
A pass proves only the exact operation, authentication generation, account authority, region, endpoint host, and observation time. It is not entitlement for an adjacent capability or production approval.
- 05
Stateful products require full replay, concurrency, unknown-outcome, reconciliation, expiry, recovery, and independent-release journeys beyond any read probe.