[bokelley]

Makes the optional AdCP-owned 3.2 gender agreement self-contained in the stable targeting guide. The 3.3 coherence decision removes the gender ext.adcp binding and its documentation from main, so this guide no longer links to that removed section or promises a published gender namespace schema.

Cooperating 3.2 buyers and sellers explicitly negotiate demographics.gender.v1, advertise product-scoped native capabilities, preserve exact requested/applied readback, and apply the existing custom gender-policy mechanism. The vocabulary includes female, male, and non_binary, with explicit independent unknown membership and rejection of unsupported or approximate execution. The agreement remains optional and documentation-only; 3.2 core remains age-only.

Migration uses the experimental 3.3 core surface from #7925. This does not introduce a second representation into 3.3, a baseline 3.2 requirement, a new source-schema binding, or a released artifact/version change.

Validation: all 14 schema-tagged examples on the stable page pass; the snippet checker reports no failures (41 non-executable blocks skipped). Normal commit hooks and both typechecks pass (including the hook's successful serial retry of an existing statistical diagnostic that hit its time ceiling under parallel load). Fresh stable CI follows the pushed head.

Rebased onto current 3.2.x. Keep draft and do not merge while #7925 and release-manager landing order remain pending. No changeset, package, source schema, registry, or dist/ changes.

Draft disposition — 2026-10-09

• Existing author: @bokelley.
• Workstream / hold: Existing dependency stack; stack dependency.
• Next action: Hold until feat(schema): add experimental portable core gender targeting #7925 merges to main; then confirm the linked contract exists before this 3.2.x backport lands.

This draft is retained for the stated workstream. Continue on this existing branch; no parallel PR is needed. This disposition does not waive CI, review, migration, or release gates.

[aao-secretariat]

Ladon verdict: Escalate to human review

Escalate — new optional capability added to a stable maintenance line requires human review.

This docs-only PR adds a 227-line section to the stable 3.2.x targeting guide (docs/media-buy/advanced-topics/targeting.mdx) documenting a brand-new optional ext.adcp gender-targeting agreement. While mechanically clean — the demographics.age core shape validates, targeting.json is additionalProperties:true so ext.adcp.demographics.gender is valid open-ext JSON (no schema drift), anchors/cross-links resolve, naming/brand/character conventions are clean, and fail-closed semantics (UNSUPPORTED_FEATURE before mutation, ext preserved in signing/idempotency hashes) are correct — the substance is a new normative capability, not errata.

Per the repo's patch-eligibility rule, a new field / new normative requirement on a stable schema line is not patch-eligible and is treated as a non-editorial, breaking-class decision. Introducing an entirely new optional-capability spec to a stable maintenance guide is a protocol-policy decision whose decision-class and patch-eligibility call is a human act (constitution: Breaking/Normative-class changes are never auto-approved absent review_decision: APPROVED). review_decision is unknown/none here, so the gate is not satisfied.

Medium finding

• docs/media-buy/advanced-topics/targeting.mdx:30 — 227-line new optional-capability spec added to the stable 3.2.x maintenance guide

Escalation reasons

• New optional gender-targeting capability (bis, not errata) added to the stable 3.2.x maintenance line — patch/decision-class eligibility is a human ratification call, not auto-approvable.

Follow-up (low, non-blocking): the stable guide hard-links to blob/main (L37), mutable content the PR itself notes is in flux.

Medium findings

• docs/media-buy/advanced-topics/targeting.mdx:30 — 227-line new optional-capability spec added to the stable 3.2.x maintenance guide

Why human review

• New optional gender-targeting capability (bis, not errata) added to the stable 3.2.x maintenance line — decision-class/patch-eligibility is a human ratification call per the constitution's never-auto-approve bar for non-editorial normative changes; review_decision is not APPROVED.