Skip to content

WRB scorecard: FF-Occam vs external CLI

Captured 2026-09-07 on one Windows machine. Fetch-only. Same WRB pin. Raw JSON stays under gitignored artifacts/wrb/52025c304f6c/results/.

  • FF-Occam: occam.json (2026-09-07T17:25:39), tree 6bc19e5c7c26, long-lived MCP host, OCCAM_WRB_RETAIN_COMPILE=1
  • external CLI: external_cli.json (2026-09-07T17:22:36), CLI 3.6.7 (external_cli.exe, git 24e6ee8, npm global)
  • WRB revision: 52025c304f6cdd242eb6d3fef2f0cb3700838fbd
Area Metric FF-Occam external CLI Better value
Fetch retrieval 75.0% 87.5% external CLI
Fetch tier 1 100.0% 100.0% tie
Fetch tier 2 75.0% 100.0% external CLI
Fetch tier 3 38.5% 53.8% external CLI
Fetch false positives 0.0% 0.0% tie
Fetch p50 2109 ms 1453 ms external CLI
Fetch p90 4313 ms 5918 ms FF-Occam
Fetch median tokens 1250 1028 external CLI
Search — not measured not measured not comparable
Crawl — not measured not measured not comparable

Occam crawl slot remains an occam_map discovery proxy. Search was not run. Do not set OCCAM_SEARCH_PROVIDER=external_cli in a discovery comparison.

WRB uses substring probes and chars / 4 token estimates. This is comparative evidence, not an agent-answer-quality benchmark and not a product-wide success headline.

P1 live re-run (2026-09-07, same WRB pin, archive policy aligned):

Arm Retrieval T1 / T2 / T3 FP Notes
Occam in-tree (OCCAM_FORCE_DOTNET_RUN=1) 36/48 = 75.0% 100 / 75.0 / 38.5 0 occam-p1.json. Same six misses as the frozen run.
external CLI 3.6.7 archive=off 39/48 = 81.2% 100 / 81.2 / 53.8 0 external_cli-archive-off.json. Down from frozen 42/48.

Fair live gap is 3 URL / 6.25 pp (not 6 / 12.5). external CLI still retrieves one SO question, Indeed, and Reuters. Occam retrieves none of those three. Three other SO URLs missed on both arms this time (external CLI: two ~45–52s deadline, one instant fail). P0+P1 did not raise Occam's 36/48. False-positive rate stayed 0.