Skip to content
runward
runward
Product
Who it is for
Trust
Documentation
News
Try it on an example Talk to us

2026-11-15Release · v0.47.0

runward 0.47.0

A release that tightens the check: under --strict, four sabotages and evidence of the wrong kind are refused, verify says verified only for what it re-derives, and runward-run, shipped with the release, runs the tests out of the agent’s reach.

What changes

  • verify says verified only for what it re-derives, names what it covers, and sends an older attestation back to the runward version that produced it.
  • Four sabotages that passed the strict check are now refused, among them a decision record of the example replaced by a 47-character stub.
  • Under --strict, a row that cites another kind of evidence than its rule requires is refused.
  • runward-run, shipped with the release: the tests and the declared reports run out of the agent’s reach, and the check then reads them.
  • Built-in analyzers read the delivered code against what the mission declares, for a mission that asks for them in its lock; existing missions do not move.

Source

This note restates the section “0.47.0” of runward’s CHANGELOG, at the tag v0.47.0, and nothing else. The detail, and what it leaves out, is in the release notes on GitHub.

← All news

Talk to us

Tell us who you are, and we will get back to you.

Your details are recorded by Another Framework, publisher of runward, to get back to you. They are neither sold nor shared, and are deleted three years after our last exchange. To see or delete them: contact@runward.dev.