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/cp-or-dp-why-not-both-a-case-study-in-the-partial-shop-scheduling-problem
Subject: CP or DP? Why Not Both: A Case Study in the Partial Shop Scheduling Problem
Verdict
Watch
Verdict is Watch because viability or proof quality is intermediate and should be re-evaluated before execution.
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/cp-or-dp-why-not-both-a-case-study-in-the-partial-shop-scheduling-problem
Paper ref
cp-or-dp-why-not-both-a-case-study-in-the-partial-shop-scheduling-problem
arXiv id
2605.23569
Generated at
2026-05-25T20:37:22.658Z
Evidence freshness
stale
Last verification
2026-05-25T20:37:22.658Z
Sources
3
References
0
Coverage
50%
Lineage hash
07c4f48efe0d3ede45cdea15f467e3cb1231d6f885f3ae232ea03a9400948023
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