E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Harsh Patel

harshpatle@kyma.world

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

Hours tracked

0.2

1 days tracked

Hours per day

0.2

on days with tracked time

Mean activity

58.2%

never scored

PRs opened

0

in this period

PRs merged

0

none opened

Median time to merge

—

nothing merged

Commits

0

0 repositories

Lines changed

0

context only — never scored

Identity

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

aws Harsh-Vaws Harsh_Patelgithub harsh-kymahubstaff Harsh Patel

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.

Insufficient evidence

0h tracked, and no commit or pull request under this account across the organisation's repositories in this period. Either the work was not code, or it was authored under a different account.

Infrastructure work

From CloudTrail — the only record of work that leaves no trace in git.

Weighted points

16

Changes

4

Days

1

Unscored

2

sign-ins, own MFA, shells

Deployment 4 × 4pt

What they actually did

  • amplify StartJob×2 · 8 pts
  • amplify UpdateApp×2 · 8 pts

CloudTrail records the API call, not the intent. It cannot tell a considered change from one corrected a minute later, and it retains 90 days — so an empty earlier period means “not retained”, never “nothing happened”.

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 0.24h 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 2 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-270.2459.0000

Raw Hubstaff intervals · 2026-09-27

StartEndAct%ProjectSourceProvider row
04:3504:4056.23Coxahubhubstaffhubstaff:10305047848
04:4004:5060.17Coxahubhubstaffhubstaff:10305054332

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

Coxahub0.2h2 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 · 0 counted, 0 excluded

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

No commits by this person on a default branch in this window. This is not a claim that no code was written — commits on PR branches are invisible to this table.

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.