impact

Stale Scan

Flag this org's artifacts affected by a spec moving on — a version bump, or an RFC being obsoleted by another.

Three outcomes per artifact, and the distinction matters: · the clause was reworded -> stale, and we record where it now lives, so it can be regenerated in one click; · the clause was removed -> stale, and NOT regenerable: there is nothing to write a test against, so we say so instead of inventing a target; · the clause was carried over into a new document (only possible across an RFC obsolescence) -> stale only because it now lives in a different RFC; regenerating re-anchors the test to its new home.

post/artifacts/stale-scan

Request

  • Base URL: https://api.specproof.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.specproof.ai/artifacts/stale-scan
  • Auth: none declared

Headers

X-Org-Idstring nullable
authorizationstring

Request body

spec_basestring nullable
from_versionstring nullable
to_versionstring nullable
from_docinteger nullable
to_docinteger nullable

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 1 revision of this API.