Update from code changes: document PENDING EVIDENCE takedown status#96
Open
mintlify[bot] wants to merge 2 commits into
Open
Update from code changes: document PENDING EVIDENCE takedown status#96mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
Add the new
PENDING EVIDENCEtakedown status to the Takedowns concept page and the How-It-Works Takedown page.Changes
concepts/takedowns.mdx— listPENDING EVIDENCEunder Alternative Outcomes with its email/phone-number scope and 21-day auto-cancel behavior.getting-started/how-it-works/takedown.mdx— same addition, with slightly more detail on the pause semantics (no retractions, provider emails, or automations while in this state) and the daily auto-cancel job.Context
Follows chainpatrol/chainpatrol-web#7044, which introduced
PENDING_EVIDENCEfor email and phone-number takedowns. The external/takedowns/listtakedownStatusenum was intentionally not updated, so the API reference is unchanged.Note
Low Risk
Documentation-only updates to takedown lifecycle copy and meta descriptions; no runtime or API behavior changes in this repo.
Overview
Documentation now reflects the
PENDING EVIDENCEtakedown status introduced in product code, on both the Takedowns concept page and the How it works — Takedown page.Under Alternative Outcomes, each page adds PENDING EVIDENCE: the takedown pauses while ChainPatrol waits on externally supplied evidence; it applies only to email and phone-number assets; while in this state, retractions, provider outreach, and automations do not run (the how-it-works page also notes staff can move takedowns in or out of this state from any other status). Takedowns left in PENDING EVIDENCE for more than 21 days are auto-canceled by a daily job with an insufficient-evidence note.
Both files also get updated frontmatter descriptions for clearer SEO/summary text. No API reference changes are included in this diff.
Reviewed by Cursor Bugbot for commit 53def91. Bugbot is set up for automated code reviews on this repo. Configure here.