marketing-guidelines

Withdraw Requirement Downvote Route

Changed on

Remove this reviewer's downvote.

A missing vote is still 200: un-filling twice must not 404.

Hard-deletes the vote row. That is the exception to A-6, not a second kind of requirement removal: a downvote is a unique (requirement, user) signal, and withdrawing has to release the unique slot. Findings and the requirement itself are untouched.

delete/marketing/guidelines/requirements/{requirement_id}/downvote

Request

  • Base URL
    https://api.kobaltlabs.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.kobaltlabs.com/marketing/guidelines/requirements/{requirement_id}/downvote
  • Auth
    none declared

Path parameters

requirement_idstring uuid required

Response

Successful Response

requirement_idstring uuid required
downvote_countinteger required
downvoted_by_meboolean required
live_state'active' | 'disabled' | 'archived' | 'superseded' | 'proposed' required

Whether a requirement is in the working library, and if not, why not.

All of them are recorded as revisions, so every one is reversible and readable.

ARCHIVED and SUPERSEDED are deliberately distinct: ARCHIVED is a person deciding this obligation does not apply to them, SUPERSEDED is a newer decomposition of the same guideline taking over. A regeneration must never overwrite the first with the second — that would erase a human decision.

Changes

    • warning

      added the new proposed enum value to the response property for the response status