E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Dhiraj Ambekar

dhiraj@kyma.world

2026-09-19 → 2026-09-26 · showing up to 2026-09-26 · live data last updated 26 Sept, 12:18 UTC

Hours tracked

40.4

5 days tracked

Hours per day

8.1

on days with tracked time

Mean activity

24.4%

never scored

PRs opened

0

in this period

PRs merged

0

none opened

Median time to merge

—

nothing merged

Commits

2

1 repositories

Lines changed

186

context only — never scored

Identity

A person is only measurable across the providers they are linked to.

aws dhirajaws Dhiraj-Agithub Dhiraj4113hubstaff Dhiraj Ambekar

Evidence confidence for this person

0.00floor 0.601.00

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.

Steady

73

rank 10 of 12

behind ≤ 78median 7881 ≤ leading
infrastructure 15%35
craft 25%90
consistency 12%45
change discipline 18%100
completed work 22%—
review 8%—

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.

73 of 100, ranked 10 of 12 people with a score, against a cohort median of 78. The bands are cut from this period's own distribution, not fixed thresholds: ≤ 78 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 82; they score 73. That difference is carried by infrastructure (35 against a cohort median of 53, worth -3.9 points) and craft (90 against a cohort median of 98, worth -2.9 points). 2 of 6 components (completed work, review) could not be measured at all, so the remaining weights were rescaled — this score rests on 70% of the intended evidence.

A band compares this person to the 12 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.

ComponentWeightScoreCohort medianEffectComputed from
Infrastructure15%3553-3.9318 points from 89 AWS changes on 14 days
Craft25%9098-2.935 of 41 commits name what they changed
Consistency12%4555-1.7code landed on 16 separate days
Change discipline18%1001000median commit 197 lines
Completed work22%———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.
Review8%———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 73 − 82 = -9, where 82 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: 40.4 hours tracked, 2 commits, 186 lines changed, 23.6% 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.

Infrastructure work

From CloudTrail — the only record of work that leaves no trace in git.

Weighted points

12

Changes

4

Days

1

Unscored

2

sign-ins, own MFA, shells

Deployment 2 × 4ptConfiguration 2 × 2pt

What they actually did

  • cloudformation UpdateStack×1 · 4 pts
  • elasticbeanstalk UpdateEnvironment×1 · 4 pts
  • autoscaling ResumeProcesses×1 · 2 pts
  • autoscaling SuspendProcesses×1 · 2 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.90

0%

All 40.45h 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.00

55%

Below the 0.6 floor, so no composite score is computed and no alert can fire (AC-05).

Accepted difficulty pointsblockedNone of this person's 5 work units reached acceptance (merged + first CI green + ≥1 review).
First-pass acceptanceblockedNothing accepted, so there is no first-pass rate.
Idle classification mixblocked0 of 257 intervals carry a class.
Tokens per accepted pointblockedNo AI usage data connected.

Day by day

Tracked time beside code that landed. Click a day for the raw Hubstaff intervals behind its hours.

DayHoursAct%CommitsPRs openedPRs merged
▸ 2026-09-260.00—000
▸ 2026-09-258.0321.5000
▸ 2026-09-248.0819.5000
▸ 2026-09-238.0319.9000
▾ 2026-09-228.1621.1000
▸ 2026-09-218.1435.7200
▸ 2026-09-200.00—000
▸ 2026-09-190.00—000

Raw Hubstaff intervals · 2026-09-22

StartEndAct%ProjectSourceProvider row
04:4104:5063.65Thunder Marketing's Projecthubstaffhubstaff:10275692946
04:5005:0038.83Thunder Marketing's Projecthubstaffhubstaff:10275719921
05:0005:1012.17Thunder Marketing's Projecthubstaffhubstaff:10275747448
05:1005:2013.17Thunder Marketing's Projecthubstaffhubstaff:10275775968
05:2005:3010.33Thunder Marketing's Projecthubstaffhubstaff:10275812598
05:3005:4028.50Thunder Marketing's Projecthubstaffhubstaff:10275837381
05:4005:5050.50Thunder Marketing's Projecthubstaffhubstaff:10275870652
05:5006:0019.67Thunder Marketing's Projecthubstaffhubstaff:10275904083
06:0006:1031.00Thunder Marketing's Projecthubstaffhubstaff:10275937478
06:1006:2031.67Thunder Marketing's Projecthubstaffhubstaff:10275982268
06:2006:3024.67Thunder Marketing's Projecthubstaffhubstaff:10276016805
06:3006:4019.67Thunder Marketing's Projecthubstaffhubstaff:10276050199
06:4006:504.17Thunder Marketing's Projecthubstaffhubstaff:10276087975
06:5007:006.67Thunder Marketing's Projecthubstaffhubstaff:10276123362
07:0007:1036.67Thunder Marketing's Projecthubstaffhubstaff:10276160906
07:1007:2038.50Thunder Marketing's Projecthubstaffhubstaff:10276200389
07:2007:3024.00Thunder Marketing's Projecthubstaffhubstaff:10276240810
07:3007:4014.33Thunder Marketing's Projecthubstaffhubstaff:10276280435
07:4007:507.33Thunder Marketing's Projecthubstaffhubstaff:10276318947
07:5008:0024.17Thunder Marketing's Projecthubstaffhubstaff:10276364280
08:0008:1065.33Thunder Marketing's Projecthubstaffhubstaff:10276401195
08:1008:2012.17Thunder Marketing's Projecthubstaffhubstaff:10276443597
08:2008:307.83Thunder Marketing's Projecthubstaffhubstaff:10276479429
08:3008:4027.00Thunder Marketing's Projecthubstaffhubstaff:10276518429
08:4008:5024.17Thunder Marketing's Projecthubstaffhubstaff:10276565062
08:5009:0025.50Thunder Marketing's Projecthubstaffhubstaff:10276599951
09:0009:1019.17Thunder Marketing's Projecthubstaffhubstaff:10276642776
09:1009:2049.67Thunder Marketing's Projecthubstaffhubstaff:10276678812
09:2009:3015.17Thunder Marketing's Projecthubstaffhubstaff:10276724994
09:3009:4014.33Thunder Marketing's Projecthubstaffhubstaff:10276773100
09:4009:5022.83Thunder Marketing's Projecthubstaffhubstaff:10276804543
09:5010:0010.50Thunder Marketing's Projecthubstaffhubstaff:10276848336
10:0010:1012.83Thunder Marketing's Projecthubstaffhubstaff:10276887136
10:1010:209.00Thunder Marketing's Projecthubstaffhubstaff:10276929844
10:2010:306.83Thunder Marketing's Projecthubstaffhubstaff:10276972676
10:3010:4010.33Thunder Marketing's Projecthubstaffhubstaff:10277012598
10:4010:5034.50Thunder Marketing's Projecthubstaffhubstaff:10277053625
10:5011:0017.50Thunder Marketing's Projecthubstaffhubstaff:10277102327
11:0011:108.17Thunder Marketing's Projecthubstaffhubstaff:10277143114
11:1011:2011.17Thunder Marketing's Projecthubstaffhubstaff:10277189671
11:2011:304.83Thunder Marketing's Projecthubstaffhubstaff:10277234075
11:3011:4016.33Thunder Marketing's Projecthubstaffhubstaff:10277279124
11:4011:5020.67Thunder Marketing's Projecthubstaffhubstaff:10277324315
11:5012:0012.17Thunder Marketing's Projecthubstaffhubstaff:10277379665
12:0012:1015.50Thunder Marketing's Projecthubstaffhubstaff:10277439052
12:1012:205.17Thunder Marketing's Projecthubstaffhubstaff:10277486297
12:2012:3024.67Thunder Marketing's Projecthubstaffhubstaff:10277543258
12:3012:4020.83Thunder Marketing's Projecthubstaffhubstaff:10277600477
12:4012:5015.00Thunder Marketing's Projecthubstaffhubstaff:10277633785
12:5012:5138.10Thunder Marketing's Projecthubstaffhubstaff:10277633868

50 rows from time_intervals. This is the bottom of the chain — there is nothing below it but the Hubstaff API response.

Where the time went

Hubstaff project attribution.

Thunder Marketing's Project29.4h183 rows
Position10.7h70 rows
Social media0.3h4 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 · 2 counted, 0 excluded

Default-branch history only. Work on unmerged PR branches does not appear here — see the pull requests above.

SHARepoMessageWhen+/−Counted
f59697dPOSITION_INTELLIGENCEfix(agents): route Pillar 1/3 to POSITION_DB_NAME without touching ap…2026-09-21+148 −19counted
112101bPOSITION_INTELLIGENCEfeat(squada): expose campaign agent APIs on api.position.services2026-09-21+16 −3counted

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.

There is no authentication in this POC, so the submitter is self-declared. Before this platform is used for anything that affects pay, this field has to come from a real session.

Corrections on record · 0

Open disputes are shown to anyone reading this person's numbers.

Nothing disputed yet.