E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Anshuman Parmar

anshuman@kyma.world

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

Hours tracked

3.6

1 days tracked

Hours per day

3.6

on days with tracked time

Mean activity

42.8%

never scored

PRs opened

2

in this period

PRs merged

1

50% of opened

Median time to merge

0.2h

open → merge

Commits

4

1 repositories

Lines changed

1,717

context only — never scored

Identity

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

aws Anshuman_Paws 2:Anshuman_Pgithub anshumankymahubstaff Anshuman Parmar

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

85

rank 2 of 3

behind ≤ 80median 8585 ≤ leading
craft 25%98
consistency 12%55
change discipline 18%100
infrastructure 15%67
completed work 22%—
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.

85 of 100, ranked 2 of 3 people with a score, against a cohort median of 85. The bands are cut from this period's own distribution, not fixed thresholds: ≤ 80 is behind, ≥ 85 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 85; they score 85. No single component moves the score by as much as a point; the position comes from the spread across all of them, not from one weak term. 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 3 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
Craft25%98100-0.7185 of 189 commits name what they changed
Consistency12%5558-0.5code landed on 28 separate days
Change discipline18%1001000median commit 208 lines
Infrastructure15%6765+0.4788 points from 253 AWS changes on 10 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 85 − 85 = 0, where 85 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: 3.6 hours tracked, 4 commits, 1,717 lines changed, 42.1% activity, first-pass CI 100%. 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.

  • ⚑ Only 3 people produced code this period — too few to rank against

    Rule: relative bands need at least 4 producing people — found 3.

    What it does not mean: The component scores are still measured. What is withheld is the comparison: with a cohort this small, "leading" and "behind" are noise wearing a number.

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 3.64h 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 40 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 24 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-293.6442.1421

Raw Hubstaff intervals · 2026-09-29

StartEndAct%ProjectSourceProvider row
00:0000:1079.67Positionhubstaffhubstaff:10313516520
00:1000:2052.33Positionhubstaffhubstaff:10313547743
00:2000:3067.67Positionhubstaffhubstaff:10313572687
00:3000:4030.00Positionhubstaffhubstaff:10313600911
00:4000:5060.00Positionhubstaffhubstaff:10313630574
00:5001:005.83Positionhubstaffhubstaff:10313654466
01:0001:1054.67Positionhubstaffhubstaff:10313681443
01:1001:2019.00Positionhubstaffhubstaff:10313706415
01:2001:3040.83Positionhubstaffhubstaff:10313732490
01:3001:4054.17Positionhubstaffhubstaff:10313756133
01:4001:5071.67Positionhubstaffhubstaff:10313780432
01:5001:5835.02Positionhubstaffhubstaff:10313909984
02:3902:40100.00Positionhubstaffhubstaff:10313910005
02:4002:5067.17Positionhubstaffhubstaff:10313930080
02:5003:0069.17Positionhubstaffhubstaff:10313955539
03:0003:1012.50Positionhubstaffhubstaff:10313980237
03:1003:2043.67Positionhubstaffhubstaff:10314004983
03:2003:3077.67Positionhubstaffhubstaff:10314028753
03:3003:4056.00Positionhubstaffhubstaff:10314053522
03:4003:5017.83Positionhubstaffhubstaff:10314093029
03:5004:001.67Positionhubstaffhubstaff:10314094231
04:0004:104.00Positionhubstaffhubstaff:10314134654
04:1004:205.83Positionhubstaffhubstaff:10314155346
04:2004:200.00Positionhubstaffhubstaff:10314196410

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

Position3.6h24 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 · 2

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

PRTitleOpenedMerged+/−ReviewsFirst CI
#41
POSITION_INTELLIGENCE
feat(squad-d): candidate storylines, narrative board, deploy path fix
squad-d/storyline-stage
2026-09-29open+1,444 −00success
#40
POSITION_INTELLIGENCE
fix(clustering): stop merging unrelated stories and double-adding articles
fix/story-clustering
2026-09-292026-09-29+265 −60success

Commits · 4 counted, 0 excluded

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

SHARepoMessageWhen+/−Counted
639aaadPOSITION_INTELLIGENCEfeat(narrative): narrative board from a storyline, every claim cited,…2026-09-29+378 −1counted
485f83ePOSITION_INTELLIGENCEfeat(clustering): candidate storylines (fronts and threads) built fro…2026-09-29+1,064 −0counted
7bcb3ddPOSITION_INTELLIGENCEci(deploy): redeploy when intelligence, datalayer or collector change2026-09-29+3 −0counted
86de610POSITION_INTELLIGENCEfix(clustering): stop merging unrelated stories and adding an article…2026-09-29+265 −6counted

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.