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/lapro-dta-latent-dual-view-drug-representations-and-salient-protein-feature-extraction-for-generalizable-drug-target-aff
Subject: LaPro-DTA: Latent Dual-View Drug Representations and Salient Protein Feature Extraction for Generalizable Drug--Target Affinity Prediction
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/lapro-dta-latent-dual-view-drug-representations-and-salient-protein-feature-extraction-for-generalizable-drug-target-aff
Paper ref
lapro-dta-latent-dual-view-drug-representations-and-salient-protein-feature-extraction-for-generalizable-drug-target-aff
arXiv id
2603.14792
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
4250e06ec372cf10a0de123332bf1869aa04423253310625b816ec0f5d9d470e
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