Hours tracked
41.1
6 days tracked
Hours per day
6.9
on days with tracked time
Mean activity
21.7%
never scored
PRs opened
0
in this period
PRs merged
0
none opened
Median time to merge
—
nothing merged
Commits
17
13 repositories
Lines changed
30,920
context only — never scored
Identity
A person is only measurable across the providers they are linked to.
Evidence confidence for this person
0.40 against a 0.60 floor — no composite score is computed and no alert can fire for this person (AC-05).
Delivery signal
An input to a conversation, not a verdict.
79
rank 8 of 11
Why this reads as “Steady”
The band is cut from this period's own distribution, not a fixed threshold. The arithmetic is below so it can be checked rather than believed.
79 of 100, ranked 8 of 11 people with a score, against a cohort median of 80. The bands are cut from this period's own distribution, not fixed thresholds: ≤ 79 is behind, ≥ 81 is leading, and this person is in the middle 40% of people with a score this period. With every component at the cohort median this person would score 87; they score 79. That difference is carried by change discipline (70 against a cohort median of 100, worth -9.8 points). 3 of 6 components (completed work, infrastructure, review) could not be measured at all, so the remaining weights were rescaled — this score rests on 55% of the intended evidence.
A band compares this person to the 11 people who have a score in this window — nothing more. It is not a rating, it does not persist, and it moves when the cohort or the window moves.
How this number was built
Every term is shown with the rows it came from and the cohort figure it was judged against. If a term looks wrong, the tables below are the argument.
| Component | Weight | Score | Cohort median | Effect | Computed from |
|---|---|---|---|---|---|
| Change discipline | 18% | 70 | 100 | -9.8 | median commit 627 lines |
| Craft | 25% | 93 | 94 | -0.5 | 154 of 167 commits name what they changed |
| Consistency | 12% | 62 | 55 | +1.5 | code landed on 29 separate days |
| Completed work | 22% | — | — | — | not scored — never assigned a task in any connected tracker. Scoring 0 here would read as "delivered nothing" when the truth is that no tracker describes this person’s work. |
| Infrastructure | 15% | — | 56 | — | not scored — has an AWS account but made no infrastructure changes in the window. Not scored as zero: console access is not a job description, and someone whose work is code has not failed at ops. |
| Review | 8% | — | — | — | not scored — no review is recorded anywhere in the organisation, so this term has no data for anyone. It is withheld rather than scored 0 — a 0 would read as "does not collaborate". |
Effect is a counterfactual, not a share: how many points this person’s score would move if that one component dropped to the cohort median for it. The effects sum to 79 − 87 = -8, where 87 is what this person would score with every one of their components at the cohort median. Negative rows are the reason the total sits where it does. A component with no data is withheld and the remaining weights are rescaled — it is never scored as zero, and it never counts against anyone.
Measured but deliberately not scored: 41.1 hours tracked, 17 commits, 30,920 lines changed, 18.4% activity. The first four measure motion rather than delivery and are trivially inflated. CI is excluded because it exists on a minority of repositories, so scoring it would rank people by which repository they work in. This score cannot see architecture, planning, mentoring, incident response or infrastructure work at all.
Employee KPIs
Six of the twelve. Where a value is absent the reason is stated — never rendered as a zero.
Focused project ratio
conf 0.900%
All 41.14h went to Hubstaff projects that are not mapped to any repository or external key. This is a project-mapping metric, not a diligence metric — it measures our configuration, not this person's focus.
Evidence confidence
conf 1.0040%
Below the 0.6 floor, so no composite score is computed and no alert can fire (AC-05).
| Accepted difficulty points | blocked | None of this person's 0 work units reached acceptance (merged + first CI green + ≥1 review). |
| First-pass acceptance | blocked | Nothing accepted, so there is no first-pass rate. |
| Idle classification mix | blocked | 0 of 296 intervals carry a class. |
| Tokens per accepted point | blocked | No AI usage data connected. |
Day by day
Tracked time beside code that landed. Click a day for the raw Hubstaff intervals behind its hours.
| Day | Hours | Act% | Commits | PRs opened | PRs merged |
|---|---|---|---|---|---|
| ▾ 2026-09-27 | 0.00 | — | 0 | 0 | 0 |
| ▸ 2026-09-26 | 0.06 | 57.9 | 0 | 0 | 0 |
| ▸ 2026-09-25 | 8.03 | 18.0 | 0 | 0 | 0 |
| ▸ 2026-09-24 | 8.08 | 25.5 | 0 | 0 | 0 |
| ▸ 2026-09-23 | 8.72 | 17.8 | 3 | 0 | 0 |
| ▸ 2026-09-22 | 8.01 | 16.1 | 4 | 0 | 0 |
| ▸ 2026-09-21 | 8.24 | 14.2 | 10 | 0 | 0 |
| ▸ 2026-09-20 | 0.00 | — | 0 | 0 | 0 |
Raw Hubstaff intervals · 2026-09-27
No intervals stored for this day. That is an absence of tracked time, not a claim that no work happened.
Where the time went
Hubstaff project attribution.
| Thunder Marketing's Project | 41.1h | 296 rows |
What was not counted
Commits excluded from output, with the reason stored on the row.
Nothing of this person's was excluded in this window.
Pull requests · 0
The rows behind “merged” and “reviewed before merge”. Every one links to GitHub.
No pull requests opened or merged by this person in this window.
Commits · 17 counted, 0 excluded
Default-branch history only. Work on unmerged PR branches does not appear here — see the pull requests above.
| SHA | Repo | Message | When | +/− | Counted |
|---|---|---|---|---|---|
| f8ffed2 | ecuadoraldia.live | Keep football fetches cacheable so Amplify static pages do not drop f… | 2026-09-23 | +1 −1 | counted |
| 409f2a6 | ecuadoraldia.live | Load football fixtures from CMS date windows so scores, tables, and m… | 2026-09-23 | +686 −149 | counted |
| 3e413c2 | informeec.com | Fix football CMS queries so fixtures and match pages load, and add Am… | 2026-09-23 | +1,901 −696 | counted |
| bfedcb0 | vozdelecuador.com | Fix football CMS queries so live scores and match pages load real Lig… | 2026-09-22 | +801 −107 | counted |
| 081e641 | Ecuadorhoynews.com | Wire live football CMS fixtures into homepage and sports routes. | 2026-09-22 | +2,119 −182 | counted |
| 1e31c20 | Actualidadec.com | Serve CMS football fixtures from date windows so match clicks stop 40… | 2026-09-22 | +1,381 −827 | counted |
| 29234e0 | elpulsoec.com | Load Pasión fixtures from CMS date ranges and /live so widgets work a… | 2026-09-22 | +4,658 −203 | counted |
| 47124b1 | global-cms-Persian | Remove World Cup 2026 pages and wire the live PitchPulse newsletter. | 2026-09-21 | +608 −2,181 | counted |
| b2d0197 | global-cms-Italiano | Wire PitchPulse newsletter subscribe and drop the World Cup 2026 hub. | 2026-09-21 | +425 −2,311 | counted |
| 2b60b63 | fifa-clone-global-cms | Wire live newsletter subscribe API and strip World Cup 2026 surfaces. | 2026-09-21 | +261 −110 | counted |
| 54b5f7c | global-cms-Dutch | Wire the footer newsletter to PitchPulse and strip leftover World Cup… | 2026-09-21 | +423 −2,051 | counted |
| 394a6c5 | global-cms-Brazilian | Wire the footer newsletter to PitchPulse with react-hook-form so Torc… | 2026-09-21 | +4,327 −106 | counted |
| 7d43db9 | global-cms-turkish- | Add Amplify npm deploy spec and Husky pre-commit lint/build gate. | 2026-09-21 | +403 −74 | counted |
| 30eedf7 | global-cms-bengali | docs: document newsletter CTA, env var, and Amplify npm install. | 2026-09-21 | +6 −2 | counted |
| 2320291 | global-cms-bengali | feat: wire newsletter CTA with react-hook-form and reusable memory. | 2026-09-21 | +1,289 −1,548 | counted |
| 1a732e1 | global-cms-bengali | fix: harden locale URLs, banner hydration, and hide WC 2026 data. | 2026-09-21 | +406 −320 | counted |
| df08392 | global-cms-bengali | fix: harden Amplify husky gate and React 19 script injection. | 2026-09-21 | +278 −79 | counted |
This is wrong
Anything on this page can be disputed. A correction is a stored row, not an email — it stays attached to the figure it challenges.
Corrections on record · 0
Open disputes are shown to anyone reading this person's numbers.
Nothing disputed yet.