# B2B platform evidence requests

## REQ_RECORD_SHAPE

- Owner: record owner
- Evidence needed: one top-level b2b_platform_decision/v1 object with required object and scalar kinds

## REQ_BUYER

- Owner: demand generation or revenue owner
- Evidence needed: named roles, company scope, geography and approved buyer reference

## REQ_BUYING_MOMENT

- Owner: campaign strategist
- Evidence needed: one supported buying moment and dated evidence

## REQ_OFFER

- Owner: offer or content owner
- Evidence needed: approved offer, format and production owner

## REQ_DESTINATION

- Owner: web or form owner
- Evidence needed: exact destination and successful controlled submission receipt

## REQ_CONSENT

- Owner: privacy or data-use owner
- Evidence needed: approved audience/data use and evidence reference

## REQ_FOLLOW_UP

- Owner: revenue operations
- Evidence needed: CRM object, route owner and controlled routing receipt

## REQ_MEASUREMENT

- Owner: measurement owner
- Evidence needed: source, platform, destination and CRM receipt definitions with cutoff and review deadline

## REQ_CANDIDATES

- Owner: campaign strategist
- Evidence needed: documented candidates for the evidenced route, one selected primary route, one secondary HOLD and a change condition

## REQ_ACCOUNT_OBSERVATION

- Owner: platform operator
- Evidence needed: observed date, exact account identity, value, unit, cutoff and evidence reference for the selected route

## REQ_PILOT_CONTRACT

- Owner: campaign owner and operator
- Evidence needed: owner-approved budget, dates, learning question, audience rules, confirmed operator capacity, reviewer and stop, repair and expansion conditions

## REQ_ACTION_AUTHORIZATION

- Owner: authorized campaign owner
- Evidence needed: explicit action authorization state, owner and evidence reference; decision readiness is not launch permission

## REQ_POST_LAUNCH_RECEIPTS

- Owner: measurement owner
- Evidence needed: source, platform, destination and CRM receipts bound to the same account, campaign and cutoff