E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Pramod Soni

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

43.0

5 days tracked

Hours per day

8.6

on days with tracked time

Mean activity

31.6%

never scored

PRs opened

0

in this period

PRs merged

0

none opened

Median time to merge

—

nothing merged

Commits

14

9 repositories

Lines changed

6,621

context only — never scored

Identity

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

github PRAMODS0NIgithub pramod-thunderhubstaff Pramod Soni

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

84

rank 1 of 12

behind ≤ 78median 7881 ≤ leading
consistency 12%27
change discipline 18%100
craft 25%99
completed work 22%—
infrastructure 15%—
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.

84 of 100, ranked 1 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 89; they score 84. That difference is carried by consistency (27 against a cohort median of 55, worth -6.1 points). 3 of 6 components (completed work, infrastructure, review) could not be measured at all, so the remaining weights were rescaled — this score rests on 55% 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
Consistency12%2755-6.1code landed on 6 separate days
Change discipline18%1001000median commit 98 lines
Craft25%9998+0.530 of 30 commits name what they changed
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.
Infrastructure15%—53—not scored — no AWS account is mapped to this person, so infrastructure work cannot be seen at all. CloudTrail is the only evidence of it, and it names accounts, not people.
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 84 − 89 = -5, where 89 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: 43.0 hours tracked, 14 commits, 6,621 lines changed, 30.3% 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.

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

18.7%

8.02h of 42.99h 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 287 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.0227.6000
▸ 2026-09-248.2139.6000
▸ 2026-09-238.6827.4000
▸ 2026-09-229.1426.9700
▸ 2026-09-218.9430.3700
▸ 2026-09-200.00—000
▸ 2026-09-190.00—000

Raw Hubstaff intervals · 2026-09-26

No intervals stored for this day. That is an absence of tracked time, not a claim that no work happened.

Where the time went

Hubstaff project attribution.

Thunder Marketing's Project35.0h229 rows
CMS8.0h58 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 · 14 counted, 0 excluded

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

SHARepoMessageWhen+/−Counted
53de339ecuadoractual.live-Update routing for news articles to use new URL structure. Add new de…2026-09-22+2,745 −423counted
d917653global-cms-veitanamese-newRefactor newsletter subscription components to use async handling and…2026-09-22+72 −10counted
9469933global-cms-turkish-Update Husky pre-commit script to use npm commands for linting and bu…2026-09-22+7 −2counted
8df57f2global-cms-turkish-Add email subscription functionality to NewsletterForm; implement API…2026-09-22+36 −1counted
3735cbbglobal-cms-telgufeat: enhance footer newsletter functionality and error handling2026-09-22+49 −7counted
bda40e1global-cms-tamil-websitefeat: update project configuration and add Husky for pre-commit checks2026-09-22+56 −26counted
f0a6a51global-cms-tamil-websitefeat: enhance NewsletterForm with subscription functionality2026-09-22+48 −4counted
b3e7ca7global-cms-spanishImplement newsletter subscription functionality: refactor API route t…2026-09-21+65 −33counted
02f03bbglobal-cms-RussianEnhance Newsletter Signup functionality and add subscription API2026-09-21+43 −2counted
55b2a3bglobal-cms-punjabifeat: implement newsletter subscription functionality with validation…2026-09-21+96 −1counted
5fa7905global-cms-arabicImplement newsletter subscription feature in FooterClient component2026-09-21+52 −5counted
b9efab3global-cms-RussianRefactor FootballHub component to improve type safety2026-09-21+3 −1counted
34676dbglobal-cms-RussianAdd Russian football hub via TheSportsDB CMS proxy.2026-09-21+1,141 −2counted
b6d9445global-cms-RussianUpdate metadata and content for improved SEO and user experience2026-09-21+308 −1,383counted

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.