E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Aziz Bohra

aziz@kyma.world

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

Hours tracked

45.1

5 days tracked

Hours per day

9

on days with tracked time

Mean activity

36.8%

never scored

PRs opened

0

in this period

PRs merged

0

none opened

Median time to merge

—

nothing merged

Commits

11

2 repositories

Lines changed

63,366

context only — never scored

Identity

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

aws Aziz-Bohraaws Aziz-Bgithub AzizBohraKymahubstaff Aziz Bohra

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.

Steady

78

rank 7 of 12

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

78 of 100, ranked 7 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 78. That difference is carried by infrastructure (36 against a cohort median of 53, worth -3.6 points). 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
Infrastructure15%3653-3.6327 points from 138 AWS changes on 9 days
Change discipline18%1001000median commit 162 lines
Consistency12%55550code landed on 24 separate days
Craft25%9998+0.4198 of 199 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 78 − 82 = -4, 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: 45.1 hours tracked, 11 commits, 63,366 lines changed, 35.7% 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.

Infrastructure work

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

Weighted points

181

Changes

74

Days

2

Unscored

7

sign-ins, own MFA, shells

Provisioning 11 × 5ptConfiguration 63 × 2pt

What they actually did

  • route53 ChangeResourceRecordSets×52 · 104 pts
  • ses CreateEmailIdentity×11 · 55 pts
  • ses PutEmailIdentityDkimAttributes×11 · 22 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.2%

0.11h of 45.09h 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 287 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.9627.9000
▸ 2026-09-249.4234.2000
▸ 2026-09-239.2642.6000
▸ 2026-09-228.4544.4000
▸ 2026-09-218.0029.9500
▸ 2026-09-200.00—000
▾ 2026-09-190.00—600

Raw Hubstaff intervals · 2026-09-19

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.

Thunder Marketing's Project26.3h167 rows
Position18.7h118 rows
webmail0.1h2 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 · 11 counted, 0 excluded

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

SHARepoMessageWhen+/−Counted
a827400HyerPathEnrichmentMerge pull request #270 from 1Touch-dev/product-doors/t5-full-suite2026-09-21+197 −57counted
39fe884HyerPathEnrichmentMerge origin/main into product-doors/t5-full-suite2026-09-21+29,678 −6,609counted
1f52bb6HyerPathEnrichmentMerge pull request #278 from 1Touch-dev/fix/manual-ui-test-script-qa2026-09-21+383 −52counted
1e77f1cHyerPathEnrichmentMerge origin/main into fix/manual-ui-test-script-qa2026-09-21+9,074 −3,742counted
fe2eef1HyerPathEnrichmentMerge pull request #275 from 1Touch-dev/fix/multilogin-docker-rca2026-09-21+9,074 −3,742counted
dd62e73email-servicefix(admin): keep mailbox table full width2026-09-19+4 −2counted
f620c67email-servicefeat(admin): show Admin Portal beside Thunder Mail2026-09-19+3 −3counted
c3f0831email-servicefeat(admin): restyle login and sidebar, tighten mailbox table2026-09-19+396 −90counted
6e88cc1email-servicefix(admin): keep mailbox emails on one line2026-09-19+42 −30counted
cb2a774email-servicefix(admin): tighten mailbox domain panel and space the table2026-09-19+17 −9counted
5eabd86email-servicefeat(admin): sit mailbox domain panel under the header2026-09-19+144 −18counted

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.