E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Rishav Raj

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

42.0

6 days tracked

Hours per day

7

on days with tracked time

Mean activity

49.7%

never scored

PRs opened

1

in this period

PRs merged

0

0% of opened

Median time to merge

—

nothing merged

Commits

9

1 repositories

Lines changed

9,450

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

Steady

77

rank 9 of 14

behind ≤ 73median 7982 ≤ leading
change discipline 18%75
consistency 12%35
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.

77 of 100, ranked 9 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 middle 40% of people with a score this period. With every component at the cohort median this person would score 89; they score 77. That difference is carried by change discipline (75 against a cohort median of 100, worth -8.2 points) and consistency (35 against a cohort median of 53, worth -3.9 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 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%75100-8.2median commit 1,740 lines
Consistency12%3553-3.9code landed on 11 separate days
Craft25%9998+0.516 of 16 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%—50—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 77 − 89 = -12, 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: 42.0 hours tracked, 9 commits, 9,450 lines changed, 49.4% activity, first-pass CI 0%. 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

0%

All 41.95h 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

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 1 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 291 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-283.5047.9210
▸ 2026-09-270.00—000
▾ 2026-09-260.00—000
▸ 2026-09-257.2256.7200
▸ 2026-09-246.0257.6300
▸ 2026-09-238.9735.0200
▸ 2026-09-227.3663.3000
▸ 2026-09-218.8841.5000

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 Project30.4h209 rows
Position11.6h82 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 · 1

The rows behind “merged” and “reviewed before merge”. Every one links to GitHub.

PRTitleOpenedMerged+/−ReviewsFirst CI
#27
POSITION_INTELLIGENCE
feat(followers): add stale bulk-job recovery
Feature/follower-stale-job-recovery
2026-09-28open+499 −00failure

Commits · 9 counted, 0 excluded

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

SHARepoMessageWhen+/−Counted
b9915a7POSITION_INTELLIGENCEfeat(followers): add stale bulk-job recovery2026-09-28+499 −0counted
77d1443POSITION_INTELLIGENCEfeat(intel): add async content embedding pipeline2026-09-28+585 −0counted
5753ad9POSITION_INTELLIGENCEfeat(scheduler): harden one-time schedule execution and retrieval2026-09-25+1,040 −24counted
98b6ba6POSITION_INTELLIGENCEfeat(intel): add Atlas vector search foundation2026-09-25+514 −1counted
435f003POSITION_INTELLIGENCEfeat(audience): add manual named references to promoted records2026-09-24+2,504 −1counted
12b462fPOSITION_INTELLIGENCEfeat(followers): add hold/resume for existing bulk jobs2026-09-24+384 −5counted
1cf02c6POSITION_INTELLIGENCEfeat(run-history): strengthen filtering, lineage, sorting, and lifecy…2026-09-24+437 −40counted
7aeed9fPOSITION_INTELLIGENCEfeat(apify-readback): implement Run History Ops APIs and Saved Data r…2026-09-23+2,415 −1counted
b48e0e7POSITION_INTELLIGENCEfeat(run-history): add extras, lineage tracking, and failure snapshots2026-09-23+717 −283counted

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.