Buildability / Receipt
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.
Public buildability page receipt window
/buildability/why-does-rlaif-work-at-all
Subject: Why Does RLAIF Work At All?
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.
Structured compute envelope
Insufficient data
No data, compute, hardware, memory, latency, dependency, or serving requirement receipt is attached.
Truth Boundary
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.
Receipt path
/buildability/why-does-rlaif-work-at-all
Paper ref
why-does-rlaif-work-at-all
arXiv id
2603.03000
Generated at
2026-04-02T02:30:40.136Z
Evidence freshness
stale
Last verification
2026-04-02T02:30:40.136Z
Sources
0
References
0
Coverage
17%
Lineage hash
9f3aaa65d0a91f25f1e68ad9422db53bb672c140a4825b0dd949b997a5406f15
Canonical opportunity-kernel lineage hash.
External signature
unsigned_external
No founder, registry, pilot, or production-adoption signature is attached to this receipt.
Verification
not_verified
Verification is blocked until an external signature is provided.
Some score or evidence fields are outside the preferred freshness window.
repo_url
references