Skip to content
FREN

No cookies, no trackers.

runward, a brick by Another Framework

You ship with AI agents. The tests pass. Does what the team decided still hold?

Your agent says it is done. runward asks for the proof.

The agent works with your team’s decisions, and a check that is not a model refuses what no longer has its proof. Anyone can recompute the verdict. Free and open source.

Try it on an examplenpx --yes runward@0.46.0 init --example

The verdict is not taken on trust: anyone recomputes it from the repository, offline, with the same runward version, and without us. Free and open source, under the MIT licence.

Tests: passedin the team’s delivery chain
Reading of the check

runward-demo-renaming, on the branch of the change: Refused by the check. Public run no. 15.

runward-demo-renaming

Refused by the check
branch of the change · commit 97fce96 · check of 10 Nov, 15:52

The check refuses this version, for the reasons that follow.

  • First-version measurements: a cited piece of evidence is refused by the check.runward/floor.md · line 22
  • Security assessment: a cited piece of evidence is refused by the check.runward/governance/threat-model.md · line 50

The scene, on a public repository

Tests say the code works. They do not say it is ready for production.

One honest rename, made by an agent. Follow it to the moment someone has to say go.

01

An agent changes a name in the code.

In one application, an agent renames guardFields to applyFieldGuards, everywhere the code knows it. A clean change, the kind made every day.

  • 2 files changed
  • The commit names the agent’s session
02

The tests still pass.

All 14 tests pass, before and after. The code works. Nothing here warns the person who has to say go.

  • 14 tests passed
03

The check refuses, and says why.

The team wrote down what it requires before production, and what proves it. Two of those pieces of evidence still cite the old name: one in the first-version measurements, one in the security assessment. The check refuses them and names the two lines.

  • 2 pieces of evidence refused
  • floor.md, line 22
  • threat-model.md, line 50
04

Two lines, and nothing is blocking.

The repair is two lines: the record cites the new name. The check never asked for a rollback. It asked for the record to match the code, and it said which lines no longer did.

  • 2 lines
  • Nothing is blocking, according to the team’s requirements
The change
refactor: rename guardFields to applyFieldGuards, everywhere the code knows0ea7a60 · the commit message names the agent’s session
code/src/core/domain/guard.ts+1 −1
−export function guardFields(
+export function applyFieldGuardsapplyFieldGuards(
code/src/core/application/triage-request.usecase.ts+2 −2
−const guarded = guardFields(proposal, input.body, registry);
+const guarded = applyFieldGuards(proposal, input.body, registry);

2 files changed. The behaviour is unchanged.

The team’s delivery chain
runward-demo-renamingcommit 97fce96
Tests14 tests
Passed
Check before productionrunward 0.46.0
Refused by the check

The tests do not look at the team’s record.

Reading of the check

runward-demo-renaming

Refused by the check
branch of the change · commit 97fce96 · check of 10 Nov, 15:52

The check refuses this version, for the reasons that follow.

First-version measurements: a cited piece of evidence is refused by the check.runward/floor.md · line 22
Security assessment: a cited piece of evidence is refused by the check.runward/governance/threat-model.md · line 50

Detail of the check, as written (the same for both)typed pointer file:code/src/core/domain/guard.ts#guardFields: symbol "guardFields" not found in the file (moved or renamed? update the pointer)

The team’s record
runward/floor.mdline 22
−file:code/src/core/domain/guard.ts#guardFields
+file:code/src/core/domain/guard.ts#applyFieldGuardsapplyFieldGuards
runward/governance/threat-model.mdline 50
−file:code/src/core/domain/guard.ts#guardFields
+file:code/src/core/domain/guard.ts#applyFieldGuardsapplyFieldGuards

runward-demo-renaming

Nothing is blocking
according to the team’s requirements · branch of the repair · commit 0b56196

Without taking our word for it

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.

  • The check runs in the team’s delivery chain.
  • The engine is under the MIT licence: anyone can read it and run it again.
  • The check verifies that the evidence is there, what it points to and its integrity, never the quality of the code; runward does not run your code.
  • Your audit redoes the calculation on its own machine, without going through the team or through us. It needs read access to the code.
On your sideNode.js 22.12 or newer
git clone https://github.com/stranxik/runward-demo-renaming && git -C runward-demo-renaming checkout 97fce96d901d0d07cad8a230950d391b223736af && npx --yes runward@0.46.0 check --strict --path runward-demo-renaminggit clone https://github.com/stranxik/runward-demo-renaming && git -C runward-demo-renaming checkout 97fce96d901d0d07cad8a230950d391b223736af && npx --yes runward@0.46.0 check --strict --path runward-demo-renaming
Why red ✗ Floor · frontier-deterministic-boundary: typed pointer file:code/src/core/domain/guard.ts#guardFields: symbol "guardFields" not found in the file (moved or renamed? update the pointer) ✗ Govern · security-prompt-injection: typed pointer file:code/src/core/domain/guard.ts#guardFields: symbol "guardFields" not found in the file (moved or renamed? update the pointer)
  • Same applicationrunward-demo-renaming
  • Same versionrunward 0.46.0
  • Same stateRefused by the check
  • Same gaps2 points to fix
Repository
stranxik/runward-demo-renaming
Commit
97fce96d901d0d07cad8a230950d391b223736af
Public run
no. 15

In the studio’s chain

The engine Dropyour is built on.

At Another Framework, agents build the apps with runward. Dropyour is built with runward: every app with a server on Dropyour comes with its evidence record, verifiable without us. The Radar’s own repository is run with runward.

  1. 05runward
    Tests: passedin the team’s delivery chain
    Reading of the check

    runward-demo-renaming

    Refused by the check
    branch of the change · commit 97fce96 · check of 10 Nov, 15:52

    The check refuses this version, for the reasons that follow.

    • First-version measurements: a cited piece of evidence is refused by the check.runward/floor.md · line 22
    • Security assessment: a cited piece of evidence is refused by the check.runward/governance/threat-model.md · line 50

    Public repository runward-demo-renaming · public run no. 15

    The team’s record
    runward/floor.mdline 22
    −file:code/src/core/domain/guard.ts#guardFields
    +file:code/src/core/domain/guard.ts#applyFieldGuards
    runward/governance/threat-model.mdline 50
    +file:code/src/core/domain/guard.ts#applyFieldGuards

    runward-demo-renaming

    Nothing is blocking

    according to the team’s requirements · branch of the repair · commit 0b56196

    runward makes the agents ask for the team’s decisions.What no longer has its proof does not pass. Two lines fixed, and nothing is blocking.

0:00

Watch the studio’s full presentation