Repository navigation
Docs: edge, Exchange, transaction-log and dispute pages match the protocol - #83
Merged
Merged
Conversation
Delivery URLs are bound to the purchasing agent's key and a short window, and the edge records each delivery it authorizes in its delivery log; the edge, signed-URL and CDN adapter pages no longer describe single-use URLs. Signing keys belong to a tenant, which is its own Exchange with its own domain, key directory and keys, and signs every publisher it represents. Retroactive alteration of the transaction log is detectable even when the Exchange operator is the adversary, because the agent and the publisher's edge hold their own records; the storage layers are defense in depth. Dispute tiers are a recommended policy, with their time and share figures as design goals. The bot detection page states the reference edge's lists, settings and 403 body. The multi-tenant page drops application-level rate limits and price overrides and names Offer.signature. The Broker deployment page states its five-minute key cache. Pages that linked threat-model entries now state the protection or link the protocol section that defines it.
EugeneDymo
approved these changes
Nov 16, 2026
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.
Stacked on #81. Makes the edge, Exchange, transaction-log and dispute pages say what the protocol and the reference edge do.
signed_url_hash.BOT_UA_*_JSONsettings and the{error, reason}body, the publisher decides per crawler, and the example usespublisher.example.Offer.signaturereplacesexchange_signature.not_after.npm run build,npm test,npm run routes,routes:checkand doc conformance all pass. No page links to the threat model.