E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Pankaj Kumar

pankaj@kyma.world

2026-09-21 → 2026-09-28 · showing up to 2026-09-28 · live data last updated 28 Sept, 05:07 UTC

Hours tracked

61.9

8 days tracked

Hours per day

7.7

on days with tracked time

Mean activity

26.0%

never scored

PRs opened

0

in this period

PRs merged

0

none opened

Median time to merge

—

nothing merged

Commits

16

6 repositories

Lines changed

4,329

context only — never scored

Identity

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

aws pankajaws Pankaj-Sgithub pankaj1touchhubstaff Pankaj Kumar

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.

Leading

87

rank 1 of 14

behind ≤ 73median 7982 ≤ leading
change discipline 18%87
craft 25%94
consistency 12%57
infrastructure 15%100
completed work 22%—
review 8%—

Why this reads as “Leading”

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.

87 of 100, ranked 1 of 14 people with a score, against a cohort median of 79. The bands are cut from this period's own distribution, not fixed thresholds: ≤ 73 is behind, ≥ 82 is leading, and this person is in the top 30% of people with a score this period. With every component at the cohort median this person would score 81; they score 87. That difference is carried by change discipline (87 against a cohort median of 100, worth -3.3 points) and craft (94 against a cohort median of 98, worth -1.4 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 14 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
Change discipline18%87100-3.3median commit 416 lines
Craft25%9498-1.4163 of 175 commits name what they changed
Consistency12%5753+0.7code landed on 30 separate days
Infrastructure15%10050+10.76208 points from 1829 AWS changes on 32 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 87 − 81 = 6, where 81 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: 61.9 hours tracked, 16 commits, 4,329 lines changed, 24.2% 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

2253

Changes

710

Days

7

Unscored

5

sign-ins, own MFA, shells

Provisioning 211 × 5ptDeployment 37 × 4ptAccess & security 126 × 3ptConfiguration 336 × 2pt

What they actually did

  • route53 ChangeResourceRecordSets×329 · 658 pts
  • amplify CreateApp×63 · 315 pts
  • route53 CreateHostedZone×41 · 205 pts
  • amplify CreateDomainAssociation×38 · 190 pts
  • amplify DeleteDomainAssociation×35 · 175 pts
  • amplify CreateBranch×30 · 150 pts
  • amplify StartJob×33 · 132 pts
  • iam AttachRolePolicy×42 · 126 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

39.1%

24.18h of 61.91h on mapped projects. A project-mapping metric, not a diligence metric.

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 6 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 414 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-280.6234.0000
▾ 2026-09-275.6820.2800
▸ 2026-09-2610.1514.2200
▸ 2026-09-257.7321.3200
▸ 2026-09-248.4529.8000
▸ 2026-09-239.1528.5000
▸ 2026-09-229.5732.4000
▸ 2026-09-2110.5621.9400

Raw Hubstaff intervals · 2026-09-27

StartEndAct%ProjectSourceProvider row
08:3608:3610.53CMShubstaffhubstaff:10305257282
08:3808:4027.87CMShubstaffhubstaff:10305263366
08:4008:4518.35CMShubstaffhubstaff:10305266515
09:0909:1040.91CMShubstaffhubstaff:10305299099
09:1009:206.00CMShubstaffhubstaff:10305309797
09:2009:3018.17CMShubstaffhubstaff:10305319961
09:3009:4029.17CMShubstaffhubstaff:10305331787
09:4009:507.50CMShubstaffhubstaff:10305336431
09:5010:007.50CMShubstaffhubstaff:10305352208
10:0010:1018.83CMShubstaffhubstaff:10305364134
10:1010:2020.67CMShubstaffhubstaff:10305375214
10:2010:3012.83CMShubstaffhubstaff:10305386039
10:3010:407.33CMShubstaffhubstaff:10305397339
10:4010:5018.50CMShubstaffhubstaff:10305410239
10:5011:003.17CMShubstaffhubstaff:10305424482
11:0011:1012.33CMShubstaffhubstaff:10305434004
11:1011:2015.50CMShubstaffhubstaff:10305445623
11:2011:3024.00CMShubstaffhubstaff:10305455518
11:3011:4013.17CMShubstaffhubstaff:10305467630
11:4011:509.50CMShubstaffhubstaff:10305480430
11:5012:0029.83CMShubstaffhubstaff:10305492674
12:0012:1018.00CMShubstaffhubstaff:10305505557
12:1012:2036.00CMShubstaffhubstaff:10305517330
12:2012:3014.50CMShubstaffhubstaff:10305532246
12:3012:4016.50CMShubstaffhubstaff:10305542733
12:4012:5013.83CMShubstaffhubstaff:10305556614
12:5013:0017.83CMShubstaffhubstaff:10305570794
13:0013:103.33CMShubstaffhubstaff:10305584809
13:1013:2019.83CMShubstaffhubstaff:10305602115
13:2013:3011.17CMShubstaffhubstaff:10305614009
13:3013:4023.00CMShubstaffhubstaff:10305626081
13:4013:4839.51CMShubstaffhubstaff:10305630125
13:4913:5046.30CMShubstaffhubstaff:10305639508
13:5014:0019.17CMShubstaffhubstaff:10305656334
14:0014:1029.67CMShubstaffhubstaff:10305674355
14:1014:2022.33CMShubstaffhubstaff:10305685530
14:2014:3052.17CMShubstaffhubstaff:10305700526
14:3014:4059.33CMShubstaffhubstaff:10305712142
14:4014:4359.49CMShubstaffhubstaff:10305712167

39 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 Project37.7h247 rows
CMS24.2h167 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 · 16 counted, 0 excluded

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

SHARepoMessageWhen+/−Counted
3be35e9puntoecuador.worldPin Amplify SSR to Next's React and swc helper so compute stops retur…2026-09-27+9 −7counted
a94cc1dpuntoecuador.worldRefactor boundedGet function to utilize the native fetch API, improvi…2026-09-27+14 −84counted
bd78ad9puntoecuador.worldUpdate next.config.ts to remove outputFileTracingRoot and add serverE…2026-09-27+4 −2counted
8a9b500puntoecuador.worldRefactor boundedGet function to simplify timeout handling by removing…2026-09-27+3 −4counted
c689a2bpuntoecuador.worldRefactor API calls to use boundedGet for improved timeout handling an…2026-09-27+108 −44counted
a2593dcpuntoecuador.worldUpdate .env.example to include INDEXNOW_SECRET variable formatting ad…2026-09-27+1 −1counted
803b025puntoecuador.worldEnhance environment configuration and update dependencies.2026-09-27+2 −11counted
69f4b7epuntoecuador.worldEnhance environment configuration and update dependencies.2026-09-27+720 −448counted
377db86ecuadorenvivo.lifeUpdate site domain references from ecuadorenvivo.com to ecuadorenvivo…2026-09-26+22 −14counted
f49893cecuadorenvivo.lifeSync the npm lockfile so Amplify can install emnapi 1.11.3.2026-09-26+22 −0counted
c033c35noticiasecuador24.comUpdate package-lock.json to upgrade @alloc/quick-lru to version 5.3.0…2026-09-25+826 −668counted
91b0fcaecuadoractual.live-Update package-lock.json to upgrade @alloc/quick-lru to version 5.3.0…2026-09-25+693 −526counted
82db370Business-Directory-for-Coritibanoop: touch server.ts to create branch divergence2026-09-21+0 −0counted
96b75ddBusiness-Directory-for-Coritibachore: initialize main branch2026-09-21+0 −47counted
635ea88Business-Directory-for-Coritibachore: empty base for main branch2026-09-21+1 −48counted
2ecfa64globla-cms-IndonesianMerge pull request #4 from 1Touch-dev/1touch/CMSA-72026-09-21+0 −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.