Hours tracked
246.5
39 days tracked
Hours per day
6.3
on days with tracked time
Mean activity
11.1%
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.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.
Insufficient evidence
No code account linked — delivery cannot be measured for this person.
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.
⚑ No code account linked to this person
Rule: fires when the employee has no row in `identities` for provider `github`.
What it does not mean: Nothing here says this person wrote no code — it says nothing can be attributed to them. Until an identity is mapped, every code-derived figure on this page is an absence of evidence, not evidence of absence.
Infrastructure work
From CloudTrail — the only record of work that leaves no trace in git.
Weighted points
790
Changes
267
Days
27
Unscored
62
sign-ins, own MFA, shells
What they actually did
- iam AddUserToGroup×30 · 90 pts
- iam AttachGroupPolicy×25 · 75 pts
- ec2 RunInstances×11 · 55 pts
- iam ListOrganizationsFeatures×17 · 51 pts
- iam CreateUser×16 · 48 pts
- support-console CreateCaseDraft×9 · 45 pts
- guardduty ArchiveFindings×19 · 38 pts
- inspector2 ListConnectors×13 · 26 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 246.5h 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 1688 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.
Raw Hubstaff intervals · 2026-08-08
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 | 246.5h | 1688 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.