# AI-native Mappls integrations

## Select the interface

- Use the offline AI corpus for retrieval, planning, evaluation, and citations.
- Use MCP when a model needs typed tools/resources in one client session.
- Use A2A when another agent needs discovery, delegation, durable task status, and artifact retrieval.
- Use the REST/SDK boundary behind tools when the application, not the model, owns the integration.

## Default authority

Start offline. The offline profile accepts no provider credential, performs no provider call, exposes no write, and grants no production approval.

For live reads, bind purpose, client/principal identity, OAuth resource/scope, exact tool allowlist, restricted server-held provider credential, region, minimization, consent/workforce authority, budget, timeout, audit, kill switch, evaluation suite, and independent release outside model context.

## Model-visible data

Keep credentials, raw provider payloads, unnecessary precise locations, long asset histories, customer content, private media, operational write authority, and chain-of-thought out of prompts and retained traces. Preserve safe provenance: tool, canonical identity, source, region, event/observation time, and result class.

Separate in every answer:

1. observed provider fact;
2. deterministic application calculation;
3. model inference or recommendation;
4. human decision;
5. missing evidence.

Conversation history is not a consent ledger, durable workflow, telemetry store, release record, or system of authority.

