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-21

StartEndAct%ProjectSourceProvider row
02:5703:0042.75CMShubstaffhubstaff:10268463674
03:0003:1031.50CMShubstaffhubstaff:10268493552
03:1003:2015.17CMShubstaffhubstaff:10268503130
03:2003:3039.00CMShubstaffhubstaff:10268522192
03:3003:4014.00CMShubstaffhubstaff:10268544045
03:4003:5021.00CMShubstaffhubstaff:10268564438
03:5004:0021.17CMShubstaffhubstaff:10268587383
04:0004:1046.83CMShubstaffhubstaff:10268608075
04:1004:2012.83CMShubstaffhubstaff:10268623117
04:2004:2042.86CMShubstaffhubstaff:10268623153
04:3704:409.38CMShubstaffhubstaff:10268672204
04:4004:5047.33CMShubstaffhubstaff:10268694593
04:5005:0055.17CMShubstaffhubstaff:10268721080
05:0005:1020.00CMShubstaffhubstaff:10268749425
05:1005:209.83CMShubstaffhubstaff:10268773628
05:2005:3018.00CMShubstaffhubstaff:10268810760
05:3005:405.83CMShubstaffhubstaff:10268829504
05:4005:5025.67CMShubstaffhubstaff:10268847734
05:5005:50100.00CMShubstaffhubstaff:10268847790
06:3306:4014.83CMShubstaffhubstaff:10269039510
06:4006:504.50CMShubstaffhubstaff:10269065305
06:5006:523.73CMShubstaffhubstaff:10269065409
07:1007:1226.72CMShubstaffhubstaff:10269139543
07:3907:4027.50CMShubstaffhubstaff:10269253933
07:4007:5011.33CMShubstaffhubstaff:10269291429
07:5008:0012.50CMShubstaffhubstaff:10269333459
08:0008:109.33CMShubstaffhubstaff:10269365582
08:1008:112.61CMShubstaffhubstaff:10269365613
08:3108:3460.96CMShubstaffhubstaff:10269455294
09:0609:1068.44CMShubstaffhubstaff:10269606682
09:1009:2045.67CMShubstaffhubstaff:10269645057
09:2009:3039.33CMShubstaffhubstaff:10269685631
09:3009:4058.17CMShubstaffhubstaff:10269722996
09:4009:5044.50CMShubstaffhubstaff:10269765907
09:5010:007.33CMShubstaffhubstaff:10269803999
10:0010:1026.50CMShubstaffhubstaff:10269870814
10:1010:202.67CMShubstaffhubstaff:10269891334
10:2010:304.67CMShubstaffhubstaff:10269925434
10:3010:4013.00CMShubstaffhubstaff:10269975709
10:4010:5014.00CMShubstaffhubstaff:10270008346
10:5010:592.96CMShubstaffhubstaff:10270030850
11:0911:0928.57CMShubstaffhubstaff:10270077666
11:0911:0933.33CMShubstaffhubstaff:10270078177
11:1011:203.21CMShubstaffhubstaff:10270141044
11:2011:308.67CMShubstaffhubstaff:10270184412
11:3011:4025.83CMShubstaffhubstaff:10270239800
11:4011:504.33CMShubstaffhubstaff:10270271064
11:5011:5449.79CMShubstaffhubstaff:10270273470
12:5213:0041.52CMShubstaffhubstaff:10270673505
13:0013:102.50CMShubstaffhubstaff:10270741377
13:1013:2015.67CMShubstaffhubstaff:10270808704
13:2013:3017.67CMShubstaffhubstaff:10270975763
13:3013:323.03CMShubstaffhubstaff:10270975922
13:4613:5037.22CMShubstaffhubstaff:10271028426
13:5014:0013.00CMShubstaffhubstaff:10271146441
14:0014:1014.83CMShubstaffhubstaff:10271183452
14:1014:2013.17CMShubstaffhubstaff:10271235907
14:2014:2027.27CMShubstaffhubstaff:10271236278
14:4314:5027.69CMShubstaffhubstaff:10271525089
14:5015:0016.00CMShubstaffhubstaff:10271607970
15:0015:103.83CMShubstaffhubstaff:10271671808
15:1015:2018.50CMShubstaffhubstaff:10271727511
15:2015:2153.51CMShubstaffhubstaff:10271727723

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