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/no-attack-required-semantic-fuzzing-for-specification-violations-in-agent-skills
Subject: No Attack Required: Semantic Fuzzing for Specification Violations in Agent Skills
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/no-attack-required-semantic-fuzzing-for-specification-violations-in-agent-skills
Paper ref
no-attack-required-semantic-fuzzing-for-specification-violations-in-agent-skills
arXiv id
2605.13044
Generated at
2026-05-14T20:10:39.395Z
Evidence freshness
fresh
Last verification
2026-05-14T20:10:39.395Z
Sources
0
References
0
Coverage
0%
Lineage hash
88c93ff2db3e9214a77a7569b69b0efe9a0f390b58778eb195809b965c444d90
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.
paper_evidence_receipts.references_count
paper_evidence_receipts.coverage