Spec: auction provider refactor - #1016
Open
ChristianPavilonis wants to merge 2 commits into
Open
Conversation
ChristianPavilonis
force-pushed
the
docs/config-first-auction-provider-spec
branch
from
August 11, 2026 23:42
8de9eab to
0c98095
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The current architecture combines provider identity, routing, request construction, transport, and response interpretation inside static Prebid Server and Amazon Publisher Services implementations. This design establishes clear ownership boundaries and a central bidder-to-provider routing model so future implementation work can proceed against an agreed contract.
Changes
docs/superpowers/specs/2026-08-10-config-first-auction-provider-architecture-design.mdScope
This is intentionally a documentation-only pull request. It records the complete architecture decision in one design document because provider configuration, routing, profile ownership, and compatibility requirements must be reviewed together. It does not change runtime code, configuration parsing, or auction behavior; implementation will follow separately.
Closes
No linked issue. This pull request records the approved architecture before implementation work begins.
Test plan
cargo test-fastly && cargo test-axum— not applicable; no Rust changescargo clippy-fastly && cargo clippy-axum— not applicable; no Rust changescargo fmt --all -- --check— not applicable; no Rust changescd crates/trusted-server-js/lib && npx vitest run— not applicable; no JavaScript changescd crates/trusted-server-js/lib && npm run format— not applicable; no JavaScript changescd docs && npm run format— local dependencies are not installedcargo build --package trusted-server-adapter-fastly --release --target wasm32-wasip1— not applicable; no runtime changesfastly compute serve— not applicable; no runtime changescd docs && npx --yes prettier@3.4.2 --check superpowers/specs/2026-08-10-config-first-auction-provider-architecture-design.mdChecklist