E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Shakir Khan

shakir@kyma.world

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

Hours tracked

1.0

2 days tracked

Hours per day

0.5

on days with tracked time

Mean activity

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

hubstaff Shakir Khan

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

No code account linked — delivery cannot be measured for this person.

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.

  • ⚑ No code account linked to this person

    Rule: fires when the employee has no row in `identities` for provider `github`.

    What it does not mean: Nothing here says this person wrote no code — it says nothing can be attributed to them. Until an identity is mapped, every code-derived figure on this page is an absence of evidence, not evidence of absence.

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

98%

1h of 1.02h on mapped projects. A project-mapping metric, not a diligence metric.

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 18 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.00—000
▸ 2026-09-260.00—000
▸ 2026-09-250.6357.1000
▸ 2026-09-240.3866.1000
▸ 2026-09-230.00—000
▸ 2026-09-220.00—000
▸ 2026-09-210.00—000
▸ 2026-09-200.00—000
▸ 2026-09-190.00—000
▸ 2026-09-180.00—000
▸ 2026-09-170.00—000
▸ 2026-09-160.00—000
▸ 2026-09-150.00—000
▸ 2026-09-140.00—000
▸ 2026-09-130.00—000
▸ 2026-09-120.00—000
▸ 2026-09-110.00—000
▸ 2026-09-100.00—000
▸ 2026-09-090.00—000
▸ 2026-09-080.00—000
▸ 2026-09-070.00—000
▾ 2026-09-060.00—000
▸ 2026-09-050.00—000
▸ 2026-09-040.00—000
▸ 2026-09-030.00—000
▸ 2026-09-020.00—000
▸ 2026-09-010.00—000
▸ 2026-08-310.00—000
▸ 2026-08-300.00—000
▸ 2026-08-290.00—000
▸ 2026-08-280.00—000

Raw Hubstaff intervals · 2026-09-06

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.

CMS1.0h13 rows
Thunder Marketing's Project0.0h2 rows
brazil-sports-news0.0h2 rows
ecuadorfocus.com0.0h1 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.