E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Aziz Bohra

aziz@kyma.world

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

Hours tracked

49.3

7 days tracked

Hours per day

7

on days with tracked time

Mean activity

35.4%

never scored

PRs opened

3

in this period

PRs merged

3

100% of opened

Median time to merge

0.2h

open → merge

Commits

37

2 repositories

Lines changed

95,994

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

79

rank 8 of 14

behind ≤ 73median 7982 ≤ leading
infrastructure 15%38
change discipline 18%100
craft 25%99
consistency 12%57
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.

79 of 100, ranked 8 of 14 people with a score, against a cohort median of 79. The bands are cut from this period's own distribution, not fixed thresholds: ≤ 73 is behind, ≥ 82 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 81; they score 79. That difference is carried by infrastructure (38 against a cohort median of 50, worth -2.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 14 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%3850-2.6327 points from 138 AWS changes on 9 days
Change discipline18%1001000median commit 168 lines
Craft25%9998+0.4223 of 224 commits name what they changed
Consistency12%5753+0.7code landed on 30 separate days
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 79 − 81 = -2, where 81 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: 49.3 hours tracked, 37 commits, 95,994 lines changed, 34.3% activity, first-pass CI 100%. 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 49.3h on mapped projects. A project-mapping metric, not a diligence metric.

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 3 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 314 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-280.8232.8100
▸ 2026-09-270.00—000
▸ 2026-09-263.3815.9511
▸ 2026-09-259.9627.91722
▸ 2026-09-249.4234.2200
▸ 2026-09-239.2642.6500
▸ 2026-09-228.4544.4000
▸ 2026-09-218.0029.9700

Raw Hubstaff intervals · 2026-09-28

StartEndAct%ProjectSourceProvider row
04:1004:2048.06Positionhubstaffhubstaff:10306941171
04:2004:3021.50Positionhubstaffhubstaff:10306960919
04:3004:4048.50Positionhubstaffhubstaff:10306983148
04:4004:5032.33Positionhubstaffhubstaff:10307006408
04:5005:0014.67Positionhubstaffhubstaff:10307034166

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

Thunder Marketing's Project26.3h167 rows
Position22.9h145 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 · 3

The rows behind “merged” and “reviewed before merge”. Every one links to GitHub.

PRTitleOpenedMerged+/−ReviewsFirst CI
#21
POSITION_INTELLIGENCE
feat(squadb): Day 3 news path (near-dup to story to incident)
feature/squadB-aziz-day3-newspath
2026-09-262026-09-26+2,199 −540success
#17
POSITION_INTELLIGENCE
Day 2: all-history baselines and dark Gate F
feature/squadB-aziz-baseline-gatef
2026-09-252026-09-25+2,237 −480success
#16
POSITION_INTELLIGENCE
feat(squadb): trust gates, provenance, volume rollup, and CI hardening
feature/squadB-aziz-trust-gates-provenance-volume
2026-09-252026-09-25+1,896 −680success

Commits · 37 counted, 0 excluded

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

SHARepoMessageWhen+/−Counted
a9970dbPOSITION_INTELLIGENCEci: run pytest workflow on pushes to feature/squadB2026-09-28+3 −1counted
fb2e155POSITION_INTELLIGENCEdocs(squadb): append Day 3 Alpha/Beta leftover vs calendar2026-09-26+45 −1counted
98f645ePOSITION_INTELLIGENCEdocs(squadb): append remaining work after Day 3 news path2026-09-26+30 −1counted
0cd6c25POSITION_INTELLIGENCEdocs(squadb): record Day 3 news path as landed on feature/squadB2026-09-26+310 −228counted
6d500ffPOSITION_INTELLIGENCEMerge PR #21: Squad B Day 3 news path2026-09-26+2,199 −54counted
d17c9d2POSITION_INTELLIGENCEfeat(squadb): complete Day 3 news path end-to-end2026-09-26+2,199 −54counted
6afb468POSITION_INTELLIGENCEdocs(squadb): record Day 2 Alpha as landed and correct stale status2026-09-25+231 −163counted
c7e76a0POSITION_INTELLIGENCEMerge PR #17: Day 2 Alpha baselines and Gate F2026-09-25+2,237 −48counted
1c08090POSITION_INTELLIGENCEfix(squadb): close Day 2 baseline and incident wiring gaps2026-09-25+186 −4counted
c0ff59dPOSITION_INTELLIGENCEfeat(datalayer): fold all-history baselines and keep Gate F dark2026-09-25+2,053 −46counted
a4ebe6fPOSITION_INTELLIGENCEMerge branch 'feature/squadB-aziz-trust-gates-provenance-volume' into…2026-09-25+81 −50counted
2c60727POSITION_INTELLIGENCEdocs(squadb): record Day 1 completion, completeness follow-up, and ev…2026-09-25+81 −50counted
a7be4dfPOSITION_INTELLIGENCEMerge PR #16: Squad B Day 1 trust gates, provenance, volume rollup, CI2026-09-25+1,896 −68counted
c64e73ePOSITION_INTELLIGENCEfix(ci): isolate agent API tests from live Mongo on clean runners.2026-09-25+5 −2counted
934f0bcPOSITION_INTELLIGENCEfix(ci): add numpy and scipy to requirements for full pytest collection.2026-09-25+2 −0counted
9e91bf2POSITION_INTELLIGENCEfix(squadb): close Day 1 remediation gaps and harden release gate.2026-09-25+318 −24counted
90801fdPOSITION_INTELLIGENCEDay 1 Track Alpha: enforce Gate B on both stores and make volume coun…2026-09-25+1,543 −47counted
6701785POSITION_INTELLIGENCEMerge branch 'feature/squadB' into feature/squadB-aziz-trust-gates-pr…2026-09-25+1,745 −16counted
4af954fPOSITION_INTELLIGENCEMerge branch 'feature/squadB' into feature/squadB-aziz-trust-gates-pr…2026-09-25+4,042 −0counted
63bfecePOSITION_INTELLIGENCEMerge branch 'main' into feature/squadB-aziz-trust-gates-provenance-v…2026-09-25+35 −2counted
115e46dPOSITION_INTELLIGENCEdocs(squadb): drop duplicate scraper evidence docx2026-09-25+0 −0counted
ffb4352POSITION_INTELLIGENCEdocs(squadb): add remaining Squad B reference briefs and schema maps2026-09-25+4,042 −0counted
fed769bPOSITION_INTELLIGENCEdocs(squadb): keep Squad B briefs and scraper evidence under .squadb/2026-09-25+0 −0counted
a3e5aa3POSITION_INTELLIGENCEdocs(squadb): track SoT/ARCH/phases/OSS briefs on feature/squadB for …2026-09-24+2,852 −17counted
38e7590POSITION_INTELLIGENCEfeat(squadb): add feature/squadB memory bank and agent context layers2026-09-24+561 −5counted
6297306HyerPathEnrichmentRequire full HyrePath frontend and observability UIs on Day-1.2026-09-23+101 −32counted
bc849fbHyerPathEnrichmentBlock real env files from git and document the host-only secret rule.2026-09-23+69 −8counted
1f0bf21HyerPathEnrichmentExpand EC2 deploy plan with soft-env policy and full env inventory.2026-09-23+422 −164counted
d867c9eHyerPathEnrichmentAdd EC2 live preview deployment plan (scripts not implemented).2026-09-23+350 −0counted
f05bee2HyerPathEnrichmentApply Figma premium 3-color design system across the frontend.2026-09-23+2,113 −1,301counted
c82375aHyerPathEnrichmentExpand Figma migration plan to close implementation gaps.2026-09-21+375 −222counted
d2f08ccHyerPathEnrichmentAdd Figma-to-frontend design implementation plan.2026-09-21+652 −0counted
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

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.