Engineering work as a compounding asset
Value Cockpit
Every dollar shown here is derived from signals CodeLedger captured directly from CI — retries avoided, context reused, patterns compounded. The math is in the open.
Estimated savings (last 30 days)
Total hours saved
93.7h
across 87 executions
Breakdown by component
hours saved · % of total
Rework reduction
59.5 = 87 executions × reworkRatio(0.57) × reworkMultiplier(1.2)
59.5h
63.5%
Context recovery
12.0 = 87 executions × timeToContextSaved(0.14)
12.0h
12.8%
Pattern leverage
22.2 = 87 executions × patternReuseRate(0.62) × hoursPerReuse(0.41)
22.2h
23.7%
How this value is computed
estimatedSavings = cost_per_hour × (reworkAvoidedHours + contextRecoveryHours + patternLeverageHours)
Input signals (each with evidence)
| Signal | Value | Severity | Evidence |
|---|---|---|---|
Rework ratio Rework ratio — fraction of executions requiring follow-up fixes | 0.57% | warn | View evidence → |
Context recovery time Context recovery time — hours saved per execution via bundle precision | 0.14h | info | View evidence → |
Pattern reuse rate Pattern reuse rate — fraction of executions matching a known pattern | 0.62% | info | View evidence → |
Execution reliability Execution reliability — first-pass success rate | 0.78% | info | View evidence → |
Assumptions
Adjust these to match your loaded rate. The math changes — the direction doesn’t.
Cost per hour (loaded)
$150
per engineer-hour
Rework multiplier
1.2×
context switching cost
Blended hours / execution
0.80h
average
Unseen value — not in this estimate
Value also includes prevention of unsafe memory persistence — writes that required redaction or were blocked by safety checks represent avoided risk that does not appear in the dollar estimate but contributes to institutional memory hygiene.
Value is grounded in aggregate signals. No individual developer scoring.