procurement_coverage_cells: 57
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 57 | gvibuy_po_detail | GVIBuy purchase-order detail pages | header-detail | Detail-page header fields (dollar limit, spend to date, release authority, requisition number) | not-applicable | PARTIAL | 4391 | 4391 | detail-layer-held-against-a-bounded-list | The list view GVIBuy publishes carries none of these fields; they exist only on each document's own detail page, one HTTP request each, made by a detail crawl that runs separately from the weekly walk of the list. We hold 4,391 of the 4,393 documents the purchase-order list returned. This cell is PARTIAL rather than HELD for three reasons, all measured, and the first of them is the crawl. 4 documents in the list carry a document number a detail request can be built from and have not been fetched, so this cell is marked as waiting on the crawl. 1 document in the list has no detail page here and a purchase-order number that does not begin with a letter; this surface does not treat that as a requestable document number and makes no claim about whether GVIBuy serves a page for it. And the list itself is one walk on one day: GVIBuy's own type-filtered searches return 0 documents that the unfiltered walk did not, so they are in no cell of this matrix and are not in this denominator either. What the fetched layer does settle is the department question - a contract's header department and the department authorised to release against it are now separate fields on every document we hold, and the surface no longer has to merge them. | MEASURED | SELECT COUNT(*) FROM gvibuy_po_header_detail | 1 | 1 | /procurement/chain?source=gvibuy_po_detail&kind=header-detail&fy=not-applicable | 2026-11-21T22:40:46Z | 2026-11-21T22:36:15Z |