AdminConsole
Capability Qualification Center

From listed to independently qualified.

Turn any product-platform decision into a source lock, runtime and authentication choice, offline contract proof, issued-account conformance run, hostile-path suite, and independently governed release handoff—without putting secrets or invented support claims into the plan.

Build a qualification plan Review capability matrix
Decision plans130Every product × platform cell
Ready to qualify43Exact public evidence exists
Contract selection4Listed, exact evidence missing
Not listed83Product-owner decision first
Exact selector

Build one portable evidence journey.

A successful plan is not a support claim. Product, account, entitlement, compatibility, region, quota, security, operations, release, and deployment each retain separate authority.

Reset
Intelligence · browser or embed

GIS & Analytics on Web

Spatial data, analysis, maps, dashboards, and embeddable location intelligence.

Ready for qualification
Decision boundary

Listed means this product names the platform in the canonical catalog. Source evidence, repository activity, fixtures, tutorials, and successful builds still do not prove package availability, account entitlement, runtime compatibility, region, quota, support, or production approval.

Identity lock

Freeze the decision before touching an account.

  • Product and platform decision ID
  • Account and environment reference
  • Region and data-residency decision
  • Exact HTTPS origin and CSP policy
  • Script, iframe, widget, or deep-link generation
  • Browser fallback and message-origin contract
  • Source/distribution fingerprint and release owner
  • Quota, support, incident, rollback, and retirement owners
Authentication candidates

3 scoped paths

Open credential center
widget · entitlement-specificApp widgets and iframe embedsSelected widget contractenterprise · entitlement-specificmGIS browser surfacesSelected mGIS or MIGIST surfaceenterprise · selection-requiredEntitled or source-ambiguous productAccount-specific
Six-phase journey

Application proof stays separate from external authority.

01
Product owner + application technical owner

Lock source and product authority

actionable

Resolve the exact product, platform, source, distribution, generation, account, region, and owner before code or access is approved.

Work
  • Review exact evidence separately from adjacent learning material.
  • Record every unresolved package, endpoint, callback, entitlement, and version question.
  • Keep not-listed and selection-required decisions blocked until an attributable owner supplies exact evidence.
Exit evidence
  • Immutable product-platform decision
  • Exact source/distribution identities and fingerprints
  • Named product, security, application, and release owners
02
Application owner + security

Lock runtime and authentication

actionable

Bind the runtime identity to one authentication generation and least-privilege placement without accepting a credential value.

Work
  • Record the runtime identity fields for this integration lane.
  • Choose one issued authentication path and document forbidden placement.
  • Define non-production restrictions, rotation, redaction, and incident ownership.
Exit evidence
  • Runtime compatibility decision
  • Credential class and restriction record
  • Secret/public-value placement review
03
Application team

Prove the application contract offline

actionable

Exercise a deterministic adapter and every application-owned invariant before provider access.

Work
  • Run the clean-build and fixture-success scenarios.
  • Normalize provider-shaped data at the adapter edge and keep opaque objects out of durable state.
  • Prove denial, quota, unavailable, upgrade, and rollback behavior with fixtures.
Exit evidence
  • Fixture results tied to the source lock
  • Application contract/schema
  • Failure and rollback evidence
04
Product owner + application team

Qualify issued non-production access

external evidence required

Run the smallest read or explicitly approved test journey against an issued non-production account without exporting secrets or sensitive payloads.

Work
  • Confirm account, entitlement, host, region, quota, and exact operation/distribution.
  • Capture credential-free conformance results and safe request identities.
  • Compare live shape and failure classification to the locked application contract.
Exit evidence
  • Signed or attributable product-owner decision
  • Credential-free conformance report
  • Account/region/quota/entitlement reference
  • Observed compatibility and divergence record
Blocked byIssued non-production account and approved provider contract are external requirements.
05
Application team + operations

Exercise lifecycle and hostile paths

external evidence required

Prove complete success, denial, degradation, recovery, restart, and rollback behavior at the integration's true state depth.

Work
  • Execute every published qualification scenario.
  • For hybrid/stateful work, prove replay, stale-version, unknown-outcome, and restart recovery.
  • Verify telemetry, quota alarms, support evidence, cleanup, and rollback.
Exit evidence
  • Scenario-by-scenario result ledger
  • State/reconciliation evidence where applicable
  • Alert, runbook, support, cleanup, and rollback evidence
Blocked byOperational telemetry and provider-degradation exercises require an approved environment.
06
Independent security + operations + product release owners

Independent release and deployment

external evidence required

Freeze the qualified artifact and collect independent authority without allowing developer evidence to self-approve production.

Work
  • Attach exact artifacts to the governed release workflow.
  • Review security/privacy, product conformance, operations, quota, regional, legal, and rollback evidence.
  • Use progressive deployment and independently reconcile production health.
Exit evidence
  • Immutable release artifact and evidence digests
  • Independent approvals
  • Progressive deployment, rollback, and post-release reconciliation evidence
Blocked byThis catalog never grants entitlement, support, production release, or deployment authority.
Hostile-path suite

9 scenarios at hybrid depth

Replay, concurrency, unknown outcome, delayed evidence, and restart recovery are mandatory.

Clean build and identity lock

Prove the selected source, distribution, toolchain, and runtime identity from a clean environment.

Checksums, dependency lock, build log, runtime identity, and exact evidence links agree without workstation-only state.
Stop qualification, reconcile the exact distribution or contract, and rebuild from a clean environment.
Deterministic fixture success

Exercise the application adapter without credentials or provider traffic.

The fixture produces the documented application contract and retains source identity plus state ownership.
Fix the application boundary before requesting account access; a live call must not compensate for an unproven adapter.
Missing, denied, expired, and revoked access

Prove least-privilege failure without logging, reflecting, or weakening credential controls.

Every access failure is classified, redacted, bounded, and routes to entitlement or credential reconciliation.
Stop retries, preserve only safe request evidence, and reconcile the issued account contract independently.
Quota, timeout, offline, and service unavailability

Prove bounded retry, fallback, and user-visible degradation for the exact operation safety class.

Retry-After is honored where present; uncertain state changes never become blind retries.
Use bounded backoff for safe reads and reconcile state-changing unknown outcomes before replay.
Upgrade, downgrade, and rollback

Prove that source, SDK, wrapper, schema, and runtime changes are independently reversible.

Compatibility evidence names both versions, acceptance results, rollback trigger, and retained data/state behavior.
Freeze rollout, restore the last qualified artifact, and reopen source and entitlement selection.
Idempotent command replay

Repeat one stable command identity after a committed or uncertain result.

The aggregate version and application event identity do not duplicate.
Reconcile by stable business and provider identity before any new command.
Stale version and concurrent actor

Prevent an older actor or callback from overwriting newer durable truth.

The stale transition is rejected without state mutation or event emission.
Reload the current aggregate, re-evaluate policy, and require a new attributable decision.
Unknown provider outcome

Separate timeout from failure and preserve a recoverable pending state.

The application records the attempt, reconciles provider truth, and completes or retries without duplication.
Do not infer success or failure; reconcile using the exact issued operation and durable identity.
Restart and delayed evidence

Recover application-owned state after process restart and reject late or superseded callbacks.

The journey resumes from durable records and preserves generation, actor, and event ordering.
Rebuild the read model from immutable application evidence and quarantine ambiguous callbacks.
Required release evidence
  • Exact source, package/distribution, contract generation, and runtime identity
  • Issued account, entitlement, region, quota, and credential-class reference without secret values
  • Clean build, fixture, non-production conformance, hostile-path, upgrade, and rollback results
  • Security, privacy, accessibility, operational, legal/content, and product-owner decisions
  • Immutable release artifact digest, progressive deployment evidence, and independent post-release reconciliation

This downloadable plan accepts no credential or provider payload, makes zero provider calls, exposes no write, and never grants production approval.