Buildability / Receipt

Can Small Language Models Use What They Retrieve? An Empirical Study of Retrieval Utilization Across Model Scale

This public receipt window renders only fields present in the canonical receipt object, deterministic fixture receipt, or canonical evidence receipt. Missing compute, demo, hash, signature, approval, telemetry, and adoption fields stay explicit.

API receipt Buildability hub

Public buildability page receipt window

Not build-ready: Can Small Language Models Use What They Retrieve? An Empirical Study of Retrieval Utilization Across Model Scale

/buildability/can-small-language-models-use-what-they-retrieve-an-empirical-study-of-retrieval-utilization-across-model-scale

Ignoreblocked

Subject: Can Small Language Models Use What They Retrieve? An Empirical Study of Retrieval Utilization Across Model Scale

Verdict

Ignore

Verdict is Ignore because current viability and proof state do not clear the buildability gate.

Time to first demo

Insufficient data

No first-demo timestamp, owner estimate, or elapsed demo receipt is attached to this surface.

Compute envelope

Structured compute envelope

Insufficient data

No data, compute, hardware, memory, latency, dependency, or serving requirement receipt is attached.

Evidence ids

Truth Boundary

External gate remains unresolved for live deployment claims.

Buildability surfaces only report computed viability and proof receipts. They do not claim live production usage, pilot outcomes, founder sign-off, public Brier calibration, judge divergence, or external adoption unless explicitly sourced.

Proof divergence Developer guide

Can Small Language Models Use What They Retrieve? An Empirical Study of Retrieval Utilization Across Model Scale

Not build-ready: Can Small Language Models Use What They Retrieve? An Empirical Study of Retrieval Utilization Across Model Scale

Compute envelope

Evidence ids

External gate remains unresolved for live deployment claims.

Freshness

Hash state

Signature state

Blockers