Evidence levels
Read support claims by implementation, contract, live account, approval, and release evidence for each capability.
Social integrations can compile while remaining unusable for a particular account, scope, runtime, or platform approval state. Social SDK records those facts separately.
| Level | What it proves | What it does not prove |
|---|---|---|
| Implemented | The adapter contains a real code path for the capability. | The upstream request succeeds. |
| Contract-tested | Fixtures and protocol tests cover requests, responses, errors, and lifecycle mapping. | A current live account accepts the operation. |
| Live-verified | A named account class completed the recorded operation on a stated date. | Every account, format, region, or permission works. |
| Approval-dependent | Code and permitted test-mode evidence exist, but public use needs platform review or audit. | Public production approval has been granted. |
| Released | The verified package artifact exposes the documented module and behavior. | A user’s credentials or account are eligible. |
These levels are recorded separately from the capability manifest. A manifest declaration carries only operation, platform, availability, and optionally formats, requiredScopes, and notes; the manifest itself names the backend, apiRevision, and runtime. Account class and verification date belong to a live-verification record, and a claim at that level needs one.
Provider documentation links and their check date are provenance, not live verification. A cited limit or upstream feature can explain an adapter contract, but it does not prove that the current account, plan, scope, or approval accepts the request.
Evidence levels are separate from the CapabilityAvailability values in a manifest: available, unsupported-by-platform, not-implemented-by-adapter, permission-required, reconnect-required, account-ineligible, runtime-unavailable, approval-dependent, and unknown-until-request. The client dispatches only available. The approval-dependent evidence level above is not the approval-dependent availability value; see capabilities.