Skip to content

Unpublish the threat model page - #81

Merged
EugeneDymo merged 3 commits into
mainfrom
docs/unpublish-threat-model
Nov 16, 2026
Merged

EugeneDymo merged 3 commits into
mainfrom
docs/unpublish-threat-model

Conversation

@KonstantinMirin

@KonstantinMirin KonstantinMirin commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Takes the threat model page off the site until a reviewed version is ready. Merge together with #82, which removes the last references to it from the protos and SDK tests.

  • Page and redirect. Deletes security/threat-model.mdx and redirects /security/threat-model/ to /protocol/authentication/ with a 301, in website/redirects.json. /security/ held only this page.
  • Links and ids. Removes every link to the page and every old threat id (T2–T21, T-LIC-1) from the docs:
    • licensing terms and the CoMP extension state the SSRF guards inline;
    • the Broker deployment table keeps the threat names;
    • the transaction-log pages drop the ids;
    • the "Review the Threat Model" next step is removed.
  • Unchanged. Past changelog entries stay as history.

npm run build, npm test, npm run routes, routes:check (nothing retired without a redirect) and doc conformance all pass.

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.
Docs: edge, Exchange, transaction-log and dispute pages match the protocol
@EugeneDymo
EugeneDymo merged commit 9c84ccf into main Nov 16, 2026
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants