# BT6 External Provider Integration Checklist

## Service and identity

- Resolve the endpoint without credentials where safe; record TLS validity,
  DNS/CDN ownership, response status, and vendor-specific headers.
- Corroborate legal identity and contributor affiliation.
- Record organization, domain, and product age as maturity evidence rather than
  a binary legitimacy test.
- Prefer primary documents and label vendor-authored research or benchmarks.

## Trust and data handling

- Inventory prompts, outputs, credentials, metadata, tool arguments, logs,
  billing data, upstream providers, CDN/edge services, and subprocessors.
- Compare observed infrastructure with published processor disclosures.
- Compare legal privacy promises with technical logging/configuration behavior.
- Verify assurance claims through an auditor, report, certificate identifier,
  BAA/DPA, or other checkable evidence. Marketing badges are insufficient.
- State which workload and data classifications the evidence supports.

## Claim-to-code traceability

| Claim | Implementing code/config | Behavioral test | Classification |
| --- | --- | --- | --- |
| `<claim>` | `<path or none>` | `<test or none>` | `<implemented/provider-only/future/unsupported>` |

Tool-governance claims require explicit policy configuration, pre-execution
evaluation of every claimed path, fail-closed outage behavior, bypass tests,
and auditable decisions. A chat-completion endpoint alone does not meet this
bar.

## Named-provider completeness

- Provider type, registry, adapter, and configured-provider detection.
- Setup, generated environment templates, documentation, and removal path.
- Secret redaction, safe export, logging discipline, and child-process stripping.
- CLI status and relevant UI/settings surfaces.
- Explicit activation and documented fallback ordering.
- Dynamic discovery or reviewed fallback metadata with provenance/date.
- Normalized authentication, timeout, rate-limit, malformed-response, and
  upstream errors.

## Tests and gates

- Mock the HTTP boundary and assert URL, authorization handling, model ID,
  request body, success, 401, 429, timeout, malformed response, and unintended
  fallback behavior.
- Prove secrets do not enter exported settings, logs, fixtures, snapshots, or
  child-process environments.
- Run profile quick, matched risk-surface, full, documentation, and CI checks as
  required by blast radius.
- Re-verify the exact published head SHA.

## Documentation defaults

- Describe remote providers as third-party and opt-in.
- Disclose which credentials and data leave the consuming repository.
- Identify upstream/subprocessor uncertainty and link current policies.
- Avoid endorsement of security, compliance, availability, model provenance,
  privacy, or tool control without independent evidence.
