E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Rushikesh Powar

rushikesh@kyma.world

2026-09-23 → 2026-09-30 · showing up to 2026-09-30 · live data last updated 30 Sept, 05:08 UTC

Hours tracked

44.8

6 days tracked

Hours per day

7.5

on days with tracked time

Mean activity

54.5%

never scored

PRs opened

0

in this period

PRs merged

0

none opened

Median time to merge

—

nothing merged

Commits

26

5 repositories

Lines changed

111,717

context only — never scored

Identity

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

aws 2:Rushikesh-Sgithub rushikesh-swehubstaff Rushikesh Powar

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.

Behind

64

rank 15 of 15

behind ≤ 74median 8183 ≤ leading
infrastructure 15%16
change discipline 18%75
craft 25%90
consistency 12%55
completed work 22%—
review 8%—

Why this reads as “Behind”

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.

64 of 100, ranked 15 of 15 people with a score, against a cohort median of 81. The bands are cut from this period's own distribution, not fixed thresholds: ≤ 74 is behind, ≥ 83 is leading, and this person is in the bottom 30% of people with a score this period. With every component at the cohort median this person would score 80; they score 64. That difference is carried by infrastructure (16 against a cohort median of 50, worth -7.3 points) and change discipline (75 against a cohort median of 100, worth -6.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 15 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%1650-7.345 points from 21 AWS changes on 8 days
Change discipline18%75100-6.4median commit 592 lines
Craft25%9098-2.994 of 107 commits name what they changed
Consistency12%5552+0.5code landed on 27 separate 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 64 − 80 = -16, where 80 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.8 hours tracked, 26 commits, 111,717 lines changed, 51.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

4

Changes

2

Days

2

Unscored

0

sign-ins, own MFA, shells

Configuration 2 × 2pt

What they actually did

  • ec2 StartInstances×2 · 4 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

14.3%

6.38h of 44.77h 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 335 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-300.4751.4000
▸ 2026-09-298.9851.7500
▸ 2026-09-289.5052.0400
▸ 2026-09-270.00—000
▸ 2026-09-268.1943.1500
▸ 2026-09-250.00—000
▸ 2026-09-248.7556.4500
▸ 2026-09-238.8854.3700

Raw Hubstaff intervals · 2026-09-30

StartEndAct%ProjectSourceProvider row
04:3204:4042.32CMShubstaffhubstaff:10321604432
04:4004:5060.33CMShubstaffhubstaff:10321630278
04:5005:0044.33CMShubstaffhubstaff:10321646620
05:0005:0186.25CMShubstaffhubstaff:10321646656

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

Position25.6h191 rows
Thunder Marketing's Project12.8h97 rows
CMS5.9h41 rows
Football_Scraping_Main0.5h6 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 · 26 counted, 0 excluded

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

SHARepoMessageWhen+/−Counted
46479d6POSITION_INTELLIGENCEAdd Crawl4AI web open source scraper2026-09-29+245 −7counted
ddc85cbPOSITION_INTELLIGENCEAdd MongoDB time-series metrics collections2026-09-29+163 −2counted
2e5bd88POSITION_INTELLIGENCEExpand Arizona sources and update incident validation status2026-09-29+348 −7counted
f9c8f4bPOSITION_INTELLIGENCEAdd Atlas Search document search and relevance tuning2026-09-29+908 −21counted
2256a14POSITION_INTELLIGENCEDocument Atlas Search plan, fix Redis and update variables2026-09-29+248 −3counted
c29828dPOSITION_INTELLIGENCEExpand news collection coverage and document validation results2026-09-28+892 −0counted
73e9326cmsUpdate and check the correct domain names, and Switch Ecuador Actual'…2026-09-28+18 −18counted
b009cefGlobal_CMSAudit the articles per website and fix the article generation per web…2026-09-28+213 −157counted
dd8909cBrazil_CMSdocs(website-builder): add frontend manual for Create with AI2026-09-28+416 −2counted
7d08eeaPOSITION_INTELLIGENCEAdd collection-to-classification handoff and source runtime health st…2026-09-26+19 −1counted
436e825POSITION_INTELLIGENCEQueue classification for new documents and stamp source health from t…2026-09-26+537 −79counted
775e037POSITION_INTELLIGENCEMerge remote-tracking branch 'origin/main' into feature/incident-news…2026-09-26+93,563 −288counted
a8b4bf6POSITION_INTELLIGENCEAdd intel worker classification task registration2026-09-26+379 −0counted
e9e8397POSITION_INTELLIGENCERegister required production sources. Mark sources as approved/enable…2026-09-26+85 −7counted
1c2531aPOSITION_INTELLIGENCEAdd RSS and WEB sources for five more states and store full state names.2026-09-24+1,253 −162counted
6855a6dPOSITION_INTELLIGENCEAdded basic read APIs and commands for: Source health Collection runs…2026-09-24+1,932 −29counted
0a24967cmsUpdate fetchWithCache.ts2026-09-24+10 −9counted
780952fcmsUpdate footballController.ts2026-09-24+27 −1counted
0004b87cmsfixing the mongocache layer with increasing pool size2026-09-24+1,064 −18counted
0660040Football_Scraping_MainConfigure and adding new sources with regional sports in the scrapper…2026-09-23+501 −50counted
2b05319POSITION_INTELLIGENCEFix failed item preservation in db and Add global/cross-source dedupe2026-09-23+1,083 −12counted
d872588POSITION_INTELLIGENCEProduction storage path with S3 and re-run end-to-end validation. In…2026-09-23+1,805 −9counted
3b77b0dGlobal_CMSUpdate swagger.ts2026-09-23+1 −2counted
9e5c523Global_CMSMerge remote-tracking branch 'origin/feat/thesportsdb-proxy'2026-09-23+2,582 −6counted
d2e9ac2Global_CMSMerge pull request #2 from 1Touch-dev/feat/cms-s2s-article-write-apis2026-09-23+1,245 −7counted
9b59a7aGlobal_CMSMerge pull request #1 from 1Touch-dev/feat/cms-s2s-dashboard-apis2026-09-23+1,278 −5counted

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.