runwardTrustCheck it yourself
Check it yourself
It is not our screen saying so. The same check, run again on your side on the same commit, gives the same application, the same version, the same state and the same gaps.
- Same applicationrunward-demo-renaming
- Same versionrunward 0.47.0
- Same stateRefused by the check
- Same gaps2 points to fix
The command, in one line
Three gestures, from your desk.
- Copy the command.The repository is public, the command is one line. You can run it again from your seat.
- Run it in an empty folder.Node.js 22.12 or newer
- Compare with this screen.The same check, run again on your side on the same commit, gives the same application, the same version, the same state and the same gaps. Node.js 22.12 or newer.
- Same applicationrunward-demo-renaming
- Same versionrunward 0.47.0
- Same stateRefused by the check
- Same gaps2 points to fix
- Repository
- stranxik/runward-demo-renaming
- Commit
- 97fce96d901d0d07cad8a230950d391b223736af
- Public run
- no. 15
Public run
The public verdict: run no. 15.
One honest rename, made by an agent. Follow it to the moment someone has to say go.
All 14 tests pass, before and after. The code works. Nothing here warns the person who has to say go.
- The tests do not look at the team’s record.
- The check refuses: two pieces of evidence in the record still cite the old name, one of them in the security assessment.
- The repair is two lines, and nothing is blocking.
The tests do not look at the team’s record.
Offline
What replays without us, and without a network.
These outputs come from the runward command, in your delivery chain. None calls the network.
- in-toto Statement v1check --strict --attest01
in-toto Statement v1
The verdict, bound to the digest of the record and of the cited evidence. If a field of the attestation was changed,
runward verifyrefuses it and names that field. The digest covers the team’s record and the cited evidence; the rest of the repository, with--whole-tree. - Evidence sealcheck --freeze02
Evidence seal
The digest of each cited piece of evidence. A later change makes the check refuse.
- Delivery reportrunward report03
Delivery report
A standalone HTML page: the verdict, for a reader with no terminal and no account.
- None of these outputs is signed by runward. Signing is your gesture, with your own key.
The sources
Everything this page states has a public address.
- The engine
- github.com/stranxik/runward · MIT licence
- Public run
- no. 15
- Our internal tool, the runward app
- github.com/stranxik/runward-hosted
- The package
- npmjs.com/package/runward ·
runward@0.47.0
Get started
Try it on an example, in one command.
The command writes a complete example and runs the check: everything is green. Then rename the function it points to, run the tests and then the check: the tests pass, the check refuses and names the two lines of the record that cite it.
- You needNode 22.12 or later, and git.
- The command
npx --yes runward@0.47.0 init --example - What it writesAn example application, its record of decisions and evidence, and the charter for your agents.
- What does not changeYour agent, your tests and your delivery chain.
Those who ship with agents. Those who have to answer for it. One verdict, that anyone can recompute.
Try it on an example