E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Harsh Patel

harshpatle@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

44.5

6 days tracked

Hours per day

7.4

on days with tracked time

Mean activity

29.0%

never scored

PRs opened

0

in this period

PRs merged

0

none opened

Median time to merge

—

nothing merged

Commits

19

3 repositories

Lines changed

23,670

context only — never scored

Identity

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

aws Harsh-Vaws Harsh_Patelgithub harsh-kymahubstaff Harsh Patel

Evidence confidence for this person

0.00floor 0.601.00

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.

Steady

79

rank 6 of 12

behind ≤ 78median 7881 ≤ leading
craft 25%63
change discipline 18%100
consistency 12%57
infrastructure 15%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.

79 of 100, ranked 6 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 79. That difference is carried by craft (63 against a cohort median of 98, worth -12.5 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
Craft25%6398-12.575 of 133 commits name what they changed
Change discipline18%1001000median commit 99 lines
Consistency12%5755+0.3code landed on 26 separate days
Infrastructure15%10053+10.14640 points from 1387 AWS changes on 26 days
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 79 − 82 = -3, 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: 44.5 hours tracked, 19 commits, 23,670 lines changed, 27% 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

1014

Changes

309

Days

6

Unscored

16

sign-ins, own MFA, shells

Provisioning 93 × 5ptDeployment 35 × 4ptAccess & security 47 × 3ptConfiguration 134 × 2pt

What they actually did

  • route53 ChangeResourceRecordSets×81 · 162 pts
  • amplify CreateDomainAssociation×27 · 135 pts
  • ec2 DeleteSecurityGroup×42 · 126 pts
  • amplify CreateApp×18 · 90 pts
  • amplify DeleteDomainAssociation×16 · 80 pts
  • amplify StartJob×12 · 48 pts
  • amplify CreateBranch×8 · 40 pts
  • autoscaling SuspendProcesses×19 · 38 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

63.5%

28.29h of 44.52h on mapped projects. A project-mapping metric, not a diligence metric.

Evidence confidence

conf 1.00

40%

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 0 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 328 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.1125.0000
▸ 2026-09-248.1141.6000
▾ 2026-09-238.0536.3000
▸ 2026-09-228.0516.81200
▸ 2026-09-218.0321.0700
▸ 2026-09-204.1715.9000
▸ 2026-09-190.00—000

Raw Hubstaff intervals · 2026-09-23

StartEndAct%ProjectSourceProvider row
02:3002:4045.58CMShubstaffhubstaff:10282577941
02:4002:5037.83CMShubstaffhubstaff:10282604196
02:5003:0050.50CMShubstaffhubstaff:10282626103
03:0003:1052.17CMShubstaffhubstaff:10282650613
03:1003:1837.27CMShubstaffhubstaff:10282660807
03:2903:3078.79CMShubstaffhubstaff:10282697194
03:3003:4064.33CMShubstaffhubstaff:10282720466
03:4003:5062.67CMShubstaffhubstaff:10282787399
03:5003:506.98CMShubstaffhubstaff:10282787430
04:3704:4039.73CMShubstaffhubstaff:10282867335
04:4004:5069.67CMShubstaffhubstaff:10282893129
04:5005:0069.50CMShubstaffhubstaff:10282920766
05:0005:1039.33CMShubstaffhubstaff:10282948683
05:1005:2064.50CMShubstaffhubstaff:10282977182
05:2005:3084.17CMShubstaffhubstaff:10283007554
05:3005:407.17CMShubstaffhubstaff:10283037706
05:4005:5072.50CMShubstaffhubstaff:10283067887
05:5005:5290.18CMShubstaffhubstaff:10283067921
06:1306:177.20CMShubstaffhubstaff:10283151490
06:3606:4025.00CMShubstaffhubstaff:10283244064
06:4006:5015.50CMShubstaffhubstaff:10283286436
06:5006:5520.06CMShubstaffhubstaff:10283289300
07:3207:4062.58CMShubstaffhubstaff:10283494069
07:4007:5015.83CMShubstaffhubstaff:10283514919
07:5008:0023.83CMShubstaffhubstaff:10283558486
08:0008:1054.83CMShubstaffhubstaff:10283596810
08:1008:2011.00CMShubstaffhubstaff:10283635241
08:2008:3022.00CMShubstaffhubstaff:10283675219
08:3008:4022.50CMShubstaffhubstaff:10283728941
08:4008:500.33CMShubstaffhubstaff:10283763215
08:5009:001.67CMShubstaffhubstaff:10283806755
09:0009:101.50CMShubstaffhubstaff:10283837360
09:1009:175.75CMShubstaffhubstaff:10283850987
09:5310:0012.11CMShubstaffhubstaff:10284059691
10:0010:1026.00CMShubstaffhubstaff:10284079254
10:1010:2033.50CMShubstaffhubstaff:10284127584
10:2010:297.69CMShubstaffhubstaff:10284144659
11:1411:2049.67CMShubstaffhubstaff:10284373553
11:2011:2856.19CMShubstaffhubstaff:10284394686
11:2811:3050.96CMShubstaffhubstaff:10284411040
11:3011:4010.67CMShubstaffhubstaff:10284473049
11:4011:5028.67CMShubstaffhubstaff:10284508291
11:5011:5244.19CMShubstaffhubstaff:10284508407
12:3112:405.91CMShubstaffhubstaff:10284782314
12:4012:431.33CMShubstaffhubstaff:10284782347
12:4912:50100.00CMShubstaffhubstaff:10284838387
12:5013:0053.50CMShubstaffhubstaff:10284903787
13:0013:1062.33CMShubstaffhubstaff:10284973124
13:1013:2046.83CMShubstaffhubstaff:10285024347
13:2013:2038.10CMShubstaffhubstaff:10285024532
13:4713:5064.46CMShubstaffhubstaff:10285274404
13:5014:0037.67CMShubstaffhubstaff:10285352661
14:0014:1034.83CMShubstaffhubstaff:10285433120
14:1014:2043.83CMShubstaffhubstaff:10285513545
14:2014:3029.33CMShubstaffhubstaff:10285585536
14:3014:3226.28CMShubstaffhubstaff:10285585768
14:4014:5038.49CMShubstaffhubstaff:10285754835
14:5015:0042.83CMShubstaffhubstaff:10285837851
15:0015:1027.50CMShubstaffhubstaff:10285919727
15:1015:1951.61CMShubstaffhubstaff:10285966689
15:5416:0023.85CMShubstaffhubstaff:10286338020
16:0016:0418.28CMShubstaffhubstaff:10286347448

62 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.

CMS28.3h209 rows
(no project selected)11.1h80 rows
Coxa Internship2.8h21 rows
Coxahub2.3h18 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 · 19 counted, 0 excluded

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

SHARepoMessageWhen+/−Counted
f95d6cbcoxa-hubfix(web): remove stale react-hooks/exhaustive-deps disable comment2026-09-22+4 −1counted
5da0e4dNexusAIFix i18n gaps found in production E2E: wire Video Jobs UI strings to …2026-09-22+46 −35counted
0bd983eNexusAIi18n (EN + PT-BR) Frontend2026-09-22+7,051 −2,325counted
0008691coxa-hubchore: added user and admin manuals2026-09-22+2,343 −14counted
b5e44c4coxa-hubMerge branch 'feat/harsh-roadmap-followups' into master2026-09-22+3,740 −94counted
43f6764coxa-hubmerge: catch up with origin/master (438c6f0 launch-sector-backfill)2026-09-22+425 −1counted
b88d0dccoxa-hubfeat(admin): AdminAuditLog + four-eyes approval for admin deactivate/…2026-09-22+1,900 −36counted
6c71220coxa-hubfix(test): update e2e-flows SearchService constructor calls for Meili…2026-09-22+3 −3counted
58d65c8coxa-hubdocs(infra): AWS runbooks for Prometheus/Grafana and Meilisearch2026-09-22+511 −0counted
c96e7fecoxa-hubfix(storage): support EC2/EB instance-role S3 auth when static keys a…2026-09-22+611 −41counted
5fcc8a9coxa-hubfeat(twenty-crm): admin sync-status UI + manual resync endpoint2026-09-22+634 −2counted
5e04578coxa-hubfeat(seed): flip all 24 sectors to launch + seed anchor businesses fo…2026-09-22+86 −13counted
6603e11coxa-hubShip Phase 2 design system, offers with QR, profile logo upload, and …2026-09-21+2,483 −205counted
aacbbd2coxa-hubUpdate http-metrics.interceptor.ts2026-09-21+12 −4counted
40a778bcoxa-hubShip Phase 1 newsroom, events calendar, and Prometheus metrics, and r…2026-09-21+873 −79counted
09faebbcoxa-hubFix the Amplify favicon 500 and let admins update the city hostname a…2026-09-21+8 −0counted
af9a1f6coxa_crmUpdate checkFileSafety.test.ts2026-09-21+1 −1counted
dd25c22coxa_crmnpm version fixes2026-09-21+64 −15counted
2bdcaffcoxa_crmUpdate amplify.yml2026-09-21+6 −0counted

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.