E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

MOHD NAVED

mohd@kyma.world

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

Hours tracked

45.5

7 days tracked

Hours per day

6.5

on days with tracked time

Mean activity

30.3%

never scored

PRs opened

0

in this period

PRs merged

0

none opened

Median time to merge

—

nothing merged

Commits

7

1 repositories

Lines changed

10,388

context only — never scored

Identity

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

aws 2:Naved-Maws MOHD_NAVEDgithub MohdNaved123hubstaff MOHD NAVED

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.

Leading

84

rank 5 of 15

behind ≤ 74median 8184 ≤ leading
change discipline 18%88
consistency 12%45
craft 25%99
completed work 22%—
infrastructure 15%—
review 8%—

Why this reads as “Leading”

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.

84 of 100, ranked 5 of 15 people with a score, against a cohort median of 81. The bands are cut from this period's own distribution, not fixed thresholds: ≤ 74 is behind, ≥ 84 is leading, and this person is in the top 30% of people with a score this period. With every component at the cohort median this person would score 89; they score 84. That difference is carried by change discipline (88 against a cohort median of 100, worth -3.9 points) and consistency (45 against a cohort median of 52, worth -1.5 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 15 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%88100-3.9median commit 479 lines
Consistency12%4552-1.5code landed on 17 separate days
Craft25%9998+0.535 of 35 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 84 − 89 = -5, 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: 45.5 hours tracked, 7 commits, 10,388 lines changed, 27.5% 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

2.4%

1.09h of 45.52h 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 358 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-292.8725.9000
▸ 2026-09-287.4420.2700
▸ 2026-09-271.4634.0000
▸ 2026-09-260.00—000
▸ 2026-09-257.4723.6000
▸ 2026-09-248.4134.5000
▸ 2026-09-238.9024.8000
▸ 2026-09-228.9832.5000

Raw Hubstaff intervals · 2026-09-29

StartEndAct%ProjectSourceProvider row
01:5302:0031.08Positionhubstaffhubstaff:10313821448
02:0002:1032.17Positionhubstaffhubstaff:10313846402
02:1002:2025.33Positionhubstaffhubstaff:10313870719
02:2002:3037.83Positionhubstaffhubstaff:10313900974
02:3002:4017.50Positionhubstaffhubstaff:10313901007
02:4002:5037.50Positionhubstaffhubstaff:10313945010
02:5003:0058.83Positionhubstaffhubstaff:10313970277
03:0003:1072.17Positionhubstaffhubstaff:10313994628
03:1003:2016.17Positionhubstaffhubstaff:10314019546
03:2003:3015.33Positionhubstaffhubstaff:10314021791
03:3003:4030.00Positionhubstaffhubstaff:10314068608
03:4003:500.50Positionhubstaffhubstaff:10314071188
03:5003:5013.79Positionhubstaffhubstaff:10314071226
03:5803:5911.67Positionhubstaffhubstaff:10314093284
03:5903:590.00Positionhubstaffhubstaff:10314093325
03:5904:0061.29Positionhubstaffhubstaff:10314120546
04:0004:1013.83Positionhubstaffhubstaff:10314148960
04:1004:2011.00Positionhubstaffhubstaff:10314165688
04:2004:2719.74Positionhubstaffhubstaff:10314165713
04:2704:3030.94Positionhubstaffhubstaff:10314180283
04:3004:4029.67Positionhubstaffhubstaff:10314232619
04:4004:500.00Positionhubstaffhubstaff:10314232646
04:5004:532.14Positionhubstaffhubstaff:10314232679

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

Position26.5h210 rows
Thunder Marketing's Project17.9h137 rows
HyerPathEnrichment1.1h11 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 · 7 counted, 0 excluded

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

SHARepoMessageWhen+/−Counted
5d4c813POSITION_INTELLIGENCEdocs(memory-bank): record the follower scrape reliability work2026-09-28+16 −2counted
f6f391bPOSITION_INTELLIGENCEfeat(ops-ui): replace the Bright Data screen with Instagram profiles …2026-09-28+1,252 −328counted
5aee5ffPOSITION_INTELLIGENCEfeat(collector)!: replace Bright Data with the Hiker, Apify and SMA I…2026-09-28+5,797 −2,108counted
b2bd394POSITION_INTELLIGENCEfeat(collector): add SMA social-scraper HTTP client2026-09-28+788 −0counted
f008c45POSITION_INTELLIGENCEfix(ingest): dedupe followers in-batch and accept a provider source_id2026-09-28+46 −4counted
683adddPOSITION_INTELLIGENCEfix(apify): use %s logger placeholders and clamp the follower actor l…2026-09-28+32 −8counted
9c705b7POSITION_INTELLIGENCEchore(deps): pin instaloader and hikerapi, ignore Instaloader session…2026-09-28+6 −1counted

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.