Skip to content

Run the limited display publisher rollout and rollback exercise #108

Open

Description

@aram356

Acceptance Criteria

  • Verify actual bidder credentials/parameters, consent and identity enforcement, fresh reference data, ad-server targeting and creative rendering, then admit bounded real traffic with stop thresholds.
  • Observe artifact/config rollback and recovery; publish bounded non-sensitive results and evidence invalidation rules. This passing selected path unlocks M7.7, not unrelated feature or target claims.

Blocking And Review Gates

  • Blocked by: #99, #100.
  • External blockers: Actual publisher rollout authorization, bidder credentials/setup and rollback access.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions