Hours tracked
33.9
4 days tracked
Hours per day
8.5
on days with tracked time
Mean activity
20.6%
never scored
PRs opened
0
in this period
PRs merged
0
none opened
Median time to merge
—
nothing merged
Commits
0
0 repositories
Lines changed
0
context only — never scored
Identity
A person is only measurable across the providers they are linked to.
Evidence confidence for this person
0.55 against a 0.60 floor — no composite score is computed and no alert can fire for this person (AC-05). Measured 0.70, capped because no task tracker defines the work.
Delivery signal
An input to a conversation, not a verdict.
Insufficient evidence
34h tracked, and no commit or pull request under this account across the organisation's repositories in this period. Either the work was not code, or it was authored under a different account.
Flags raised · 1
Observations about the work, not judgements of the person. None of these feed the score. Each one shows the rule that fired and what it does not prove.
⚑ Tracked time, but nothing landed in this organisation’s repositories
Rule: fires at ≥ 20 tracked hours with zero commits, merged PRs and reviews — measured 33.9h and 0 of those three.
What it does not mean: This does NOT mean no work happened. Work that is not code is invisible here, and so is code pushed under an unlinked account or to a repository outside GITHUB_ORG. Check what the work was before treating it as an absence.
Infrastructure work
From CloudTrail — the only record of work that leaves no trace in git.
Weighted points
62
Changes
25
Days
1
Unscored
1
sign-ins, own MFA, shells
What they actually did
- route53 ChangeResourceRecordSets×14 · 28 pts
- ses CreateEmailIdentity×4 · 20 pts
- ses PutEmailIdentityDkimAttributes×4 · 8 pts
- q SendMessage×3 · 6 pts
CloudTrail records the API call, not the intent. It cannot tell a considered change from one corrected a minute later, and it retains 90 days — so an empty earlier period means “not retained”, never “nothing happened”.
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 33.9h 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.0055%
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 44 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 228 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-26 | 0.00 | — | 0 | 0 | 0 |
| ▸ 2026-09-25 | 9.88 | 23.1 | 0 | 0 | 0 |
| ▸ 2026-09-24 | 9.31 | 14.8 | 0 | 0 | 0 |
| ▸ 2026-09-23 | 7.52 | 23.6 | 0 | 0 | 0 |
| ▸ 2026-09-22 | 0.00 | — | 0 | 0 | 0 |
| ▸ 2026-09-21 | 7.19 | 19.5 | 0 | 0 | 0 |
| ▸ 2026-09-20 | 0.00 | — | 0 | 0 | 0 |
| ▾ 2026-09-19 | 0.00 | — | 0 | 0 | 0 |
Raw Hubstaff intervals · 2026-09-19
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.
| Position | 18.8h | 124 rows |
| Thunder Marketing's Project | 14.7h | 100 rows |
| email-service | 0.4h | 4 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 · 0 counted, 0 excluded
Default-branch history only. Work on unmerged PR branches does not appear here — see the pull requests above.
No commits by this person on a default branch in this window. This is not a claim that no code was written — commits on PR branches are invisible to this table.
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.