Skip to content

process(roadmap): RM-02 measure build speed and token cost per release - #580

Open
MendixMau wants to merge 2 commits into
masterfrom
roadmap/rm-02-release-speed-benchmark
Open

MendixMau wants to merge 2 commits into
masterfrom
roadmap/rm-02-release-speed-benchmark

Conversation

@MendixMau

Copy link
Copy Markdown
Owner

Parks RM-02 in process/roadmap.md: the per-exec check regression found in cook-off run 2 (arm C, toolkit c9dedb11), with the numbers, the fix assets under test (branch run3-speed, measured in arm D before merge), a start trigger and an exit bar. Lint stays per exec by decision, showing new warnings only.

Roadmap entry only; no code change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XM8AzTxUsYcriPXQ58ZPEV

MendixMau and others added 2 commits October 27, 2026 08:51
Run 2 of the ProcureFlow cook-off found a regression no release caught: 184 commits since
247729f added per-exec checks (lint, score, approval refusal, row-as-unit) and removed none.
Arm C: 0.93 scripts/row (cloud 0.34), lint+score 18.3 min unread, verify-module 0 runs,
docker reload broken, stopped at row 121/147 after 10 h 50 min; 399M lead input tokens,
40k fixed load per call with 0 Skill/MCP calls. RM-02 parks a per-release benchmark,
cost-and-reader per check, cadence over repetition, quiet output and lean sessions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XM8AzTxUsYcriPXQ58ZPEV
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant