If you're integrating the copilot on **your own site** (not the Platform's internal panel or its partner console), this section doesn't affect you: your widget never issues an attestation, and the `internal` audience of your actions is only reached by a session your own backend identifies some other way. Attestation is the mechanism those first-party panels use so their "Assistant" panel knows whoever opened it is an already-identified operator — a 5-minute JWT, signed by the Platform's backend, accepted only by instances marked as "first-party panel". It grants no access to data by itself: it only counts as identity for the audience check and for logging who confirmed each action.