Disclosure belongs at the point of exposure

Transparency is time-sensitive. A person forms an impression before opening the details panel, reading the caption, visiting the source page, or finding a policy link. If the synthetic or manipulated nature of content matters to interpretation, disclosure after the encounter cannot fully restore the decision context that was missing at the start.

The Commission's July guidelines address transparency obligations for providers and deployers under Article 50, which begin applying on August 2, 2026. The operational question is not only whether a disclosure exists somewhere. It is which actor presents it, to whom, in what form, and at which point in the experience.

Exposure points multiply across a distribution chain. The original service may show a clear notice while an embed, notification, search result, repost, clip, quotation, or downloaded artifact does not. Inventory the first meaningful encounter in each route. The best control often combines a portable signal with a channel-native disclosure rather than assuming one surface controls all later contexts.

Design for the first interpretation

Place the disclosure where it can influence interpretation without obscuring the content or creating warning fatigue. The appropriate form may be a persistent label, an opening statement, an audible cue, a nearby caption, or contextual text. Test with the actual audience and task. A disclosure that technically precedes exposure but is routinely skipped may need a different design.

Specificity improves usefulness. Generated, translated, reenacted, materially altered, and fictionalized are not interchangeable descriptions. State the fact the system can support and the scope of the alteration. Avoid implying falsity, deception, or endorsement when the evidence only establishes machine involvement.

Transparency arrives on time only if it can shape the first consequential interpretation.

Accessibility is part of timing. A visual label may not reach a screen-reader user. An audio disclosure may be lost in muted autoplay. A color cue may be imperceptible. Provide equivalent paths and include them in release testing. The accessible version should carry the same specificity, not a generic alternative.

Repeated exposure changes the design problem. A persistent notice can become clutter; a one-time notice can be forgotten or missed. Define when the context meaningfully changes—new content, new creator, new session, new modality, or new consequence—and renew notice there. The rule should be stable enough to test and visible enough for users to predict.

Measure comprehension and placement failures separately. Ask whether people noticed the disclosure, understood what it referred to, and changed any relevant interpretation. Pair that research with telemetry showing whether the disclosure rendered before exposure. Neither metric alone establishes an effective experience.

Make the obligation operational

Begin with the first consequential exposure point, audience, disclosure wording, modality, persistence, and renewal condition for each distribution route. Express it as a control object rather than a policy summary: scope, triggering condition, applicable system or model version, permitted exception, effective time, evidence source, and the consequence when the control cannot establish compliance. This lets engineering, product, legal, and operations examine the same boundary without pretending their responsibilities are interchangeable.

The minimum receipt should retain content and route identifiers, rendered disclosure, timing, accessibility variant, applicable rule and exception, comprehension test, and missing-render events. Keep the record proportionate and protect confidential information, but make it possible to determine which rule, artifact, system version, and accountable decision governed the event. A folder of undated screenshots may show that work occurred; it rarely proves that the operative control held for the affected release.

Test the implementation by following content through feeds, embeds, search, notifications, downloads, clips, quotations, muted playback, and assistive technology while observing first interpretation. Include ordinary cases, boundary cases, degraded dependencies, and known exceptions. Preserve the starting state, observed output, machine-readable evidence, user-visible result, and any human intervention. Re-run the test after changing a model, content pipeline, interface, standard, provider, or policy interpretation.

The deployer experience owner with accessibility and transparency owners should decide whether the evidence supports continued operation, a narrower scope, a compensating control, or a hold. The owner needs authority over the affected release and access to the evidence. Record unresolved interpretation separately from a technical defect so an engineering patch does not masquerade as a legal conclusion.

Monitor both presence and effectiveness. A marker can exist but be stripped downstream. A disclosure can render but arrive after exposure. A document can be submitted but refer to an obsolete model. Pair a control-presence measure with a consequence or comprehension test, give the claim a review date, and reopen it when a dependency changes.

Maintain a dependency register for the control. Model endpoints, editing pipelines, content formats, user interfaces, identity services, submission portals, vendors, and external standards can change the evidence without changing the policy text. Name which changes invalidate the last test and which monitoring signal proves that the dependency remains inside the reviewed state.

Exercise the exception path as carefully as the ordinary path. Record who can invoke it, which facts they must supply, how long it lasts, what capability or distribution is reduced, and which compensating evidence remains. An exception without expiry and re-entry criteria becomes a second operating model that can silently outlive the reason it was approved.

Keep public and executive claims no broader than the tested boundary. Say which systems, releases, formats, routes, and dates the evidence covers, and identify material exclusions. When a control fails or a dependency moves, update the claim and the remediation record together. A transparent limitation protects more credibility than a universal statement built from a narrow passing test.

— Dispatches · Summit Cognitive