Project statistics

Delivered engineering output across Tixim and its VX applications, alongside conservative observations of engine availability.

Human-equivalent output 11,636 person-days, base estimate

Equivalent project years 44.75 at 2,080 hours per year

Trailing four weeks 75.67 full-time equivalents

Engine observation Reachable observed 2026-08-15T01:26:33Z

Productivity over time

Weekly base effort by project, a low-to-high uncertainty range, and the rolling four-week FTE rate.

Default branches · first parent

Tixim tix.im vx-maintainer vx-wiki vx-dflash Low–high range Rolling FTE

Severe stable-first hot-fixes

Fixes delivered through stable before main, reconstructed from merge topology and scored for operational severity.

Six months · 33 flagged fixes

Severe Critical Changed lines

Severe 21

Critical 12

First detected 2026-05-03T01:33:40Z

Engine availability

Confirmed reachable, confirmed down, and unknown time. Workflow activity is shown separately and does not turn unsampled time into uptime.

Six months · first recorded workflow 2026-06-13T02:45:52Z

Confirmed reachable Confirmed down Unknown Before first workflow Workflow busy Workflow starts

Confirmed downtime 0.0h

Base estimate 755.2h

Maximum estimate 1,510.3h

Recent source data

Weekly estimates

Week	Project	Commits	Base hours	Range
2026-06-29	tixim	197	1,736.7	868.4–3,473.5
2026-06-29	vx-maintainer	23	142.5	71.3–285.0
2026-07-06	tixim	23	1,310.8	655.4–2,621.7
2026-07-06	vx-maintainer	12	40.5	20.2–80.9
2026-07-13	tixim	293	1,986.5	993.2–3,972.9
2026-07-13	vx-maintainer	17	49.4	24.7–98.8
2026-07-20	tixim	179	1,928.9	964.4–3,857.7
2026-07-20	vx-maintainer	11	175.7	87.9–351.5
2026-07-20	vx-wiki	3	9.9	4.9–19.7
2026-07-27	tixim	72	2,902.4	1,451.2–5,804.8
2026-07-27	vx-maintainer	29	327.8	163.9–655.5
2026-08-03	tixim	93	5,224.9	2,612.4–10,449.8
2026-08-03	vx-maintainer	26	249.8	124.9–499.6
2026-08-10	tixim	50	1,102.8	551.4–2,205.7
2026-08-10	vx-maintainer	6	49.1	24.5–98.1
2026-08-10	website	1	135.6	67.8–271.1

Daily engine evidence

Date	Up	Down	Unknown	Busy	Starts
2026-08-02	0.0h	0.0h	24.0h	0.0h	13
2026-08-03	0.0h	0.0h	24.0h	0.0h	0
2026-08-04	0.0h	0.0h	24.0h	0.0h	0
2026-08-05	0.0h	0.0h	24.0h	0.0h	5
2026-08-06	0.0h	0.0h	24.0h	0.0h	76
2026-08-07	0.0h	0.0h	24.0h	0.0h	33
2026-08-08	0.0h	0.0h	24.0h	0.0h	96
2026-08-09	0.0h	0.0h	24.0h	0.0h	95
2026-08-10	0.0h	0.0h	24.0h	0.0h	23
2026-08-11	0.0h	0.0h	24.0h	0.0h	46
2026-08-12	0.0h	0.0h	24.0h	0.0h	23
2026-08-13	0.3h	0.0h	23.7h	0.0h	52
2026-08-14	0.0h	0.0h	24.0h	0.2h	32
2026-08-15	0.1h	0.0h	1.4h	0.0h	0

How to read these numbers

“Human-equivalent” estimates the effort a competent human team might need to deliver the observed changes, including implementation, review, debugging, and validation. It is not actual time worked, a measure of individual performance, or a claim that lines of code equal value.

The base estimate is 93085.77 hours, with a 46542.86–186171.54 hour uncertainty range. The current dataset uses heuristic. Generated, vendored, lock, and binary files are excluded from effective churn.

The chart covers the last six months and distinguishes time before the first recorded workflow from unobserved time after it. Matching observations of the same engine process prove uptime; two consecutive absent observations prove downtime. Workflow starts remain visible even when a run interval is unusable. Long spans and clustered recovery completion timestamps are rejected. The base downtime estimate assigns half of post-start unknown time to downtime.

Stable-first hot-fixes are commits introduced to main from the stable side of a recorded stable merge. Only fix or revert commits with explicit failure-impact language are scored. Security, durability, runtime, and network paths increase the score; five points is severe and eight is critical. This is a repository-derived risk signal, not an incident or vulnerability record.

Last updated 2026-08-15T01:26:33Z · schema 3 · source c55c0e5650276939e060