Freeze publisher requirements and authorize the execution environment #52

Acceptance Criteria

• Select the publisher/bidder set and actual target, approve isolated config bindings, fixture origin, credentials handling, meters, mutation authorization and known-good restore inputs.
• Check required stored requests, identity, currency, native/AMP/video, GPP and browser features. Bring forward a reviewed owning prerequisite when needed; non-video alone is not readiness. Publish no secrets/customer data in the issue.

Blocking And Review Gates

• Blocked by: #34.
• External blockers: Publisher requirements, dedicated nonproduction deployment/config bindings and explicit authorization for credentials handling, mutation and restoration.

Use native blocked-by/blocking links for unconditional issue relationships. Conditional target gates are not universal blockers; link only the selected applicable path after its contract is frozen.

Shared Acceptance Requirements

Every implementation issue ships its own unit/conformance, failure, resource and privacy tests. A later integration issue does not postpone those checks. New untrusted decoders include generated hostile-input controls; changed hot paths include repeatable measurements. Use the existing engine, host services, validated config/push path and EdgeZero handler registration. Preserve privacy, authorization, cookie integrity, HTTPS/SSRF protections, deadlines, exact sent coverage, authoritative bidder/alias attribution and bounded work/storage. Standalone and embedded behavior share policy rather than fork implementations.

No issue may claim a missing capability from metadata import, compilation, observed allocations, a signed cookie, or a different artifact's old evidence. New public/configuration behavior requires its reviewed design before execution. No workload reduction, raised ceiling or replacement budget equation is implied. Bodies and evidence must not publish credentials, identifiers, raw consent, private provider addresses or customer configuration.

Technical Ownership

Sources: roadmap sections 6 and 8 and the existing M6 contracts/runbooks.

Source Contracts

• Approved roadmap
• Product vision
• Issue ledger and qualification limitations
• Schema qualification record