procurement_coverage_cells: 48
This data as json
| rowid | source_key | source_label | record_kind | record_kind_label | fy_key | state | n_records | prev_n_records | why_code | why_text | evidence_kind | evidence_sql | evidence_citation | evidence_lf_id | probed_for_publication | is_crawl_dependent | drill_url | computed_at | run_id |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 48 | gvibuy_requisitions | GVIBuy requisitions | requisition | Requisitions - the step every purchase order descends from | not-applicable | NOT HELD | 0 | 0 | no-requisition-layer | The warehouse holds no requisition records of any kind, in either system, in any year. Only the outputs of the requisition process are here - solicitations, purchase orders and contracts. GVIBuy's public search offers no requisition entity, and the REQ- numbers printed on purchase-order line items had no public page in anything we looked at, but nobody ran a deliberate probe for a publication route, so probed_for_publication is 0 and no claim is made that none exists. This surface therefore starts one step downstream of where the decisions get made, and how many requisitions were raised, rejected or abandoned is not measurable from what is published. The identifiers themselves ARE held, on the requisition-identifier row of this matrix - 3,284 distinct requisition numbers read off the line items of the documents we hold. An identifier is not the document it names, and this cell is about the document. | MEASURED | SELECT COUNT(*) FROM sqlite_master WHERE type = 'table' AND lower(name) LIKE '%requisition%' | 0 | 0 | /procurement/coverage#why-no-requisition-layer | 2026-11-21T22:40:46Z | 2026-11-21T22:36:15Z |