Cost meter
The cost meter measures what a finished feature costs and whether each step earned its place.
What it is
The cost meter records four metrics: Cost per completed feature (model tokens spent from plan to merge, including failed attempts), First-pass rate (how often a feature passes every automated check on its first build), Bugs found by the breaking agent, and Decisions a person made.
Each metric has a written definition. Numbers appear only when the meter has measured them.
How it works
Record every step
Every run, verification and decision is saved in a record of every step, kept in your repository.
Define the metric
Cost per completed feature, First-pass rate, Bugs found by the breaking agent and Decisions a person made each have a written definition.
Compute from the record
Numbers come from the record of every step, not from estimates.
Feed back
A step that adds cost without catching anything is a candidate for removal. Defects found later become checks.
What it guarantees
- No number is shown that was not measured.
- Definitions are public before any figure is.
- Methods is built with its own process, so its own numbers will be the first ones published.
What is not built yet
- The cost meter does not run, so there are no figures to show.
- Performance has not been measured on any axis.
Build with us as a design partner.
Methods is pre-alpha. A small number of teams will run it on real work while it is built, and shape what it becomes.