What procurement notices has the issuing body mofa.gov.bd uploaded, and what printed fields does each carry?

Procurement notices by issuing body. Part of what the twin can answer. Every figure below is the value the route serves, with its source; the raw response is at /api/twin/brain/objfam/body/mofa.

Descriptive, sourced: no model

Basis: sourced records (URL, sha256 or locator per row), no model.

scanned PDFs and parsed procurement documents

mofa.gov.bd: procurement documents by kind

Kind	Documents
Tender notice	Documents: 8

Kind	Family printed	Method	Printed date	Memo	Package	Upload folder	Pages
Tender notice	Family printed: Invitation for Tender	Method: OTM

Source	Publisher	Unit	Caveat
Text-layer scan of the stored files from government portals (gap row A1)	Publisher: each document's stored PDF (PyMuPDF text layer, pages 1-3)	Unit: one row per text-layer PDF: general kind keyword, family match, personal screen, phone count; source file is relative to the archive disk root	Caveat: Only verdict=text PDFs are scanned; legacy-encoding, undecodable and image-only PDFs are counted in the remainder, never scanned. Kind keywords match Unicode Bangla in logical order or English; visual-order extracts miss, so an absent kind is not evidence of none.

Document text: Never stored in the lake or served; fields are located by page and line.
Person names and phone numbers: No name or phone field exists in either table; phones are counted at the build (phones_detected), never stored. Screened-out documents appear only as exclusion counts by reason.
A2 oracle_wave spec values: LLM-derived; used only as pointers to design the keyword patterns, never stored or served.
Non-text-layer PDFs and non-PDF files: Not scanned in this lane; counted in the remainder for later lanes.