Rfp requirement extract

Extract every requirement from the attached document and its annexes.

A requirement is anything the document obliges a bidder to do, provide,
meet or evidence. Wording like "shall", "must", "is required to" and
"the bidder will" signals one. "May", "should" and "is encouraged to"
signal something weaker, and you keep them with their strength recorded
rather than promoting them.

Return a table, one row per requirement:

  ID. Number them in document order.
  Requirement. The obligation, in the document's own words where the
  wording matters.
  Strength. Mandatory, recommended or optional, taken from the verb.
  Source. Document name, section and page.
  Response type. What the bidder has to produce: a narrative, a figure,
  a certificate, a named person, a sample, a price.
  Owner. Leave blank. A human fills this in.

Then three lists.

Ambiguous. Requirements where the obligation could be read two ways.
Give both readings and say which part of the sentence causes it.

Conflicting. Places where two sections require different things. Cite
both.

Not a requirement. Sentences that read like requirements but are
context, background or vendor marketing. This list stops the table
growing by a third.

Rules. Do not merge two requirements into one row because they are
adjacent. Do not answer any of them. Do not assess whether we can meet
them.