E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Rishav Raj

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

46.6

7 days tracked

Hours per day

6.7

on days with tracked time

Mean activity

49.6%

never scored

PRs opened

0

in this period

PRs merged

0

none opened

Median time to merge

—

nothing merged

Commits

1

1 repositories

Lines changed

4,818

context only — never scored

Identity

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

aws 2:Rishv-Sgithub rishav1238hubstaff Rishav Raj

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

78

rank 9 of 12

behind ≤ 78median 7881 ≤ leading
change discipline 18%80
consistency 12%32
craft 25%98
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.

78 of 100, ranked 9 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 78. That difference is carried by change discipline (80 against a cohort median of 100, worth -6.5 points) and consistency (32 against a cohort median of 55, worth -5 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
Change discipline18%80100-6.5median commit 4,527 lines
Consistency12%3255-5code landed on 8 separate days
Craft25%989808 of 8 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 — has an AWS account but made no infrastructure changes in the window. Not scored as zero: console access is not a job description, and someone whose work is code has not failed at ops.
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 78 − 89 = -11, 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: 46.6 hours tracked, 1 commits, 4,818 lines changed, 49.1% 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.

Flags raised · 1

Observations about the work, not judgements of the person. None of these feed the score. Each one shows the rule that fired and what it does not prove.

  • ⚑ Median commit is 4,527 lines

    Rule: fires above a 3,000-line median commit — measured 4,527 lines across 8 commits.

    What it does not mean: A median this size is usually a lock file, a vendored dependency, generated client code or a migration — committed, but not authored line by line. It is a reason to discount the volume, not evidence of anything about the author.

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

0%

All 46.58h went to Hubstaff projects that are not mapped to any repository or external key. This is a project-mapping metric, not a diligence metric — it measures our configuration, not this person's focus.

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 319 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-257.2256.7000
▸ 2026-09-246.0257.6000
▸ 2026-09-238.9735.0000
▾ 2026-09-227.3663.3000
▸ 2026-09-218.8841.5000
▸ 2026-09-201.6753.9100
▸ 2026-09-196.4645.1000

Raw Hubstaff intervals · 2026-09-22

StartEndAct%ProjectSourceProvider row
05:3905:4088.89Thunder Marketing's Projecthubstaffhubstaff:10275819714
05:4005:5010.67Thunder Marketing's Projecthubstaffhubstaff:10275866151
05:5006:0039.83Thunder Marketing's Projecthubstaffhubstaff:10275900326
06:0006:0529.22Thunder Marketing's Projecthubstaffhubstaff:10275904361
06:0606:1073.52Thunder Marketing's Projecthubstaffhubstaff:10275933544
06:1006:2075.67Thunder Marketing's Projecthubstaffhubstaff:10275969547
06:2006:3072.83Thunder Marketing's Projecthubstaffhubstaff:10276005861
06:3006:4071.17Thunder Marketing's Projecthubstaffhubstaff:10276042254
06:4006:5072.33Thunder Marketing's Projecthubstaffhubstaff:10276079425
06:5007:0072.00Thunder Marketing's Projecthubstaffhubstaff:10276104443
07:0007:0071.43Thunder Marketing's Projecthubstaffhubstaff:10276104489
07:0307:0662.56Thunder Marketing's Projecthubstaffhubstaff:10276128703
07:1307:2038.00Thunder Marketing's Projecthubstaffhubstaff:10276196076
07:2007:3010.17Thunder Marketing's Projecthubstaffhubstaff:10276259311
07:3007:401.17Thunder Marketing's Projecthubstaffhubstaff:10276294660
07:4007:500.50Thunder Marketing's Projecthubstaffhubstaff:10276319507
07:5008:003.67Thunder Marketing's Projecthubstaffhubstaff:10276347810
08:0008:0144.23Thunder Marketing's Projecthubstaffhubstaff:10276347853
08:0408:1073.20Thunder Marketing's Projecthubstaffhubstaff:10276396563
08:1008:2071.50Thunder Marketing's Projecthubstaffhubstaff:10276435247
08:2008:3073.67Thunder Marketing's Projecthubstaffhubstaff:10276475146
08:3008:4073.00Thunder Marketing's Projecthubstaffhubstaff:10276514055
08:4008:5075.33Thunder Marketing's Projecthubstaffhubstaff:10276553523
08:5009:0072.83Thunder Marketing's Projecthubstaffhubstaff:10276594919
09:0009:1071.00Thunder Marketing's Projecthubstaffhubstaff:10276634238
09:1009:2074.33Thunder Marketing's Projecthubstaffhubstaff:10276674267
09:2009:3072.67Thunder Marketing's Projecthubstaffhubstaff:10276715980
09:3009:4073.33Thunder Marketing's Projecthubstaffhubstaff:10276756709
09:4009:5071.67Thunder Marketing's Projecthubstaffhubstaff:10276797730
09:5010:0074.50Thunder Marketing's Projecthubstaffhubstaff:10276841026
10:0010:1073.33Thunder Marketing's Projecthubstaffhubstaff:10276882418
10:1010:2074.33Thunder Marketing's Projecthubstaffhubstaff:10276924468
10:2010:3072.67Thunder Marketing's Projecthubstaffhubstaff:10276965730
10:3010:4070.17Thunder Marketing's Projecthubstaffhubstaff:10277007264
10:4010:5074.00Thunder Marketing's Projecthubstaffhubstaff:10277048830
10:5011:0072.33Thunder Marketing's Projecthubstaffhubstaff:10277093428
11:0011:0771.91Thunder Marketing's Projecthubstaffhubstaff:10277110443
18:3518:4075.59Thunder Marketing's Projecthubstaffhubstaff:10280407611
18:4018:5069.00Thunder Marketing's Projecthubstaffhubstaff:10280479507
18:5019:0074.17Thunder Marketing's Projecthubstaffhubstaff:10280555152
19:0019:1071.67Thunder Marketing's Projecthubstaffhubstaff:10280627082
19:1019:2072.00Thunder Marketing's Projecthubstaffhubstaff:10280698572
19:2019:3078.00Thunder Marketing's Projecthubstaffhubstaff:10280769026
19:3019:4077.50Thunder Marketing's Projecthubstaffhubstaff:10280838003
19:4019:5073.17Thunder Marketing's Projecthubstaffhubstaff:10280906968
19:5020:0072.33Thunder Marketing's Projecthubstaffhubstaff:10280983096
20:0020:1070.67Thunder Marketing's Projecthubstaffhubstaff:10281052477
20:1020:2071.83Thunder Marketing's Projecthubstaffhubstaff:10281121045
20:2020:3074.50Thunder Marketing's Projecthubstaffhubstaff:10281188906
20:3020:4070.67Thunder Marketing's Projecthubstaffhubstaff:10281240745
20:4020:4174.11Thunder Marketing's Projecthubstaffhubstaff:10281240801

51 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 Project38.5h261 rows
Position8.1h58 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 · 1 counted, 0 excluded

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

SHARepoMessageWhen+/−Counted
95015d4POSITION_INTELLIGENCEfeat(audience-research): add content aggregation intelligence workflow2026-09-20+4,776 −42counted

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.