Skip to main content
Use this fictional pack to rehearse source setup and merchandising before sharing real publisher material. It contains no customer data and uses reserved .invalid domains. Files may arrive independently; accepting one file does not imply that another lifecycle stage is implemented or ready.
Only the avails files labeled static-avails-feed:v1 are production-importable, and only through that compatibility parser. Every other file is supporting evidence, a manual pilot input, or an evaluation fixture—not a generalized production schema.

Choose the examples you need

This is a reference library, not a checklist that every customer must complete. Start with the examples that match the inputs your connected provider does not supply and the lifecycle stages included in the pilot.

Copy the files

Each code block has a copy control. Save the copied content under the filename shown in its heading. The first two files should each preview with two accepted rows and no rejected rows or warnings.

CTV avails — avails-ctv.csv

Display avails — avails-display.csv

Completed static-avails example

Save as publisher-avails-completed.csv. It covers net capacity, gross minus upstream-booked capacity, and numeric suffixes.

Invalid diagnostic fixture — avails-invalid.csv

These three rows deliberately prove missing formats, forbidden legacy format identity, and missing Property declarations. Preview them, but never commit them.

Merchandising and lifecycle evidence

The following files are supporting evidence or manual pilot inputs. Copy each block into the filename shown; none is a generalized production importer.

Storefront profile — storefront-profile.json

Media kit — media-kit.md

Rate card — rate-card.csv

Playbook — playbook.md

Business Rules — business-rules.md

Creative specifications — creative-specifications.md

Optional CRM context

Save this example as crm-account-context.csv after using the code-block copy control:
The CRM example is not inventory, availability, booking authority, a canonical buyer account, or a production import schema. It illustrates the stable CRM account and opportunity references, product or package references, stage, amount, outcome context, ownership role, and timestamps that can help rehearse buyer-specific merchandising. Begin with a field dictionary and a few sanitized rows; agree mapping and handling before sending a larger export.

Booking export — booking-export.csv

Reporting export — reporting-export.csv

Proposal test corpus — briefs.json

Independent evaluation instructions — agent-evaluation-prompt.md

Test-harness manifest — manifest.json

This manifest routes the fictional files for Scope3’s maintained test harness. It is included so an evaluator can confirm the expected source boundaries and projected IDs. Customers do not create this file for their own onboarding.

Rehearsal guidance

Customers do not author manifests or SHA-256 digests.