Ad Rights, Disclosure and Brand Safety

When “publishable” still does not mean “cleared for release”

A creator video is technically ready and the ad platform considers the placement eligible, but the product was gifted, the disclosure is hidden after a “more” fold, and the music license covers organic social only. A platform green light exists; release clearance does not.

This lesson produces Ad Rights Disclosure Brand-Safety Gate v1. It deliberately separates four evidence tracks: Rights, Disclosure, Platform Policy/Suitability, and Brand-specific Suitability. Each track has its own scope, version, placement/jurisdiction context, reviewer, and evidence. Release is allowed only when no decisive track is missing, stale, disputed, or blocked.

COM-025 ownership boundary

COM-025 owns the pre-release gate. COM-024 owns creator/media inventory and asset provenance; COM-026 owns attribution and measurement labels. This lesson does not create talent contracts, rebuild media inventory, prove causal lift, or publish a live campaign.

A platform may say a placement is policy-eligible or suitable. That is one evidence track only. It cannot turn an incompatible license, hidden disclosure, or jurisdiction ambiguity into approval.

Mental model: four parallel gates, one derived release decision

Use this flow:

campaign/creative identity → material connection → disclosure evidence → rights/license scope → platform/placement policy → brand suitability profile → jurisdiction/reviewer → release state

The gates are independent; the ordering is not an override hierarchy. READY_FOR_RELEASE means all decisive tracks are resolved for that exact campaign, creative, placement, and jurisdiction. Legal ambiguity becomes LEGAL_REVIEW_HOLD; the model cannot manufacture legal authority from confidence.

Separate FACT, INFERENCE, and DESIGN

FACT: FTC guidance says a material relationship with a brand—including financial, employment, personal/family, free-product, discount, or other value connections—should be disclosed. The disclosure should be placed with the endorsement and be hard to miss and understand.

FACT: Google Ads content-suitability controls add brand-fit filtering beyond baseline monetization/content policies, but applicability and coverage depend on campaign/inventory and Google documents limitations. These controls are not legal or rights clearance.

INFERENCE: Rights, disclosure, platform policy, and brand suitability need separate evidence tracks because one can pass while another fails or goes stale.

DESIGN: MAKNOW maps legal/jurisdiction ambiguity to LEGAL_REVIEW_HOLD; no platform status can override missing rights or disclosure evidence.

The 21-dimension release contract

Gate 1 — gate identity is not campaign identity

gate_id identifies an evaluation snapshot. campaign_id and creative_id identify the initiative and asset. A changed placement or creative can require a new gate even when the campaign name is unchanged.

Gate 2 — type the material connection

relationship_type and material_connection_state capture paid, gifted, discounted, employment, affiliate, personal/family, or other value relationships. Never coerce UNKNOWN to absent.

Gate 3 — disclosure text and placement are separate evidence

A disclosure_text_ref alone is insufficient. disclosure_placement and disclosure_visibility_check must show the disclosure is presented with the endorsement and is likely to be noticed and understood.

Gate 4 — separate rights clearance from asset existence

rights_clearance_ref traces the clearance source; license_scope must cover the actual use: organic/paid, territory, duration, medium/placement, and derivative rights where relevant. Organic permission does not imply paid amplification rights.

Gate 5 — bind platform to placement

platform without placement_type is incomplete. Different inventory and placements can have different control coverage and policy behavior.

Gate 6 — platform policy evidence is versioned

platform_policy_version or a dated review snapshot is required. Material policy change or stale evidence reopens the gate.

Gate 7 — brand suitability is not platform eligibility

brand_suitability_profile and exclusion_refs capture the brand's own tolerance. Platform-compliant content can still be unsuitable for a specific brand.

Gate 8 — inventory type matters

inventory_type records where controls actually apply. Never infer universal coverage from a control that covers only some inventory.

Gate 9 — jurisdiction is explicit

jurisdiction_scope names the market/legal scope reviewed. Moving the same creative to another jurisdiction reopens the legal gate even if the asset bytes do not change.

Gate 10 — reviewer role carries authority

reviewer_role records who is authorized to resolve the relevant uncertainty. Legal ambiguity is escalated, not guessed by the model.

Gate 11 — decision state is derived

Missing disclosure yields HOLD_DISCLOSURE; incompatible rights yield HOLD_RIGHTS; stale platform evidence yields STALE or HOLD_PLATFORM_POLICY; brand mismatch yields HOLD_BRAND_SUITABILITY; legal ambiguity yields LEGAL_REVIEW_HOLD.

Gate 12 — evidence_ref reconstructs the decision

Each gate row should trace to license/contract evidence, disclosure artifact, platform-policy snapshot, brand profile, and review notes. An unscoped screenshot is not enough.

Worked examples

1. All tracks resolved → READY_FOR_RELEASE

Paid use is licensed, a gifted-product disclosure is conspicuous in the creative, platform evidence is fresh, brand profile fits the inventory, and jurisdiction/reviewer are explicit.

2. Disclosure hidden behind “more” → HOLD_DISCLOSURE

A material connection exists and disclosure text exists, but visibility fails. Platform eligibility cannot override this.

3. Organic license, paid amplification → HOLD_RIGHTS

The creative is unchanged but the usage context changed. Re-run the rights gate; do not copy baseline clearance.

4. Advertiser-friendly but rights evidence missing → HOLD_RIGHTS

The platform track passes while the rights track has no decisive evidence. Release remains blocked.

5. Second jurisdiction with legal ambiguity → LEGAL_REVIEW_HOLD

Do not universalize one jurisdiction's guidance. Escalate to an authorized human reviewer.

6. Stricter brand profile → HOLD_BRAND_SUITABILITY

The platform permits the placement, but the new brand profile excludes that inventory/theme.

Common failure modes

• treating advertiser-friendly as legal clearance;
• treating platform acceptance as rights clearance;
• storing disclosure text without visibility/placement proof;
• reusing an organic license for paid media;
• dropping jurisdiction from the release gate;
• reusing stale platform-policy review;
• assuming content-suitability controls cover all inventory;
• confusing platform brand-safety floors with brand-specific suitability;
• converting UNKNOWN into PASS;
• using model confidence to resolve legal ambiguity;
• copying a baseline verdict after placement/jurisdiction/profile changes;
• dropping evidence references to simplify workflow.

Alternatives and trade-offs

Single compliance checkbox: fast, but not auditable and hides authority boundaries.

Platform-only status: operationally useful, but does not resolve rights, disclosure, or brand-specific controls.

Legal-only review: may cover legal risk but does not necessarily prove platform coverage or brand placement suitability.

Four-track gate: more overhead, but failures remain local and transfer is cheaper: re-run only changed gates while preserving unchanged evidence.

Experienced-review bridge: 17 questions

1. Which campaign and creative does this gate snapshot cover?
2. Who is the creator?
3. What relationship type exists?
4. Is material connection present, absent, or unknown?
5. What is the disclosure text reference?
6. Where is the disclosure presented?
7. Does the visibility check pass in the real placement?
8. What is the rights-clearance reference?
9. Does the license cover paid/organic, territory, duration, and placement?
10. Which platform and placement are in scope?
11. Which policy version/review date is evidenced?
12. Which brand-suitability profile version applies?
13. What inventory and exclusions apply?
14. Which jurisdiction is in scope?
15. Does the reviewer role have adequate authority?
16. Which track is actually blocked or stale?
17. On transfer, which evidence can be preserved and which gates must be recomputed?

Guided and independent practice

The offline lab contains eight fixtures: baseline release, hidden disclosure, organic-to-paid rights mismatch, platform-safe with missing rights, jurisdiction ambiguity, stricter brand profile, stale platform evidence, and a correct transfer that preserves unchanged evidence.

Independent task: move the baseline creative to a paid placement in a second jurisdiction and apply a stricter brand profile. Update only evidence that truly changed, then explain why the baseline verdict is not an oracle.

Acceptable evidence

The artifact must populate all 21 dimensions or emit an explicit non-success state. Release requires compatible rights, conspicuous disclosure when required, scoped platform evidence, brand profile, jurisdiction, reviewer, and reconstructable evidence references.

The lab is synthetic and offline. It requires no credentials, live ad account, customer data, or real legal decision.

Assessment and transfer

To complete the lesson, you must be able to:

1. separate COM-025 from COM-024 and COM-026;
2. build the four evidence tracks independently;
3. trace material connection and conspicuous disclosure;
4. compare license scope with actual usage;
5. avoid treating platform suitability as legal/rights clearance;
6. escalate jurisdiction ambiguity to human review;
7. keep brand profile and inventory evidence versioned;
8. recompute organic→paid/jurisdiction/profile transfer without copying the baseline verdict.

References and freshness

• FTC Disclosures 101 for Social Media Influencers — rechecked 2026-09-15; supports material-connection and conspicuous-disclosure guidance. It is U.S.-specific, not universal legal advice.
• Google Ads About content suitability — rechecked 2026-09-15; supports suitability controls, inventory coverage, and known limitations. It is platform-specific, not legal or rights clearance.
• Four-track separation, typed states, LEGAL_REVIEW_HOLD, and release policy are MAKNOW DESIGN.