[NOTICKET] eval(knowledge): commit the BUMA fixture artifact; K9/K10 close

The 2026-08-27T13:28 re-parse of STD_2026_006_MNO becomes the committed
fixture (S7/K10). Same document and content_hash as the 08-26 parse, same
parser_config, five corrected chunk boundaries — of which ::0030 is the one
that matters: it previously held only "Keterangan grafik:" and now carries the
hierarchy-level paragraph, moving Controllable / Hierarki Level Analysis from
E1 miss to hit.

One paid run on it (90 calls, 170 s): E1 0.8293 / E2 2.556x / E3 1.000, all
three above their kill lines, rule recall 0.4286 (6/14). 0 fields rejected by
the span check, rules_without_term_link 0.

Two caveats recorded beside the numbers rather than left for a reader to
rediscover: E3's precision 1.000 sits on a scoreable base of 6 (57 of 63
entries abstain, recall 0.33 against the 18 gold terms with criteria), and the
rule-recall delta is partly a denominator change — the same 6 rules matched as
in the 08:29 run, the gold base went 15 to 14 when X23 closed.

The harness now runs with data/knowledge_docs/ absent and MinerU not
installed, which is the seam doing its job.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

DEV_PLAN.md

@@ -319,15 +319,16 @@ A live 3-call pilot on `gpt-5.4-nano` returned correct Indonesian definitions wi
 rejections and 7,168 of 8,029 prompt tokens served from cache.
 
 **Not done, and not to be read as done:** no persistence (stage output is JSON on disk — D2 still
-owes Harry a DDL block), no HTTP surface, no full-document extraction run, and **E3 has never been
-scored on v2** — the one experiment that failed in the prototype.
+owes Harry a DDL block) and no HTTP surface. ~~no full-document extraction run, and **E3 has never
+been scored on v2**~~ — **RESOLVED 2026-08-27 (K9):** the full-document run is routine now and E3
+scores **1.000** on a committed fixture; see the K9 row for how to read that number.
 
 | # | Task | Owner | Status | Note |
 |---|---|---|---|---|
 | P1 | Freeze the `kex` prototype (read-only snapshot) | Rifqi | ✅ | **2026-08-19: kept as-is, unversioned — Rifqi's call.** Risk accepted, and much reduced once P2/P3 lifted the two things that could not be recreated |
 | P2 | Harvest the prototype's tuned constants | Rifqi | ✅ | **Done** → `KNOWLEDGE_PIPELINE_CALIBRATION.md`, 10 sections: every value with the reason it has that value, plus §7 negative findings and §9/§10 the deviations made while rebuilding |
 | P3 | Migrate the evidence into `eval/knowledge/` | Rifqi | ✅ | **Done.** Gold set (41 terms + 15 rules), ported scorer, frozen baseline. Migration proved faithful: the ported scorer re-derives the prototype numbers exactly |
-| S1 | Agree the parsed-artifact schema | Sofhia + Rifqi | ✅ | **Settled 2026-08-21.** `src/knowledge_parsing/contracts.py` (`schema_version 0.2.0`) is the shape of record and the extraction adapter consumes it directly. Envelope, verbatim heading, 0-based `page_idx`, prose `text` with `latex`/`table_html` beside it |
+| S1 | Agree the parsed-artifact schema | Sofhia + Rifqi | ✅ | **Settled 2026-08-21.** `src/knowledge_parsing/contracts.py` (`schema_version 0.2.0`; **0.3.0** as of the 2026-08-27 fixture) is the shape of record and the extraction adapter consumes it directly. Envelope, verbatim heading, 0-based `page_idx`, prose `text` with `latex`/`table_html` beside it |
 | S5 | Keep the seam off the file path | Sofhia + Rifqi | ✅ | **Satisfied both sides.** `ParsedDocument` carries no handle to the parser, and `knowledge_extraction.adapter` accepts only the artifact. Locked by local seam tests importing the parsing contract directly |
 | X* | Build extraction v2 in this repo | Rifqi | ✅ | **Done 2026-08-21** — `src/knowledge_extraction/`: adapter · filters (span/cue/legend) · cluster · rank · extract (4 branches) · validate · diff · queue · service facade · CLI. Recall matches the frozen baseline exactly |
 | D2 | Artifact + candidate-entry persistence | Rifqi → Harry | ⬜ | **The main gap.** Stage output is JSON on disk today. Parsed artifacts, candidate entries, glossary versions + approval audit trail all still need one consolidated Harry-ready DDL block; Go owns dedorch DDL (§2.2) |
@@ -337,8 +338,8 @@ scored on v2** — the one experiment that failed in the prototype.
 | D5 | v2 module name | Rifqi | ✅ | **`src/knowledge_extraction/`**, beside Sofhia's `src/knowledge_parsing/`. Neither collides with the existing `src/knowledge/` OCR→pgvector service, which is untouched |
 
 | D1 | New dependencies | Rifqi | ✅ | **Added 2026-08-21.** `rapidfuzz`, `gliner`, `torch>=2.6` as main deps; **`mineru==3.4.4` as an optional extra** (`.[knowledge-parsing]`) so the deployed Space never builds it. See the §6 open decision — the same argument arguably applies to gliner/torch |
-| K9 | Full-document extraction run + score E3 on v2 | Rifqi | ⬜ | ~83 calls, ~$0.007. The one prototype experiment that FAILED (0.75 vs a 0.80 line) has never been scored on v2, and the ranking changes (calibration §9 V1/V2) are unmeasured |
-| K10 | Fixture artifact committed | Rifqi | ⬜ | Promote one real `ParsedDocument` into the repo so extraction is testable with MinerU not installed at all — the seam doing its job. Tracked as S7 in the checklist |
+| K9 | Full-document extraction run + score E3 on v2 | Rifqi | ✅ | **Done — latest run 2026-08-27** (`eval/knowledge/results/v2_full_2026-08-27_133757.json`, 90 calls, 170 s). E1 **0.8293** / E2 **2.556×** / E3 **1.000** — all three above their kill lines; rule recall 0.4286 (6/14, tracked not gated). **The prototype's failing experiment now passes**, but read E3 as *precision on a scoreable base of 6*: 57 of 63 entries abstain, so recall against the 18 gold terms with criteria is 0.33. 0 fields rejected by the span check |
+| K10 | Fixture artifact committed | Rifqi | ✅ | **Done 2026-08-27** — `eval/knowledge/fixtures/parsed_STD_2026_006_MNO.json` (BUMA standard, MinerU 3.4.4 `hybrid`, `schema_version 0.3.0`, 31 chunks). The eval and the extraction CLI both run with MinerU absent. The Open Pit textbook fixture is still open (S7 in the checklist) |
 | K11 | Output schema v2 (Harry's contract review) | Rifqi | 🔎 | **Landed 2026-08-26, unevaluated.** Deterministic entity ids, glossary references formulas instead of restating them, rules link to formulas and terms, 16 fields cut (50 → 42). Contract: [docs/knowledge/KNOWLEDGE_OUTPUT_CONTRACT.md](docs/knowledge/KNOWLEDGE_OUTPUT_CONTRACT.md); detail in the checklist as X24. Fixed two live defects — neither `cluster_id` (a frequency ordinal) nor `rule_id` (model-written) survived a re-run, which breaks an expert's approvals, not just links. Suite 497 passed / 7 skipped; **no eval run** — the prompt edits join X20's in the unevaluated queue |
 
 **Not decided, do not assume:** whether the admin ingest surface is HTTP at all (the offline CLI is

docs/knowledge/KNOWLEDGE_PIPELINE_TODO.md

@@ -20,10 +20,12 @@
 > now carries **three unevaluated prompt changes**: X20's bare-equation fix, X23's unresolved
 > prompt-vs-gold conflict capping it at 14/15, and X24's new `rule_type`.
 >
-> **The eval cannot currently run on this dev box** — `data/knowledge_docs/`, `data/knowledge_cache/`
-> and `data/knowledge_runs/` are all gitignored and absent, MinerU is not installed, and there is no
-> `eval/knowledge/run_eval.py` (the 2026-08-24 run was assembled ad-hoc). Restoring one parsed
-> artifact unblocks X20's measurement.
+> **Updated 2026-08-27 — the eval now runs on this dev box.** `run_eval.py` landed on 2026-08-26 and
+> a parsed artifact of the BUMA standard is **committed** as
+> `eval/knowledge/fixtures/parsed_STD_2026_006_MNO.json` (S7), so the harness runs with
+> `data/knowledge_docs/` absent and MinerU not installed — the seam doing its job. Latest run:
+> `results/v2_full_2026-08-27_133757.json` — E1 **0.8293**, E2 **2.556×**, E3 **1.000**, rule recall
+> **0.4286** (6/14), 0 span rejections.
 
 ---
 
@@ -113,7 +115,7 @@ verbatim-text warning that independently identifies the same failure mode as the
 | **S4** | Add `source_wording` while the contract is open | Rifqi → Sofhia | ✅ | **Done 2026-08-19.** `source_wording` added to `TermRecord`, and `heading` is carried verbatim — so "Physical **of** Availability" survives instead of being silently normalised (R1). |
 | **S5** | Keep the seam off the file path | Sofhia + Rifqi | ✅ | **Satisfied both sides 2026-08-21.** `ParsedDocument` carries no handle to the parser; the adapter accepts only the artifact (or a plain dict) and has no path argument at all |
 | **S6** | Minor contract items (deferred to review) | Rifqi → Sofhia | 🔄 | **Four of six closed 2026-08-19; two need a joint call.** **(b) page indexing — OPEN:** the artifact uses `page_idx`/`page_idxs`, **0-based**, no conversion anywhere, so it always matches the raw MinerU output kept beside it; converting to 1-based is the UI's job, done once at display. Say if you want a 1-based `page_no` added instead, since this number reaches Mas Beta. **(a) formatting signal — OPEN, but the premise was wrong:** `text_format` is emitted by *both* backends and is not a formatting signal at all — it is the constant `'latex'` on equation blocks. Checked further: MinerU carries **no emphasis information anywhere** (zero `**` in its markdown, no style/font/span keys in `middle.json`). So the signal has no source in MinerU; it would need a separate pass reading the PDF directly (PyMuPDF exposes per-span bold flags). Recommend dropping it from the ranker for now — one of six signals, and adding a PDF pass buys nothing measured yet. Your ranker, your call. **(c) chunk size — done:** ~1500-token cap, matching calibration §4; splits at item boundaries so text stays verbatim. **(d) `chapter` lossy — done:** now `chapters: list[str]`, one per page the chunk spans. **(e) pydantic — done.** **(f) `TermRecord`** — left to you; the declaration in `contracts.py` is a placeholder, not a claim. |
-| **S7** | Commit fixture artifacts | Rifqi | ⬜ | Both source PDFs exist (BUMA standard + Open Pit textbook). Promote a parsed artifact of each into the target repo as committed fixtures, so the extraction half is testable **with MinerU not installed at all** — the seam doing its job |
+| **S7** | Commit fixture artifacts | Rifqi | 🔄 | **BUMA done 2026-08-27** → `eval/knowledge/fixtures/parsed_STD_2026_006_MNO.json` (MinerU 3.4.4 `hybrid`, `schema_version 0.3.0`, 31 chunks, `content_hash f10807…`). It is the 2026-08-27T13:28 re-parse, not the 08-26 one: same document and hash, five corrected chunk boundaries, of which `::0030` is the one that matters — it previously held only `"Keterangan grafik:"` and now carries the hierarchy-level paragraph, moving `Controllable` / `Hierarki Level Analysis` from E1 miss to hit. **Open Pit textbook fixture still ⬜.** Extraction is now testable **with MinerU not installed at all** |
 | **S8** | Write the seam rule into the repo docs | Rifqi | ✅ | **Done 2026-08-21.** REPO_STATUS §14 states it as a rule, and `src/knowledge_parsing/README.md` carries the three easy-to-get-wrong properties. The prototype drifted from this rule once; it is now written where a newcomer meets it |
 
 ---

eval/knowledge/README.md

@@ -19,8 +19,9 @@ ships first and every v2 stage is measured from its first commit rather than ret
 
 | Path | What it is |
 |---|---|
-| `knowledge_gold.yaml` | 41 terms + 15 rules. **Provisional** — bootstrapped by reading the source PDF, *not* expert-reviewed |
+| `knowledge_gold.yaml` | 41 terms + 14 rules. **Provisional** — bootstrapped by reading the source PDF, *not* expert-reviewed |
 | `score.py` | Precision / recall / F1 per branch. Pipeline-independent: takes plain lists of surfaces and entry dicts, so it scores the prototype's artifacts and v2 alike |
+| `fixtures/parsed_STD_2026_006_MNO.json` | **Committed fixture artifact (2026-08-27, S7/K10).** The BUMA standard parsed by MinerU 3.4.4 `hybrid`, `schema_version 0.3.0`, 31 chunks. Every score below is measured on it, and it is what makes this harness runnable **with MinerU not installed** |
 | `results/baseline_prototype_2026-08-13_145132.json` | **Frozen.** The prototype's measured numbers. Never regenerate — add new timestamped files beside it |
 
 `run_eval.py` — **the runner. Added 2026-08-26**, following the house convention (module mode,
@@ -31,7 +32,8 @@ timestamped results, never overwritten) used by `eval/{intent,help,readiness,pla
 
 **It takes a `ParsedDocument` artifact, never a PDF — MinerU is not invoked and is not required.**
 That is the seam doing its job: point it at the `chunks.json` written by
-`python -m src.knowledge_parsing.run`.
+`python -m src.knowledge_parsing.run` — or at the committed fixture, which needs no parser at all:
+`eval/knowledge/fixtures/parsed_STD_2026_006_MNO.json`.
 
 ```bash
 # free — E1 recall, E2 compression, the funnel. No API calls, no spend
@@ -74,6 +76,26 @@ Measured by the prototype on the document above, run `20260813-145132`, deployme
 Funnel: 9 pages → 13 chunks → 169 mentions → 66 clusters → 83 LLM calls → 66 entries → 66 queue
 items. Cost $0.0069; 125,184 of 155,313 prompt tokens served from cache.
 
+### Where v2 stands — `results/v2_full_2026-08-27_133757.json`
+
+Measured on the committed fixture, deployment `gpt-5.4-nano`, one run:
+
+| Experiment | Result | Kill line | Verdict | vs `v2_full_document_2026-08-24_093051.json` |
+|---|---|---|---|---|
+| **E1** term-filter recall | **0.8293** | 0.70 | **PASS** | +0.0244 |
+| **E2** compression | **2.556×** | 2.0 | **PASS** | −0.254 |
+| **E3** glossary schema fill (precision) | **1.0000** | 0.80 | **PASS** | +0.10 |
+| **rule recall** | **0.4286** (6/14) | — tracked | — | +0.2286 |
+
+Funnel: 9 pages → 31 chunks → 186 mentions → 63 clusters → 90 LLM calls → 63 glossary + 15 rule +
+6 formula entries. 153,318 prompt tokens, 98,816 cached (64%); 0 fields rejected by the span check;
+`rules_without_term_link` 0.
+
+**Two caveats to carry when quoting these.** E3's precision 1.00 sits on a **scoreable base of 6** —
+57 of 63 entries abstain with a null definition, so recall against the 18 gold terms with criteria is
+0.33. And the rule-recall delta is partly a denominator change: the same **6** rules matched as in
+the 2026-08-27 08:29 run, but the gold base went 15 → 14 when X23 was closed on the expert ruling.
+
 ## Two things the scorer refuses to do
 
 **It never conflates term-filter recall with extraction precision.** They are different failure

eval/knowledge/fixtures/parsed_STD_2026_006_MNO.json

@@ -0,0 +1,1081 @@
+{
+  "doc_id": "STD_2026_006_MNO",
+  "chunks": [
+    {
+      "chunk_id": "STD_2026_006_MNO::0000",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "BUMA | STANDARD PARAMETER\nProduction Parameter and Equipment Capacity Analysis (ECA)\nDisusun,\nDian Titisari\nManager - Mine Budget & Control | Disetujui,\nIndro Apriyono\nGroup GM - Engineering | No. Dokumen:\nMNO/2026/006/STD\nRevisi: 0.0\nTanggal Berlaku: 1 Agustus 2026 | Jumlah Halaman: 9",
+      "page_idx": 0,
+      "page_idxs": [
+        0
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        0
+      ],
+      "bbox": [
+        45,
+        30,
+        951,
+        250
+      ],
+      "images": [
+        "images/ee0f7fdc76c760453b377d1b98340a5401034d188151e955a73fca6d9cbb10b5.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td>BUMA</td><td colspan=\"3\">STANDARD PARAMETER\nProduction Parameter and Equipment Capacity Analysis (ECA)</td></tr><tr><td rowspan=\"2\">Disusun,\nDian Titisari\nManager - Mine Budget &amp; Control</td><td rowspan=\"2\" colspan=\"2\">Disetujui,\nIndro Apriyono\nGroup GM - Engineering</td><td>No. Dokumen:\nMNO/2026/006/STD</td></tr><tr><td>Revisi: 0.0</td></tr><tr><td colspan=\"2\">Tanggal Berlaku: 1 Agustus 2026</td><td colspan=\"2\">Jumlah Halaman: 9</td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0001",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "Historikal Perubahan\n\nTanggal Revisi | Nomor Revisi | Isi Perubahan\n--- | --- | ---\nBUMA | STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA) | No. Dokumen : MNO/2026/006/STD\nNo. Revisi : 0.0\nHalaman : 2 / 9",
+      "page_idx": 0,
+      "page_idxs": [
+        0
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        1
+      ],
+      "bbox": [
+        48,
+        282,
+        949,
+        336
+      ],
+      "images": [
+        "images/3ed35ff7e06224556f3ed8f2176f7db3603543333c24c9c13db54e96041fec44.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td>Tanggal Revisi</td><td>Nomor Revisi</td><td>Isi Perubahan</td></tr><tr><td>---</td><td>---</td><td>---</td></tr><tr><td rowspan=\"3\">BUMA</td><td rowspan=\"3\">STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA)</td><td>No. Dokumen : MNO/2026/006/STD</td></tr><tr><td>No. Revisi : 0.0</td></tr><tr><td>Halaman : 2 / 9</td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0002",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Standard Parameter ini merupakan pedoman dalam perhitungan parameter produksi yang meliputi Quantity (Qty) Physical Availability (PA), Utilization of Availability (UA), Productivity (PTY), serta Equipment Capacity Analysis (ECA). Standar ini digunakan sebagai acuan dalam pengukuran, analisis, dan pengendalian kinerja operasiona penambangan guna memastikan pencapaian target produksi secara aman, efektif, dan efisien.",
+      "page_idx": 1,
+      "page_idxs": [
+        1
+      ],
+      "section_no": "1",
+      "heading": "TUJUAN PARAMETER",
+      "chapters": [],
+      "heading_path": [
+        "1. TUJUAN PARAMETER"
+      ],
+      "has_formula": false,
+      "is_tabular": false,
+      "source_items": [
+        3,
+        4
+      ],
+      "bbox": [
+        48,
+        120,
+        247,
+        134
+      ],
+      "images": [],
+      "latex": [],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0003",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Adalah serangkaian kegiatan yang dilakukan untuk menciptakan nilai tambah terhadap sumber daya melalui proses pengolahan atau pemindahan sehingga menghasilkan produk yang memiliki nilai ekonomis dan dapat memenuhi kebutuhan.\n\nDalam konteks industri pertambangan, produksi merupakan seluruh rangkaian kegiatan operasional penambangan yang dimulai dari land clearing, pengupasan lapisan penutup (overburden removal), penambangan batubara (coal mining), pengangkutan batubara (coal hauling/coal transporting), hingga proses pengapalan (coal barging atau ship loading), yang bertujuan menghasilkan volume produksi sesuai target serta memberikan nilai tambah dan kontribusi terhadap pendapatan (revenue) Perusahaan.\n\nSecara umum, Production dihitung menggunakan rumus berikut:\n\nProduction = MOHH × Qty × PA × UA × Pty\n\nKeterangan:\n\nMOHH : Machine on Hand Hours\n\nQty : Quantity\n\nPA : Physical Availability\n\nUA : Utilization of Availability\n\nPty : Productivity",
+      "page_idx": 1,
+      "page_idxs": [
+        1
+      ],
+      "section_no": "2.1.1",
+      "heading": "Production",
+      "chapters": [],
+      "heading_path": [
+        "2.1.1. Production"
+      ],
+      "has_formula": true,
+      "is_tabular": false,
+      "source_items": [
+        7,
+        8,
+        9,
+        10,
+        11,
+        12,
+        13,
+        14,
+        15,
+        16,
+        17
+      ],
+      "bbox": [
+        124,
+        293,
+        272,
+        306
+      ],
+      "images": [],
+      "latex": [
+        "$$\nP r o d u c t i o n = M O H H \\times Q t y \\times P A \\times U A \\times P t y\n$$"
+      ],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0004",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Adalah jumlah equipment/unit yang digunakan untuk menghasilkan produksi dalam suatu periode. Nilai quantity dihitung berdasarkan proporsi waktu setiap equipment/unit berstatus in operation (INPR) terhadap total jam pada periode tersebut, sehingga mencerminkan jumlah equipment/unit efektif yang tersedia untuk mendukung kegiatan produksi.\n\nSecara umum, Qty dihitung menggunakan rumus berikut:\n\nQty = (INPR Hours) / (Total Hours)",
+      "page_idx": 1,
+      "page_idxs": [
+        1
+      ],
+      "section_no": "2.1.2",
+      "heading": "Quantity (Qty)",
+      "chapters": [],
+      "heading_path": [
+        "2.1.2. Quantity (Qty)"
+      ],
+      "has_formula": true,
+      "is_tabular": false,
+      "source_items": [
+        18,
+        19,
+        20,
+        21
+      ],
+      "bbox": [
+        124,
+        725,
+        297,
+        741
+      ],
+      "images": [],
+      "latex": [
+        "$$\nQ t y = \\frac {I N P R H o u r s}{T o t a l H o u r s}\n$$"
+      ],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0005",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "BUMA | STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA) | No. Dokumen : MNO/2026/006/STD\nNo. Revisi : 0.0\nHalaman : 3 / 9",
+      "page_idx": 2,
+      "page_idxs": [
+        2
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.1.2. Quantity (Qty)"
+      ],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        23
+      ],
+      "bbox": [
+        47,
+        32,
+        951,
+        105
+      ],
+      "images": [
+        "images/06dd4ec5b7eaa4db8e7dd9ac6f722778ee1fc66505cb250e437118996f0fc562.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td rowspan=\"3\">BUMA</td><td rowspan=\"3\">STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA)</td><td>No. Dokumen : MNO/2026/006/STD</td></tr><tr><td>No. Revisi : 0.0</td></tr><tr><td>Halaman : 3 / 9</td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0006",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Contoh Perhitungan:\n\nDiketahui:\n\nPada bulan Juni total 30 hari → 30 x 24 hrs = 720 hrs\n\nEX2500 beroperasi selama 15 hari → 15 x 24 hrs = 360 hrs\n\nDitanya: Quantity (Qty)\n\nJawab:\n\nQty = (INPR Hours) / (Total Hours)\n\nQty = (360) / (720) ; = 0, 5 unit ;\n\nMaka, Quantity (Qty) unit EX2500 sebesar 0.5 unit.\n\nPerhitungan quantity (Qty) disesuaikan dengan kategori aktivitas operasional (activity) meliputi Waste Removal (WR), Coal Mining (CM), Coal Transport (CT), General Work, dan Rental.\n\nOleh karena itu, perhitungan Quantity (Qty) dilakukan secara terpisah untuk setiap kategori aktivitas.\n\nRumus perhitungan untuk setiap kategori aktivitas adalah sebagai berikut:\n\nQty_activity = (INPR Hours_activity) / (Total Hours)\n\nDimana klasifikasi aktivitas operasional tersebut ditentukan berdasarkan status equipment/unit yang tercatat pada raw data Time Performance MCD Application.\n\nUntuk Qty Grouping (Composite), perhitungan dilakukan dengan menjumlahkan nilai Qty dari seluruh tipe atau kelas (type/class) equipment/unit.",
+      "page_idx": 2,
+      "page_idxs": [
+        2
+      ],
+      "section_no": "2.1.2",
+      "heading": "Quantity (Qty)",
+      "chapters": [],
+      "heading_path": [
+        "2.1.2. Quantity (Qty)"
+      ],
+      "has_formula": true,
+      "is_tabular": false,
+      "source_items": [
+        26,
+        27,
+        28,
+        29,
+        30,
+        31,
+        32,
+        33,
+        34,
+        35,
+        36,
+        37,
+        38,
+        39,
+        40,
+        41
+      ],
+      "bbox": [
+        124,
+        159,
+        297,
+        175
+      ],
+      "images": [],
+      "latex": [
+        "$$\nQ t y = \\frac {I N P R H o u r s}{T o t a l H o u r s}\n$$",
+        "$$\n\\begin{array}{l} Q t y = \\frac {3 6 0}{7 2 0} \\\\ = 0, 5 \\text {unit} \\\\ \\end{array}\n$$",
+        "$$\nQ t y _ {a c t i v i t y} = \\frac {I N P R H o u r s _ {a c t i v i t y}}{T o t a l H o u r s}\n$$"
+      ],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0007",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "BUMA | STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA) | No. Dokumen : MNO/2026/006/STD\nNo. Revisi : 0.0\nHalaman : 4 / 9",
+      "page_idx": 3,
+      "page_idxs": [
+        3
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.1.2. Quantity (Qty)"
+      ],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        43
+      ],
+      "bbox": [
+        47,
+        32,
+        951,
+        105
+      ],
+      "images": [
+        "images/d8562a4349b7fe976d9065a119dedeaa37b2eab77015cf559b82ef5b5845adb7.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td rowspan=\"3\">BUMA</td><td rowspan=\"3\">STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA)</td><td>No. Dokumen : MNO/2026/006/STD</td></tr><tr><td>No. Revisi : 0.0</td></tr><tr><td>Halaman : 4 / 9</td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0008",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Adalah ketersediaan fisik suatu equipment/unit yang menunjukkan proporsi waktu equipment/unit tersebut berada pada kondisi available (siap pakai) selama suatu periode tertentu.\n\nSecara umum, PA dihitung menggunakan rumus berikut:\n\nPA = ( Total Hours - Breakdown ) / ( Total Hours ) × 100 %\n\nPerhitungan Physical Availability (PA) untuk Grouping (Composite), baik pada tingkat tipe unit (i) nomor unit (j), dilakukan dengan menggunakan rumus dasar sebagai berikut:\n\nPA_ij = ( _ij Total Hours_ij - _ij Breakdown_ij) / ( _ij Total Hours_ij) × 100 %\n\nNilai Physical Availability (PA) hasil perhitungan di atas ekuivalen dengan rata-rata tertimbang (weight average) nilai PA masing-masing type/class unit dengan Quantity (Qty) sebagai faktor pembobot.",
+      "page_idx": 3,
+      "page_idxs": [
+        3
+      ],
+      "section_no": "2.1.3",
+      "heading": "Physical of Availability (PA)",
+      "chapters": [],
+      "heading_path": [
+        "2.1.3. Physical of Availability (PA)"
+      ],
+      "has_formula": true,
+      "is_tabular": false,
+      "source_items": [
+        46,
+        47,
+        48,
+        49,
+        50,
+        51,
+        52
+      ],
+      "bbox": [
+        124,
+        159,
+        391,
+        174
+      ],
+      "images": [],
+      "latex": [
+        "$$\n\\mathrm{PA} = \\frac {\\text {Total Hours} - \\text {Breakdown}}{\\text {Total Hours}} \\times 100\\%\n$$",
+        "$$\n\\mathrm{PA} _ {i j} = \\frac {\\sum_ {i j} \\text {Total Hours} _ {i j} - \\sum_ {i j} \\text {Breakdown} _ {i j}}{\\sum_ {i j} \\text {Total Hours} _ {i j}} \\times 100\\%\n$$"
+      ],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0009",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Adalah tingkat efektifitas penggunaan suatu alat yang tersedia secara fisik yang menunjukkan seberapa lama suatu unit digunakan secara efektif untuk bekerja – working hours selama berada dalam kondisi siap dioperasikan (available).\n\nSecara umum, UA dihitung menggunakan rumus berikut:\n\nUA = ( Working Hours ) / ( Total Hours - Breakdown )\n\nPerhitungan performance UA Grouping (Composite) type/class unit diperoleh dari hasil pembobotan UA masing-masing type/class unit hanya dengan Quantity-nya.\n\nUA_ij = ( _ij Qty_ij UA_ij) / ( _ij Qty_ij)\n\nNote : UA disesuaikan berdasarkan kategori aktivitas operasional (activity).",
+      "page_idx": 3,
+      "page_idxs": [
+        3
+      ],
+      "section_no": "2.1.4",
+      "heading": "Utilization of Availability (UA)",
+      "chapters": [],
+      "heading_path": [
+        "2.1.4. Utilization of Availability (UA)"
+      ],
+      "has_formula": true,
+      "is_tabular": false,
+      "source_items": [
+        53,
+        54,
+        55,
+        56,
+        57,
+        58,
+        59
+      ],
+      "bbox": [
+        124,
+        531,
+        411,
+        546
+      ],
+      "images": [],
+      "latex": [
+        "$$\nU A = \\frac {\\text {Working Hours}}{\\text {Total Hours} - \\text {Breakdown}}\n$$",
+        "$$\n\\mathrm{UA} _ {i j} = \\frac {\\sum_ {i j} \\mathrm{Qty} _ {i j} \\mathrm{UA} _ {i j}}{\\sum_ {i j} \\mathrm{Qty} _ {i j}}\n$$"
+      ],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0010",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "BUMA | STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA) | No. Dokumen : MNO/2026/006/STD\nNo. Revisi : 0.0\nHalaman : 5 / 9",
+      "page_idx": 4,
+      "page_idxs": [
+        4
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.1.4. Utilization of Availability (UA)"
+      ],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        61
+      ],
+      "bbox": [
+        47,
+        32,
+        951,
+        105
+      ],
+      "images": [
+        "images/da4b7965980dcf848ff839414ce3d761c5491b94d02324a2fa0bd0ead33fae3c.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td rowspan=\"3\">BUMA</td><td rowspan=\"3\">STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA)</td><td>No. Dokumen : MNO/2026/006/STD</td></tr><tr><td>No. Revisi : 0.0</td></tr><tr><td>Halaman : 5 / 9</td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0011",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Adalah ukuran efektifitas penggunaan sumber daya (input) untuk menghasilkan hasil (output) secara optimal. Output dapat berupa volume produksi, luas kerja area yang diselesaikan, atau hasil kerja lainnya, sedangkan input dapat berupa waktu operasi, manpower, peralatan, maupun sumber daya lainnya yang digunakan dalam proses operasional.\n\nSecara umum, Pty dihitung menggunakan rumus berikut:\n\nProductivity = ( Production ) / ( Effective Working Hours )\n\nDimana:\n\nProduction yang digunakan dalam perhitungan adalah produksi hasil joint survey. Apabila data joint survey belum tersedia, maka digunakan data produksi berdasarkan truck count sebagai dasar perhitungan.\nWorking Hours yang digunakan dalam perhitungan parameter produksi adalah Effective Working Hours (EWH) atau productive working hours, yaitu waktu kerja efektif yang benarbenar digunakan untuk menghasilkan produksi.\n\nPerhitungan performance Pty Grouping (Composite) type/class equipment/unit diperoleh dari hasil pembobotan Pty masing-masing type/class unit hanya dengan Quantity-nya.\n\nPTY_ij = ( _ij Qty_ij PTY_ij) / ( _ij Qty_ij)",
+      "page_idx": 4,
+      "page_idxs": [
+        4
+      ],
+      "section_no": "2.1.5",
+      "heading": "Productivity (Pty)",
+      "chapters": [],
+      "heading_path": [
+        "2.1.5. Productivity (Pty)"
+      ],
+      "has_formula": true,
+      "is_tabular": false,
+      "source_items": [
+        64,
+        65,
+        66,
+        67,
+        68,
+        69,
+        70,
+        71
+      ],
+      "bbox": [
+        124,
+        159,
+        319,
+        174
+      ],
+      "images": [],
+      "latex": [
+        "$$\n\\text {Productivity} = \\frac {\\text {Production}}{\\text {Effective Working Hours}}\n$$",
+        "$$\n\\mathrm{PTY} _ {i j} = \\frac {\\sum_ {i j} \\mathrm{Qty} _ {i j} \\mathrm{PTY} _ {i j}}{\\sum_ {i j} \\mathrm{Qty} _ {i j}}\n$$"
+      ],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0012",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "BUMA | STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA) | No. Dokumen : MNO/2026/006/STD\nNo. Revisi : 0.0\nHalaman : 6 / 9",
+      "page_idx": 5,
+      "page_idxs": [
+        5
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.1.5. Productivity (Pty)"
+      ],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        73
+      ],
+      "bbox": [
+        48,
+        33,
+        951,
+        105
+      ],
+      "images": [
+        "images/54daf97c1034e0a4ae14b6e3b92a3da847d04c74850383c4160b69d7afc3e601.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td rowspan=\"3\">BUMA</td><td rowspan=\"3\">STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA)</td><td>No. Dokumen : MNO/2026/006/STD</td></tr><tr><td>No. Revisi : 0.0</td></tr><tr><td>Halaman : 6 / 9</td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0013",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Adalah salah satu alat (tool) analisis yang digunakan untuk mengidentifikasi penyebab ketidaktercapaian target produksi berdasarkan kapasitas produksi yang telah direncanakan. Analisis dilakukan dengan membandingkan nilai rencana (plan) dan realisasi (actual) dari setiap parameter produksi, yaitu Quantity (Qty), Physical Availability (PA), Utilization of Availability (UA), dan Productivity (PTY), sehingga diperoleh nila Gain/Loss dari masing-masing parameter sebagai dasar evaluasi kinerja dan penyusunan tindakan perbaikan.",
+      "page_idx": 5,
+      "page_idxs": [
+        5
+      ],
+      "section_no": "2.2",
+      "heading": "Equipment Capacity Analysis (ECA)",
+      "chapters": [],
+      "heading_path": [
+        "2.2. Equipment Capacity Analysis (ECA)"
+      ],
+      "has_formula": false,
+      "is_tabular": false,
+      "source_items": [
+        75,
+        76
+      ],
+      "bbox": [
+        78,
+        140,
+        394,
+        155
+      ],
+      "images": [],
+      "latex": [],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0014",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "Tabel 2.1 Perhitungan Gain/Loss per Model Unit\n\nParameter | Rumus\nGain/Loss Quantity (Qty) | Gain/Loss Qty_(M) = MOHH x (Qty_A(M) - Qty_P(M)) x PA_P(M) x UA_P(M) x Pty_P(M)\nGain/Loss Physical Availability (PA) | Gain/Loss PA_(M) = MOHH x Qty_A(M) x (PA_A(M) - PA_P(M)) x UA_P(M) x Pty_P(M)\nGain/Loss Utilization of Availability (UA) | Gain/Loss UA_(M) = MOHH x Qty_A(M) x PA_A(M) x (UA_A(M) - UA_P(M)) x Pty_P(M)\nGain/Loss Productivity (Pty) | Gain/Loss Pty_(M) = MOHH x Qty_A(M) x PA_A(M) x UA_A(M) x (Pty_A(M) - Pty_P(M))\nJika ( Qty_P(M) = 0, Qty_A(M) > 0 ), maka:\nGain/Loss Quantity (Qty) | Gain/Loss Qty_(M) = MOHH x (Qty_A(M) - Qty_P(M)) x PA_A(M) x UA_A(M) x Pty_A(M)",
+      "page_idx": 5,
+      "page_idxs": [
+        5
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.1. Perhitungan Gain/Loss per Model Unit"
+      ],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        78
+      ],
+      "bbox": [
+        48,
+        291,
+        947,
+        512
+      ],
+      "images": [
+        "images/89640953ff6e0adf4b192f7203332efb550c6f8d0ff8abdd66ff1d27dc5c365a.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td>Parameter</td><td>Rumus</td></tr><tr><td>Gain/Loss Quantity (Qty)</td><td> $Gain/Loss\\ Qty_{(M)} = MOHH\\ x\\ (Qty_{A(M)} - Qty_{P(M)})\\ x\\ PA_{P(M)}\\ x\\ UA_{P(M)}\\ x\\ Pty_{P(M)}$ </td></tr><tr><td>Gain/Loss Physical Availability (PA)</td><td> $Gain/Loss\\ PA_{(M)} = MOHH\\ x\\ Qty_{A(M)}\\ x\\ (PA_{A(M)} - PA_{P(M)})\\ x\\ UA_{P(M)}\\ x\\ Pty_{P(M)}$ </td></tr><tr><td>Gain/Loss Utilization of Availability (UA)</td><td> $Gain/Loss\\ UA_{(M)} = MOHH\\ x\\ Qty_{A(M)}\\ x\\ PA_{A(M)}\\ x\\ (UA_{A(M)} - UA_{P(M)})\\ x\\ Pty_{P(M)}$ </td></tr><tr><td>Gain/Loss Productivity (Pty)</td><td> $Gain/Loss\\ Pty_{(M)} = MOHH\\ x\\ Qty_{A(M)}\\ x\\ PA_{A(M)}\\ x\\ UA_{A(M)}\\ x\\ (Pty_{A(M)} - Pty_{P(M)})$ </td></tr><tr><td colspan=\"2\">Jika ( $Qty_{P(M)} = 0, Qty_{A(M)} > 0$ ), maka:</td></tr><tr><td>Gain/Loss Quantity (Qty)</td><td> $Gain/Loss\\ Qty_{(M)} = MOHH\\ x\\ (Qty_{A(M)} - Qty_{P(M)})\\ x\\ PA_{A(M)}\\ x\\ UA_{A(M)}\\ x\\ Pty_{A(M)}$ </td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0015",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Untuk menghitung Gain/Loss untuk setiap kategori standby menggunakan rumus berikut:",
+      "page_idx": 5,
+      "page_idxs": [
+        5
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.1. Perhitungan Gain/Loss per Model Unit"
+      ],
+      "has_formula": false,
+      "is_tabular": false,
+      "source_items": [
+        79
+      ],
+      "bbox": [
+        168,
+        530,
+        845,
+        546
+      ],
+      "images": [],
+      "latex": [],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0016",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "Tabel 2.2 Perhitungan Gain/Loss untuk Setiap Kategori Delay/Standby\n\nParameter | Rumus\nGap Delay/Standby | Gap Delay/Standby = (MOHH × PA_A(M) × (1 - UA_P(M))) / (Standby_P) - Standby_A\nGain/Loss | Gain/Loss = Gap Standby × (UA_A(M) - UA_P(M)) × Pty_P(M)\n\nCatatan: P(M): Plan Model, A(M): Actual Model, A: Actual, P: Plan, Gain/Loss menggunakan satuan BCM atau ton, Gap Standby menggunakan satuan jam (hours)",
+      "page_idx": 5,
+      "page_idxs": [
+        5
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.1. Perhitungan Gain/Loss per Model Unit"
+      ],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        80
+      ],
+      "bbox": [
+        50,
+        577,
+        947,
+        662
+      ],
+      "images": [
+        "images/4be9048846d30ceb73acd679538200bba561e67d248880500db8763ba7f0f267.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td>Parameter</td><td>Rumus</td></tr><tr><td>Gap Delay/Standby</td><td> $Gap\\ Delay/Standby = \\frac{MOHH \\times PA_{A(M)} \\times (1 - UA_{P(M)})}{Standby_P} - Standby_A$ </td></tr><tr><td>Gain/Loss</td><td> $Gain/Loss = Gap\\ Standby \\times (UA_{A(M)} - UA_{P(M)}) \\times Pty_{P(M)}$ </td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0017",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Gain/Loss grouping (composite) unit merupakan penjumlahan dari Gain/Loss model unit pada grup tersebut.",
+      "page_idx": 5,
+      "page_idxs": [
+        5
+      ],
+      "section_no": "2.2.2",
+      "heading": "Perhitungan Gain/Loss Grouping (Composite) dari Model Unit",
+      "chapters": [],
+      "heading_path": [
+        "2.2.2. Perhitungan Gain/Loss Grouping (Composite) dari Model Unit"
+      ],
+      "has_formula": false,
+      "is_tabular": false,
+      "source_items": [
+        81,
+        82
+      ],
+      "bbox": [
+        122,
+        711,
+        650,
+        726
+      ],
+      "images": [],
+      "latex": [],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0018",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "Tabel 2.3 Perhitungan Gain/Loss Grouping (Composite) dari Model Unit\n\nParameter | Rumus\nGain/Loss Qty Grouping (Composite) | Gain/Loss Qty_(G) = Gain/Loss Qty_(M)\nGain/Loss PA Grouping (Composite) | Gain/Loss PA_(G) = Gain/Loss PA_(M)\nGain/Loss UA Grouping (Composite) | Gain/Loss UA_(G) = Gain/Loss UA_(M)\nGain/Loss Pty Grouping (Composite) | Gain/Loss Pty_(G) = Gain/Loss Pty_(M)\n\nCatatan: (G): Grouping, (M): Model",
+      "page_idx": 5,
+      "page_idxs": [
+        5
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.2. Perhitungan Gain/Loss Grouping (Composite) dari Model Unit"
+      ],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        83
+      ],
+      "bbox": [
+        50,
+        804,
+        947,
+        942
+      ],
+      "images": [
+        "images/008c0d8c9584d7be0fa73b1082c511f8c6ecc2e2ce0f17820359a4828a720be0.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td>Parameter</td><td>Rumus</td></tr><tr><td>Gain/Loss Qty Grouping (Composite)</td><td> $Gain/Loss Qty_{(G)} = \\sum Gain/Loss Qty_{(M)}$ </td></tr><tr><td>Gain/Loss PA Grouping (Composite)</td><td> $Gain/Loss PA_{(G)} = \\sum Gain/Loss PA_{(M)}$ </td></tr><tr><td>Gain/Loss UA Grouping (Composite)</td><td> $Gain/Loss UA_{(G)} = \\sum Gain/Loss UA_{(M)}$ </td></tr><tr><td>Gain/Loss Pty Grouping (Composite)</td><td> $Gain/Loss Pty_{(G)} = \\sum Gain/Loss Pty_{(M)}$ </td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0019",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "BUMA | STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA) | No. Dokumen : MNO/2026/006/STD\nNo. Revisi : 0.0\nHalaman : 7 / 9",
+      "page_idx": 6,
+      "page_idxs": [
+        6
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.2. Perhitungan Gain/Loss Grouping (Composite) dari Model Unit"
+      ],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        85
+      ],
+      "bbox": [
+        48,
+        33,
+        951,
+        105
+      ],
+      "images": [
+        "images/4de976c76d71c77bd273c934ceb57599041fec9ae8fcca0c785b78419db74fa8.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td rowspan=\"3\">BUMA</td><td rowspan=\"3\">STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA)</td><td>No. Dokumen : MNO/2026/006/STD</td></tr><tr><td>No. Revisi : 0.0</td></tr><tr><td>Halaman : 7 / 9</td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0020",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "Tabel 2.4 Perhitungan Parameter Plan Grouping (Composite)\n\nParameter | Rumus\nQuantity (Qty) plan grouping (composite) adalah penjumlahan dari quantity per model | Qty_P(G) = Qty_P(M)\nPA plan grouping (composite) adalah PA per model dibobotkan dengan quantity per model | PA_P(G) = ( Qty_P(M) × PA_P(M)) / ( Qty_P(M))\nUA plan grouping (composite) adalah UA per model dibobotkan dengan quantity dan PA per model | UA_P(G) = ( Qty_P(M) × PA_P(M) × UA_P(M)) / ( Qty_P(M) × PA_P(M))\nPTY plan grouping (composite) adalah PTY per model dibobotkan dengan Qty, PA, UA per model | PTY_P(G) = ( Qty_P(M) × PA_P(M) × UA_P(M) × PTY_P(M)) / ( Qty_P(M) × PA_P(M) × UA_P(M))\n\nCatatan: (G): Grouping, (M): Model",
+      "page_idx": 6,
+      "page_idxs": [
+        6
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.3. Parameter Plan Grouping (Composite)"
+      ],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        89
+      ],
+      "bbox": [
+        50,
+        193,
+        947,
+        375
+      ],
+      "images": [
+        "images/bdddcf9f5cd73aa573cfc9fde224e7c88e38e483afbd5b155c41e40af0581209.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td>Parameter</td><td>Rumus</td></tr><tr><td>Quantity (Qty) plan grouping (composite) adalah penjumlahan dari quantity per model</td><td> $Qty_{P(G)} = \\sum Qty_{P(M)}$ </td></tr><tr><td>PA plan grouping (composite) adalah PA per model dibobotkan dengan quantity per model</td><td> $PA_{P(G)} = \\frac{\\sum Qty_{P(M)} \\times PA_{P(M)}}{\\sum Qty_{P(M)}}$ </td></tr><tr><td>UA plan grouping (composite) adalah UA per model dibobotkan dengan quantity dan PA per model</td><td> $UA_{P(G)} = \\frac{\\sum Qty_{P(M)} \\times PA_{P(M)} \\times UA_{P(M)}}{\\sum Qty_{P(M)} \\times PA_{P(M)}}$ </td></tr><tr><td>PTY plan grouping (composite) adalah PTY per model dibobotkan dengan Qty, PA, UA per model</td><td> $PTY_{P(G)} = \\frac{\\sum Qty_{P(M)} \\times PA_{P(M)} \\times UA_{P(M)} \\times PTY_{P(M)}}{\\sum Qty_{P(M)} \\times PA_{P(M)} \\times UA_{P(M)}}$ </td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0021",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "2.2.4. Perhitungan Parameter Actual pada Grouping (Composite) Berdasarkan Gain/Loss Production\n\nTujuan: Gain/Loss parameter grouping (composite) sama dengan total Gain/Loss parameter masingmasing model unit dan Gain/Loss grouping (compisite) mencerminkan pencapaian parameter terhadap plannya. Perhitungan ini digunakan untuk melakukan perbandingan terhadap nilai performance parameter produksi sebagai proses verifikasi (double check).",
+      "page_idx": 6,
+      "page_idxs": [
+        6
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.3. Parameter Plan Grouping (Composite)"
+      ],
+      "has_formula": false,
+      "is_tabular": false,
+      "source_items": [
+        90,
+        91
+      ],
+      "bbox": [
+        122,
+        413,
+        907,
+        428
+      ],
+      "images": [],
+      "latex": [],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0022",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "Tabel 2.5 Perhitungan Parameter Actual pada Grouping (Composite) Berdasarkan Gain/Loss Production\n\nParameter | Rumus\nQty grouping (composite) actual | Qty_A(G) = (Qty_P(G)) / (Prod_P(G)) MOHH × Qty_A(M) × PA_P(M) × UA_P(M) × Pty_P(M) Atau Qty_A(G) = (Gain/Loss Qty_(G)) / (MOHH × PA_P(G) × UA_P(G) × PTY_P(G)) + Qty_P(G) a. Jika Qty_A ≠ 0 dan Qty_P = 0 maka gunakan MOHH × Qty_A(M) × PA_A(M) × UA_A(M) × Pty_A(M) b. Pelaporan quantity fisik unit tetap dengan menjumlahkan fisik unit sesuai INPR hours\nPA grouping (composite) actual | PA_A(G) = (Qty_P(G) × PA_P(G)) / (Prod_P(G) × Qty_A(G)) MOHH × Qty_A(M) × PA_A(M) × UA_P(M) × Pty_P(M) Atau PA_A(G) = (Gain/Loss PA_(G)) / (MOHH × Qty_A(G) × UA_P(G) × PTY_P(G)) + PA_P(G)\nUA grouping (composite) actual | UA_A(G) = (Qty_P(G) × PA_P(G) × UA_P(G)) / (Prod_P(G) × Qty_A(G) × PA_A(G)) MOHH × Qty_A(M) × PA_A(M) × UA_A(M) × Pty_P(M) Atau UA_A(G) = (Gain/Loss UA_(G)) / (MOHH × Qty_A(G) × PA_A(G) × PTY_P(G)) + UA_P(G)\nPTY grouping (composite) actual | Pty_A(G) = (Qty_P(G) × PA_P(G) × UA_P(G) × Pty_P(G)) / (Prod_P(G) × Qty_A(G) × PA_A(G) × UA_A(G)) MOHH × Qty_A(M) × PA_A(M) × UA_A(M) × Pty_A(M) Atau Pty_A(G) = (Gain/Loss Pty_(G)) / (MOHH × Qty_A(G) × PA_A(G) × UA_A(G)) + Pty_P(G)\n\nCatatan: A(G): Actual Grouping, P(G): Plan Grouping, A(M): Actual Model, P(M): Plan Model",
+      "page_idx": 6,
+      "page_idxs": [
+        6
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.3. Parameter Plan Grouping (Composite)"
+      ],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        92
+      ],
+      "bbox": [
+        45,
+        533,
+        944,
+        942
+      ],
+      "images": [
+        "images/f289d92023aa8255252abef19e8e83fc6af68d791b18d5b2f7a7cd50d7e0b172.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td>Parameter</td><td>Rumus</td></tr><tr><td>Qty grouping (composite) actual</td><td> $Qty_{A(G)} = \\frac{Qty_{P(G)}}{Prod_{P(G)}} \\sum MOHH \\times Qty_{A(M)} \\times PA_{P(M)} \\times UA_{P(M)} \\times Pty_{P(M)}$ Atau  $Qty_{A(G)} = \\frac{Gain/Loss\\ Qty_{(G)}}{MOHH \\times PA_{P(G)} \\times UA_{P(G)} \\times PTY_{P(G)}} + Qty_{P(G)}$ a. Jika  $Qty_{A} \\neq 0$  dan  $Qty_{P} = 0$  maka gunakan $MOHH \\times Qty_{A(M)} \\times PA_{A(M)} \\times UA_{A(M)} \\times Pty_{A(M)}$ b. Pelaporan quantity fisik unit tetap dengan menjumlahkan fisik unit sesuai INPR hours</td></tr><tr><td>PA grouping (composite) actual</td><td> $PA_{A(G)} = \\frac{Qty_{P(G)} \\times PA_{P(G)}}{Prod_{P(G)} \\times Qty_{A(G)}} \\sum MOHH \\times Qty_{A(M)} \\times PA_{A(M)} \\times UA_{P(M)} \\times Pty_{P(M)}$ Atau  $PA_{A(G)} = \\frac{Gain/Loss\\ PA_{(G)}}{MOHH \\times Qty_{A(G)} \\times UA_{P(G)} \\times PTY_{P(G)}} + PA_{P(G)}$ </td></tr><tr><td>UA grouping (composite) actual</td><td> $UA_{A(G)} = \\frac{Qty_{P(G)} \\times PA_{P(G)} \\times UA_{P(G)}}{Prod_{P(G)} \\times Qty_{A(G)} \\times PA_{A(G)}} \\sum MOHH \\times Qty_{A(M)} \\times PA_{A(M)} \\times UA_{A(M)} \\times Pty_{P(M)}$ Atau  $UA_{A(G)} = \\frac{Gain/Loss\\ UA_{(G)}}{MOHH \\times Qty_{A(G)} \\times PA_{A(G)} \\times PTY_{P(G)}} + UA_{P(G)}$ </td></tr><tr><td>PTY grouping (composite) actual</td><td> $Pty_{A(G)} = \\frac{Qty_{P(G)} \\times PA_{P(G)} \\times UA_{P(G)} \\times Pty_{P(G)}}{Prod_{P(G)} \\times Qty_{A(G)} \\times PA_{A(G)} \\times UA_{A(G)}} \\sum MOHH \\times Qty_{A(M)} \\times PA_{A(M)} \\times UA_{A(M)} \\times Pty_{A(M)}$ Atau  $Pty_{A(G)} = \\frac{Gain/Loss\\ Pty_{(G)}}{MOHH \\times Qty_{A(G)} \\times PA_{A(G)} \\times UA_{A(G)}} + Pty_{P(G)}$ </td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0023",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "BUMA | STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA) | No. Dokumen : MNO/2026/006/STD\nNo. Revisi : 0.0\nHalaman : 8 / 9",
+      "page_idx": 7,
+      "page_idxs": [
+        7
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.3. Parameter Plan Grouping (Composite)"
+      ],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        94
+      ],
+      "bbox": [
+        47,
+        33,
+        951,
+        105
+      ],
+      "images": [
+        "images/39402751dd66fb7e11b16fffb576eabef4307f452ead790ad5d749d4e50818c6.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td rowspan=\"3\">BUMA</td><td rowspan=\"3\">STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA)</td><td>No. Dokumen : MNO/2026/006/STD</td></tr><tr><td>No. Revisi : 0.0</td></tr><tr><td>Halaman : 8 / 9</td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0024",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Analisis yang bertujuan menyajikan visualisasi dalam bentuk grafik Waterfall untuk menggambarkan kontribusi Gain/Loss dari setiap parameter produksi berdasarkan hasil perhitungan Gain/Loss Production.\n\nWaterfall Analysis dapat di-review melalui dua metode, yaitu:\n\n1. Analisis Gain/Loss berdasarkan setiap parameter produksi (Qty, PA, UA, dan(PTY), baik pada loader maupun hauler.",
+      "page_idx": 7,
+      "page_idxs": [
+        7
+      ],
+      "section_no": "2.2.5",
+      "heading": "Waterfall Analysis",
+      "chapters": [],
+      "heading_path": [
+        "2.2.5. Waterfall Analysis"
+      ],
+      "has_formula": false,
+      "is_tabular": false,
+      "source_items": [
+        97,
+        98,
+        99,
+        100
+      ],
+      "bbox": [
+        124,
+        159,
+        326,
+        174
+      ],
+      "images": [],
+      "latex": [],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0025",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "image",
+      "text": "Gambar 2.1 Analisis Gain/Loss Berdasarkan Setiap Parameter Produksi",
+      "page_idx": 7,
+      "page_idxs": [
+        7
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.5. Waterfall Analysis"
+      ],
+      "has_formula": false,
+      "is_tabular": false,
+      "source_items": [
+        101
+      ],
+      "bbox": [
+        215,
+        332,
+        771,
+        651
+      ],
+      "images": [
+        "images/a9f776c820128048f2c58f85014b78fe961a4cb7be0591d089d5b38ad016322b.jpg"
+      ],
+      "latex": [],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0026",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Keterangan:\n\nOther Activity adalah kondisi ketika alokasi equipment/unit pada pelaksanaan aktual tidak sesuai dengan aktivitas yang telah direncanakan.\n\nSebagai contoh, equipment/unit yang dialokasikan untuk kegiatan waste removal pada tahap perencanaan digunakan untuk kegiatan coal mining pada pelaksanaan aktual, atau sebaliknya.",
+      "page_idx": 7,
+      "page_idxs": [
+        7
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.5. Waterfall Analysis"
+      ],
+      "has_formula": false,
+      "is_tabular": false,
+      "source_items": [
+        102,
+        103,
+        104
+      ],
+      "bbox": [
+        184,
+        699,
+        280,
+        713
+      ],
+      "images": [],
+      "latex": [],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0027",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "table",
+      "text": "BUMA | STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA) | No. Dokumen : MNO/2026/006/STD\nNo. Revisi : 0.0\nHalaman : 9 / 9",
+      "page_idx": 8,
+      "page_idxs": [
+        8
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.5. Waterfall Analysis"
+      ],
+      "has_formula": false,
+      "is_tabular": true,
+      "source_items": [
+        106
+      ],
+      "bbox": [
+        47,
+        33,
+        951,
+        105
+      ],
+      "images": [
+        "images/7e317972900c08d59046ba5353f5fce04033a357830180ae7e92f15e3f5cf56b.jpg"
+      ],
+      "latex": [],
+      "table_html": "<table><tr><td rowspan=\"3\">BUMA</td><td rowspan=\"3\">STANDARD PARAMETERProduction Parameter andEquipment Capacity Analysis (ECA)</td><td>No. Dokumen : MNO/2026/006/STD</td></tr><tr><td>No. Revisi : 0.0</td></tr><tr><td>Halaman : 9 / 9</td></tr></table>",
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0028",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Waterfall Analysis dapat di-review melalui dua metode, yaitu:\n\n2. Analisis Gain/Loss pada setiap komponen time management berdasarkan Hierarki Level Analyisis.",
+      "page_idx": 8,
+      "page_idxs": [
+        8
+      ],
+      "section_no": "2.2.5",
+      "heading": "Waterfall Analysis",
+      "chapters": [],
+      "heading_path": [
+        "2.2.5. Waterfall Analysis"
+      ],
+      "has_formula": false,
+      "is_tabular": false,
+      "source_items": [
+        109,
+        110,
+        111
+      ],
+      "bbox": [
+        124,
+        159,
+        326,
+        174
+      ],
+      "images": [],
+      "latex": [],
+      "table_html": null,
+      "generated_description": null
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0029",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "image",
+      "text": "Gambar 2.2 Analisis Gain/Loss pada Setiap Komponen Time Management Berdasarkan Hierarki Level Analysis",
+      "page_idx": 8,
+      "page_idxs": [
+        8
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.5. Waterfall Analysis"
+      ],
+      "has_formula": false,
+      "is_tabular": false,
+      "source_items": [
+        112
+      ],
+      "bbox": [
+        169,
+        262,
+        897,
+        407
+      ],
+      "images": [
+        "images/86b3567c6f623a477c442654a5968ff44d2c05a838778d5b6fe85579bdf4d62f.jpg"
+      ],
+      "latex": [],
+      "table_html": null,
+      "generated_description": "This waterfall chart illustrates the factors contributing to production actuals, distinguishing between uncontrollable and controllable scenarios."
+    },
+    {
+      "chunk_id": "STD_2026_006_MNO::0030",
+      "doc_id": "STD_2026_006_MNO",
+      "kind": "text",
+      "text": "Keterangan grafik:\n\nUncontrollable dan controllable merupakan kategori pada Hierarki Level Analyisis pada level 1 (satu).\n• Weather, Hazard, Customer, Qty & Other, PA Loader, UA Controllable, dan PTY merupakan kategori pada Hierarki Level Analyisis pada level 2 (dua).\nUraian pada grafik batang pada level 2 (dua) menampilkan beberapa isu utama (Gain/Loss) yang berasal dari Hierarki Level Analyisis pada level 3 (tiga). Sebagai contoh, kategori UA Controllable diuraikan ke dalam grafik batang yang terdiri atas fleet management, mineplan, UA Impact PA Truck, UA Impact PA Support, dll.",
+      "page_idx": 8,
+      "page_idxs": [
+        8
+      ],
+      "section_no": null,
+      "heading": null,
+      "chapters": [],
+      "heading_path": [
+        "2.2.5. Waterfall Analysis"
+      ],
+      "has_formula": false,
+      "is_tabular": false,
+      "source_items": [
+        113,
+        114
+      ],
+      "bbox": [
+        184,
+        481,
+        327,
+        495
+      ],
+      "images": [],
+      "latex": [],
+      "table_html": null,
+      "generated_description": null
+    }
+  ],
+  "source_path": "D:\\Data Eyond Catalog Version\\Agentic-Service-Data-Eyond-Catalog\\data\\knowledge_docs\\STD_2026_006_MNO.pdf",
+  "content_hash": "f10807178b20531e86237a2640ff4125d259aa68e5e9d9f910c0c2365cd92833",
+  "n_pages": 9,
+  "parser_name": "mineru",
+  "parser_version": "3.4.4",
+  "parser_backend": "hybrid",
+  "parser_config": "1a2e3c0649d5",
+  "version": 1,
+  "schema_version": "0.3.0",
+  "created_at": "2026-08-27T13:28:29",
+  "raw_output_dir": "D:\\Data Eyond Catalog Version\\Agentic-Service-Data-Eyond-Catalog\\data\\knowledge_cache\\parse\\f10807178b20531e-1a2e3c0649d5-3.4.4"
+}

eval/knowledge/results/v2_full_2026-08-27_133757.json

@@ -0,0 +1,154 @@
+{
+  "run": {
+    "created_at": "2026-08-27_133757",
+    "doc_id": "STD_2026_006_MNO",
+    "artifact": "C:\\Users\\RIFQIH~1\\AppData\\Local\\Temp\\claude\\C--Users-RifqiHafizuddin-Documents-Dataeyond-catalog-Agentic-Service-Data-Eyond-Catalog\\ffaa7c0a-ec95-4c95-a84d-149666a6f144\\scratchpad\\chunks_buma_v2.json",
+    "content_hash": "f10807178b20531e86237a2640ff4125d259aa68e5e9d9f910c0c2365cd92833",
+    "parser": "mineru/3.4.4/hybrid",
+    "parser_backend": "hybrid",
+    "extracted": true,
+    "mock": false,
+    "limit": null,
+    "seconds": 205.6,
+    "served_by": {
+      "model_version": [
+        "gpt-5.4-nano-2026-03-17"
+      ],
+      "system_fingerprint": []
+    },
+    "label": "re-parse 2026-08-27T13:28 (same hash, corrected chunk boundaries)"
+  },
+  "funnel": {
+    "pages": 9,
+    "chunks": 31,
+    "mentions_raw": 186,
+    "clusters": 63,
+    "compression_ratio": 2.556,
+    "abbrev_pairs": 5,
+    "rule_candidates": 16
+  },
+  "scores": {
+    "E1": {
+      "label": "term-filter recall",
+      "value": 0.8293,
+      "detail": {
+        "label": "term_filter_recall(E1)",
+        "n_gold": 41,
+        "n_pred": 84,
+        "true_positives": 34,
+        "precision": 0.4048,
+        "recall": 0.8293,
+        "f1": 0.544,
+        "misses": [
+          "Breakdown",
+          "Overburden removal",
+          "Grouping (Composite)",
+          "Weight average",
+          "Uncontrollable",
+          "Fleet management",
+          "Mineplan"
+        ]
+      }
+    },
+    "E2": {
+      "label": "review-burden compression",
+      "value": 2.556,
+      "detail": {
+        "mentions": 161,
+        "clusters": 63
+      }
+    },
+    "E3": {
+      "label": "glossary schema fill (precision)",
+      "value": 1.0,
+      "detail": {
+        "label": "glossary_schema_fill(E3)",
+        "n_gold": 18,
+        "n_pred": 6,
+        "true_positives": 6,
+        "precision": 1.0,
+        "recall": 0.3333,
+        "f1": 0.5,
+        "misses": [
+          "MOHH",
+          "Pty",
+          "ECA",
+          "INPR",
+          "Total Hours",
+          "Working Hours",
+          "EWH",
+          "Grouping (Composite)",
+          "Gain/Loss",
+          "Waterfall Analysis",
+          "Hierarki Level Analysis",
+          "Uncontrollable",
+          "Controllable"
+        ],
+        "coverage": {
+          "entries_total": 63,
+          "entries_with_definition": 6,
+          "abstained_null_definition": 57,
+          "scoreable": 6,
+          "unscoreable_term_not_in_gold": 0,
+          "unscoreable_gold_has_no_criteria": 0,
+          "gold_terms_with_criteria": 18,
+          "failures": []
+        }
+      }
+    },
+    "rule_recall": {
+      "label": "rule-branch recall",
+      "value": 0.4286,
+      "detail": {
+        "label": "rule",
+        "n_gold": 14,
+        "n_pred": 15,
+        "true_positives": 6,
+        "precision": 0.4,
+        "recall": 0.4286,
+        "f1": 0.4138,
+        "misses": [
+          "QTY_PER_ACTIVITY",
+          "QTY_GROUPING_SUM",
+          "ACTIVITY_CLASSIFICATION_SOURCE",
+          "UA_BY_ACTIVITY",
+          "PTY_PRODUCTION_SOURCE",
+          "PTY_WORKING_HOURS_DEFINITION",
+          "GAINLOSS_UNITS",
+          "QTY_PHYSICAL_REPORTING"
+        ]
+      }
+    }
+  },
+  "baseline": {
+    "file": "v2_full_document_2026-08-24_093051.json",
+    "E1": 0.8049,
+    "E2": 2.81,
+    "E3": 0.9,
+    "rule_recall": 0.2
+  },
+  "cost": {
+    "prompt_tokens": 153318,
+    "cached_tokens": 98816,
+    "completion_tokens": 8548,
+    "cache_hit_rate": 0.645,
+    "calls": 90
+  },
+  "quality": {
+    "fields_rejected_by_span_check": 0,
+    "rejections": [],
+    "glossary_entries": 63,
+    "rule_entries": 15,
+    "formula_entries": 6,
+    "abstained_null_definition": 57,
+    "latex_verification": {
+      "verified": 6
+    },
+    "links": {
+      "terms_indexed": 80,
+      "variables_unresolved": 2,
+      "glossary_without_defining_formula": 57,
+      "rules_without_term_link": 0
+    }
+  }
+}