docs(compliance): add sales-specialism decision tree#4041
Draft
docs(compliance): add sales-specialism decision tree#4041
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #4038
Sell-side adopters had no single source of truth for choosing a
sales-*specialism — the only path was to read every storyboard narrative and triangulate. A wrong claim wastes the adopter's first compliance run by grading them against storyboards their architecture doesn't support.This PR adds a
## Choosing a sales specialismthree-step decision tree (<Steps>) tocompliance-catalog.mdx, placed after### brandand before## How to claim. The tree resolves adopters tosales-broadcast-tv,sales-catalog-driven,sales-social,sales-guaranteed, orsales-non-guaranteed; covers the multi-specialism case (hybrid guaranteed + auction platforms); and explains themedia_buy.supports_proposalscapability flag withjsoncwire examples. It also correctssales-proposal-modestatus fromstable→deprecatedin four files (compliance-catalog.mdx,learning/specialist/media-buy.mdx,learning/tracks/publisher.mdx,build-an-agent.mdx), and fixes a pre-existingcreative-hosting→creative-ad-servertypo inget-test-ready.mdx.Non-breaking justification: adds a new doc section and corrects status labels/example JSON; no schema, storyboard, or enum values changed. Existing clients unaffected.
Pre-PR review:
jsonfences →jsonc; two learning-docs files showedsales-proposal-modeasstable)sales-guaranteed;build-an-agent.mdxTip block still said "proposal mode"); also moved section to correct##-level position after all###specialism subsectionsNits (not blocking, left for human reviewer):
Set media_buy.supports_proposals (sales-guaranteed only)mixes case conventions — can be polished toConfigure media_buy.supports_proposalsSession: https://claude.ai/code/session_017tXWUzFaMeS77vRFinT25W