Sign in
marketing-guidelines

List Requirement Changes

What re-readings have proposed doing to rules already in the library.

Defaults to the pending ones, which is the worklist; the resolved ones are readable by asking for them, because "what did the reviewer decide about that proposal" is a question the history of a compliance library has to be able to answer.

Each row carries the rule as it stands beside what the reading would write, which is the comparison the reviewer is making. The live revision is read per row rather than joined so the identity lock discipline every other writer here follows is not silently bypassed by a read that happens to be cheaper.

get/marketing/guidelines/requirement-changes

Query parameters

guideline_set_idstring uuid nullable
file_idstring uuid nullable
proposal_status'pending' | 'accepted' | 'rejected'

Where a proposed change has got to.

PENDING is the only status the partial unique index counts, so a requirement carries at most one open proposal at a time and a second reading cannot stack a contradictory one behind it.

Response

Successful Response

Changes

Changed in 1 of the 5 revisions of this API.1