sponsor-catalog

Sponsor Catalog

Core principle

Treat sponsor content as coordinated production configuration. Discover the current surfaces, verify operational claims, and update every still-served catalog schema that can safely represent the campaign.

Workflow

For an audit or review, use discovery and relevant compatibility guidance to report findings and coverage without editing, staging, or committing. Read public documentation or check ordinary non-affiliate links when needed to establish the findings; affiliate probing follows the campaign-facts rule below. The update and delivery steps apply only to authorized changes.

1. Inspect repository state and current ownership before editing.

   • Run git status --porcelain and preserve unrelated work.
   • Search for the sponsor name, domain, or asset to identify affected listings and catalogs. Read matching entries first; inspect runtime owners under src/features/AccountManagement/sponsors/ and the catalog test when schema or behavior matters.
   • Discover every served public/sponsor-catalog*.json when catalog content is in scope; inspect neighboring sponsors when ordering or established presentation matters.
   • Consult recent sponsor commits when current surfaces leave scope or compatibility unclear. Read a relevant rollout only when the needed historical decision is not established by current files or commits.

2. Load compatibility guidance when software or public JSON is in scope.

   • Read references/catalog-compatibility.md before choosing schema coverage, support status, actions, or rank.
   • Prefer current code, public artifacts, tests, and release tags over stale design documents.

3. Separate campaign facts from product integration facts.

   • Preserve user-supplied copy, affiliate URLs, and promotion terms in production surfaces only.
   • Verify any inferred site type, authentication type, API base URL, key-console URL, or direct-support claim against the target deployment, upstream source, or current repository behavior.
   • Keep the affiliate destination separate from operational URLs. Do not derive an API base URL or account origin from a marketing link.
   • Do not probe live affiliate URLs unless the user requests it.