Which oracle_wave spec pointers point at a printed contract-award price that the raw PDF text layer actually carries, and what is the match rate?

Oracle award prices. 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/oraclespecs.

Descriptive, sourced: no model

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

Specs are pointers, never sources: a value row exists only because the raw PDF text layer carries the printed price, located by page and line, with the stored bytes re-hashed against the inventory sha256.

machine-read, verified against PDF text

Specs in the four award-notice families: 84
With a printed price found in the PDF: 68
Match rate: 80.9524%
PDF-verified price lines: 70

The verified money

Largest printed price: Tk 62.75 crore
Smallest printed price: Tk 122,500.00
Sum of the printed price lines: Tk 383.40 crore; sum over served printed price lines; a notice can print its price on more than one page, so this is not a sum of distinct contracts
Pointers that print more than one price line: 1
Most price lines one pointer prints: 3

The specs that found no price

Why no price was served, of 84 specs in the families

Reason	Specs
Price label unparsable	Specs: 10
No award price label	Specs: 5
Not taka unit	Specs: 1

By text encoding of the spec

Match by spec encoding

Encoding	Specs	Matched
Unicode ok	Specs: 69	Matched: 64
Ocr noise	Specs: 15	Matched:

By award-notice family

Match by family

Family	Specs	Matched	sha256 verified	Content keys intact
Contract award notice	Specs: 33	Matched: 25	sha256 verified: 33

Who procured

The most frequent procuring-entity strings, exactly as the notices print them

Procuring entity, as printed	Pointers
Expansion of Teletalks network up to rural areas and	Pointers: 14
Teletalk Bangladesh Limited	Pointers: 7
Expansion of Teletalks network up to rural areas and Network

How every value was verified

Pointers whose PDF bytes matched the inventory sha256: 84
Content keys intact from spec to build: 84
Receipt lines served: 70
Receipt lines withheld: 0
Text-layer reader used for every pointer: pdftotext
Spec rows scanned in all: 36,267

The pointer register

Every award-notice pointer, 50 rows from offset 50 of 84

Pointer	Family	Encoding	Price found in the PDF	Reason no price	Procuring entity, as printed	Date of notification of award	Source PDF
77f533cb373f6b75	Family: Tender award notice

Where these figures come from

The spec scan and the raw harvested PDFs behind every figure above

Source	Published by	What it is	Caveat
`oracle_wave` LLM spec extractions of the A1 objectstorage PDFs (gap row A2)	Published by: LLM spec wave over `oracle_wave` (36,267 spec files in `spec_out`; `spec_claims_muse` and `spec_claims_muse2` hold no files); used only as pointers to where a value sits	What it is: one spec line per harvested document chunk: , family, encoding, table descriptions with parser gates; no data values

Not held

Spec values not found in the PDF: A spec pointer whose award price does not appear verbatim in the raw PDF text layer is never served; the pointer table carries the counted reason (no_award_price_label, price_label_unparsable, not_taka_unit).
USD contract prices: The claim family is taka; the one USD-labelled price is excluded rather than converted with an unstored FX rate.
Phone numbers and person-adjacent fields: Receipt lines are screened at build; a hit drops the line and keeps the value (matched_line_withheld names the reason). This build had zero hits.
Absolute server paths: source_file is relative to the archive disk root; production holds no copy of the disk.