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
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
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
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
2 files changed. The behaviour is unchanged.
The tests do not look at the team’s record.
runward-demo-renaming
The check refuses this version, for the reasons that follow.
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)
runward-demo-renaming