E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Abhishek Kulkarni

abhishekk@kyma.world

2026-09-19 → 2026-09-26 · showing up to 2026-09-26 · live data last updated 26 Sept, 08:33 UTC

Hours tracked

44.4

5 days tracked

Hours per day

8.9

on days with tracked time

Mean activity

25.8%

never scored

PRs opened

0

in this period

PRs merged

0

none opened

Median time to merge

—

nothing merged

Commits

3

2 repositories

Lines changed

2,419

context only — never scored

Identity

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

aws 2:Abhishek_Kaws Abhishek_Kaws abhishekgithub abhishek-1touchgithub Abhishek9302github Abhishek-AMKhubstaff Abhishek Kulkarni

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

81

rank 4 of 12

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

81 of 100, ranked 4 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 82; they score 81. 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 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%5055-0.9code landed on 20 separate days
Infrastructure15%5053-0.6635 points from 192 AWS changes on 16 days
Change discipline18%1001000median commit 170 lines
Craft25%9998+0.4252 of 253 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.
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 81 − 82 = -1, where 82 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.4 hours tracked, 3 commits, 2,419 lines changed, 23.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.

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 44.36h 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 41 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 294 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-259.4322.5000
▸ 2026-09-248.6028.3000
▸ 2026-09-239.9325.6000
▸ 2026-09-228.2217.6000
▸ 2026-09-218.1823.6300
▸ 2026-09-200.00—000
▸ 2026-09-190.00—000

Where the time went

Hubstaff project attribution.

Thunder Marketing's Project34.9h233 rows
ZeroHumanMultiAgentV39.4h61 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 · 3 counted, 0 excluded

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

SHARepoMessageWhen+/−Counted
914c25aZeroHumanMultiAgentV3feat(business-os): auto-hire the full catalog workforce on new accounts2026-09-21+522 −161counted
313d608ZeroHumanMultiAgentV3feat(business-os): ship founder products, GTM customer UI, and leftov…2026-09-21+1,687 −39counted
24276eaMarketing-Sponsorship-Automationdocs: correct roadmap staleness found during a fresh audit2026-09-21+5 −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.