A good fit
When to consider this workflow
Choose this workflow when project-level patterns are useful and decision-makers will read completed work, AI work time, and review time together with their definitions and samples.
Metrics with clear definitions
Understand AI work and review time
See how many tasks finished, how long recorded AI work took, and how much working-hours review time was recorded—with sample sizes and limits beside the numbers.
Why this matters
Completed work, AI work time, and review time are more useful when their definitions, ranges, samples, and exclusions stay visible.
Before and after
See what changes in the workflow.
Before alterac.ai
- Stories about one fast or slow agent run stand in for a project-level view.
- Task counts, AI work time, and review time are difficult to compare without shared definitions.
- Averages appear without sample sizes, date ranges, eligibility rules, or slower outliers.
With alterac.ai
- Completed-task counts use a selected UTC date range and clear eligibility rules.
- AI work and working-hours review time produce one sample for each eligible completed task.
- Average, median, p90, sample count, trends, unavailable values, and exclusions appear together.
What alterac.ai does
Connect the steps around your coding agents.
alterac.ai calculates project measures from recorded tasks, runs, completion dates, reviews, exclusions, and organization working hours, then shows the definitions and available samples beside them.
- 01
Choose a date range
Select a recent UTC-backed range or All time. The page keeps that choice in the URL.
- 02
See what finished
Review the Done-task count and prior period for the selected range.
- 03
Compare the time measures
Compare average, median, p90, sample counts, trends, and unavailable values for AI work and review.
- 04
Read the definitions
Check the definitions, eligibility, exclusions, and unavailable states beside the measures.
What stays in your control
Your team keeps the important decisions.
- Excluding a task removes it from current and future task-based metrics without deleting its history.
- A recovered incomplete run can remain ineligible even when its task is included.
- Human review time counts configured organization working hours. It is unavailable until that calendar is set up.
Not a fit
When another approach is better
- Replacing the source records and definitions behind each measure
- Comparing incomplete samples as though they cover the same work
- Measuring raw cycle time or service-level targets
- General project tracking or work outside software
- Choosing which coding model, IDE, or coding agent to use
- Generating code without managing repository work
- A promise that work will ship faster, code will improve, or conflicts will disappear
Product details and evidence
Learn how it works and see the evidence.
These links explain the product behavior, show the exact limits, and share first-party evidence. Use the Docs guides when you are ready for setup steps and commands.
Read the metric definitions
See the date ranges, eligibility rules, distributions, samples, working-hours model, and limitations.
View this sourceSee a dated metric snapshot
Review fixed alterac.ai tables with their source, sample sizes, interpretation, and limitations.
View this sourceSee what the evidence supports
Read what the alterac.ai observations support and what they do not prove.
View this source
Metrics with clear definitions
The team can discuss completed work, recorded AI work time, and working-hours review time using shared definitions and visible sample sizes.
Create an alterac.ai account.