E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Anshuman Parmar

anshuman@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

48.2

6 days tracked

Hours per day

8

on days with tracked time

Mean activity

27.6%

never scored

PRs opened

13

in this period

PRs merged

11

85% of opened

Median time to merge

0.4h

open → merge

Commits

74

2 repositories

Lines changed

344,195

context only — never scored

Identity

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

aws Anshuman_Paws 2:Anshuman_Pgithub anshumankymahubstaff Anshuman Parmar

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.

Leading

82

rank 5 of 14

behind ≤ 73median 7982 ≤ leading
craft 25%98
change discipline 18%100
consistency 12%53
infrastructure 15%57
completed work 22%—
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.

82 of 100, ranked 5 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 top 30% of people with a score this period. With every component at the cohort median this person would score 81; they score 82. No single component moves the score by as much as a point; the position comes from the spread across all of them, not from one weak term. 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
Craft25%98980163 of 167 commits name what they changed
Change discipline18%1001000median commit 217 lines
Consistency12%53530code landed on 26 separate days
Infrastructure15%5750+1.5714 points from 230 AWS changes on 10 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 82 − 81 = 1, 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: 48.2 hours tracked, 74 commits, 344,195 lines changed, 26.3% activity, first-pass CI 16.7%. 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

89

Changes

26

Days

3

Unscored

4

sign-ins, own MFA, shells

Provisioning 10 × 5ptDeployment 2 × 4ptAccess & security 3 × 3ptConfiguration 11 × 2pt

What they actually did

  • elasticbeanstalk CreateApplicationVersion×3 · 15 pts
  • sts GetSessionToken×6 · 12 pts
  • elasticbeanstalk UpdateEnvironment×2 · 8 pts
  • autoscaling CreateLaunchConfiguration×1 · 5 pts
  • cloudformation CreateStack×1 · 5 pts
  • cloudformation DeleteStack×1 · 5 pts
  • ec2 CreateLaunchTemplate×1 · 5 pts
  • ec2 DeleteLaunchTemplate×1 · 5 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 48.19h 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

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 29 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 333 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.00—000
▸ 2026-09-277.6932.12555
▾ 2026-09-266.9330.5220
▸ 2026-09-256.8214.5744
▸ 2026-09-249.2023.11422
▸ 2026-09-2310.1532.92000
▸ 2026-09-227.4122.2600
▸ 2026-09-210.00—000

Raw Hubstaff intervals · 2026-09-26

StartEndAct%ProjectSourceProvider row
06:5407:007.16Positionhubstaffhubstaff:10303517503
07:0007:1050.67Positionhubstaffhubstaff:10303534136
07:1007:170.64Positionhubstaffhubstaff:10303574217
07:5208:0052.66Positionhubstaffhubstaff:10303585358
08:0008:1065.33Positionhubstaffhubstaff:10303597408
08:1008:2037.67Positionhubstaffhubstaff:10303608712
08:2008:3023.67Positionhubstaffhubstaff:10303620229
08:3008:4024.00Positionhubstaffhubstaff:10303631662
08:4008:4735.06Positionhubstaffhubstaff:10303802335
11:0511:1019.14Positionhubstaffhubstaff:10303813958
11:1011:208.33Positionhubstaffhubstaff:10303820423
11:2011:3034.17Positionhubstaffhubstaff:10303832025
11:3011:4012.83Positionhubstaffhubstaff:10303851502
11:4011:505.50Positionhubstaffhubstaff:10303860298
11:5012:000.67Positionhubstaffhubstaff:10303875359
12:0012:0719.49Positionhubstaffhubstaff:10303877811
12:0812:1090.38Positionhubstaffhubstaff:10303881446
12:1012:2073.17Positionhubstaffhubstaff:10303897692
12:2012:3050.17Positionhubstaffhubstaff:10303911453
12:3012:4084.33Positionhubstaffhubstaff:10303924802
12:4012:5074.33Positionhubstaffhubstaff:10303939345
12:5012:5657.84Positionhubstaffhubstaff:10303944066
17:3617:409.01Positionhubstaffhubstaff:10304400456
17:4017:5022.83Positionhubstaffhubstaff:10304411222
17:5018:0013.33Positionhubstaffhubstaff:10304440828
18:0018:100.00Positionhubstaffhubstaff:10304440843
18:1018:2011.33Positionhubstaffhubstaff:10304456677
18:2018:305.33Positionhubstaffhubstaff:10304468530
18:3018:367.46Positionhubstaffhubstaff:10304513903
18:5818:5850.00Positionhubstaffhubstaff:10304513919
18:5819:0089.81Positionhubstaffhubstaff:10304513933
19:0019:1067.67Positionhubstaffhubstaff:10304521157
19:1019:202.00Positionhubstaffhubstaff:10304533403
19:2019:3054.50Positionhubstaffhubstaff:10304556530
19:3019:399.91Positionhubstaffhubstaff:10304584656
20:0120:1012.78Positionhubstaffhubstaff:10304603463
20:1020:2030.50Positionhubstaffhubstaff:10304612057
20:2020:3012.00Positionhubstaffhubstaff:10304625917
20:3020:4013.00Positionhubstaffhubstaff:10304637959
20:4020:5034.83Positionhubstaffhubstaff:10304647920
20:5021:0043.00Positionhubstaffhubstaff:10304660554
21:0021:1051.67Positionhubstaffhubstaff:10304674821
21:1021:2025.00Positionhubstaffhubstaff:10304683124
21:2021:306.83Positionhubstaffhubstaff:10304696080
21:3021:404.17Positionhubstaffhubstaff:10304705046
21:4021:5045.00Positionhubstaffhubstaff:10304715583
21:5022:0046.17Positionhubstaffhubstaff:10304727110
22:0022:0474.82Positionhubstaffhubstaff:10304729062
22:0622:0937.23Positionhubstaffhubstaff:10305310797

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

Position29.8h206 rows
Thunder Marketing's Project16.3h110 rows
Hubstaff Platform1.6h13 rows
(no project selected)0.6h4 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 · 13

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

PRTitleOpenedMerged+/−ReviewsFirst CI
#26
POSITION_INTELLIGENCE
feat(apify): port scheduler hardening, follower resume, and vector-search foundation onto current main
integration/apify-clean-port
2026-09-272026-09-27+2,886 −470failure
#25
POSITION_INTELLIGENCE
fix(collector): tune WHYY, re-enable Ohio via browser fallback, back off Wisconsin
integration/incident-config-tuning
2026-09-272026-09-27+20 −130failure
#24
POSITION_INTELLIGENCE
feat(api): mount incidents_router on prod's deployed app
feat/expose-incidents-on-prod-api
2026-09-272026-09-27+6 −20failure
#23
POSITION_INTELLIGENCE
fix(intel-worker): revert duplicate cluster_pending beat schedule (hotfix)
fix/revert-duplicate-cluster-pending-schedule
2026-09-272026-09-27+36 −280failure
#22
POSITION_INTELLIGENCE
Integration: consolidate collector 10-state + Squad B pipeline onto main
integration/pipeline-2026-09-27
2026-09-272026-09-27+23,186 −3320failure
#20
POSITION_INTELLIGENCE
fix(collector): schedule the fetch-job pipeline, track source runs, six-way health, classification handoff
fix/collection-layer-completeness
2026-09-26open+305 −30—
#19
POSITION_INTELLIGENCE
feat(collector): 10-state sources, source-health APIs, failure tracking, intel task registration
feature/incident-news-collection-foundation
2026-09-26open+4,127 −2060—
#18
POSITION_INTELLIGENCE
fix(collector): claim due sources atomically (stop duplicate fetches)
fix/collector-claim-due-sources
2026-09-252026-09-25+107 −30—
#15
POSITION_INTELLIGENCE
feat(collector): source catalog + live-tested registration tool
feat/register-prod-sources
2026-09-252026-09-25+246 −00—
#14
POSITION_INTELLIGENCE
feat(deploy): run intel-worker on the integration environment
feat/deploy-intel-worker
2026-09-252026-09-25+1 −00—
#13
POSITION_INTELLIGENCE
fix(deploy): ship requirements-squada.txt to the api env
fix/api-env-squada-requirements
2026-09-252026-09-25+8 −00success
#12
POSITION_INTELLIGENCE
Run collector-worker continuously; fix lxml build and TLS Redis URL
fix/collector-worker-env
2026-09-242026-09-24+35 −20—
#11
POSITION_INTELLIGENCE
Integration: merge all live feature branches into one staging baseline
staging
2026-09-242026-09-24+59,723 −2040—

Commits · 74 counted, 0 excluded

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

SHARepoMessageWhen+/−Counted
adc0c2cPOSITION_INTELLIGENCEFix: give each celery worker deploy target a unique node name2026-09-27+89 −4counted
ea5611ePOSITION_INTELLIGENCEfix(scale-triggers): breached is None (unknown), not False, when a tr…2026-09-27+2 −2counted
2f63438POSITION_INTELLIGENCEfeat(squadb): dataset export, retention sweep job, scale-trigger regi…2026-09-27+593 −0counted
60b1709POSITION_INTELLIGENCEdocs: full POSITION system status checklist, evidence-based2026-09-27+114 −0counted
a20b814POSITION_INTELLIGENCEfeat(personas): PersonaStore read-cutover + resolve the 403 orphaned …2026-09-27+314 −7counted
fd2bbf8POSITION_INTELLIGENCEdocs(tracker): record 2026-09-28 reconciliation, prod collector-worke…2026-09-27+27 −0counted
af34c20POSITION_INTELLIGENCEfix(deploy): install lxml_html_clean; remove redundant worker postdep…2026-09-27+1 −48counted
60dce38POSITION_INTELLIGENCEops: start collector-worker and intel-worker on integration env2026-09-27+48 −0counted
6e829dfPOSITION_INTELLIGENCEMerge remote-tracking branch 'origin/main' into verify/both-on-fresh-…2026-09-27+0 −0counted
b99e733POSITION_INTELLIGENCEMerge pull request #26 from 1Touch-dev/integration/apify-clean-port2026-09-27+2,886 −47counted
726b21dPOSITION_INTELLIGENCEMerge pull request #25 from 1Touch-dev/integration/incident-config-tu…2026-09-27+20 −13counted
dabb7e5POSITION_INTELLIGENCEMerge remote-tracking branch 'origin/integration/apify-clean-port' in…2026-09-27+2,886 −47counted
1b8e9f6POSITION_INTELLIGENCEMerge remote-tracking branch 'origin/integration/incident-config-tuni…2026-09-27+20 −13counted
45e8dbaPOSITION_INTELLIGENCEfeat(record-sets): add manual-selection API on Squad B's record_sets,…2026-09-27+1,064 −15counted
275eda6POSITION_INTELLIGENCEfeat(apify): port scheduler hardening, follower resume, and vector-se…2026-09-27+1,822 −32counted
d600fa5POSITION_INTELLIGENCEfix(collector): tune WHYY, re-enable Ohio via browser fallback, back …2026-09-27+20 −13counted
0e4e83bPOSITION_INTELLIGENCEMerge pull request #24 from 1Touch-dev/feat/expose-incidents-on-prod-api2026-09-27+6 −2counted
bd63314POSITION_INTELLIGENCEfeat(api): mount incidents_router on the prod-deployed squada_app2026-09-27+6 −2counted
da54237POSITION_INTELLIGENCEMerge pull request #23 from 1Touch-dev/fix/revert-duplicate-cluster-p…2026-09-27+36 −28counted
608c426POSITION_INTELLIGENCEfix(intel-worker): revert duplicate cluster_pending beat schedule2026-09-27+36 −28counted
ca4d451POSITION_INTELLIGENCEMerge pull request #22 from 1Touch-dev/integration/pipeline-2026-09-272026-09-27+23,186 −332counted
1d98df8POSITION_INTELLIGENCEfix(search-indexes): vector indexes need type=vectorSearch; widen alr…2026-09-27+71 −7counted
29b3a0aPOSITION_INTELLIGENCEfix(intel-worker): schedule cluster_pending so classification reaches…2026-09-27+38 −5counted
11a5261POSITION_INTELLIGENCEMerge remote-tracking branch 'origin/feature/squadB' into integration…2026-09-27+19,152 −142counted
b95a4abPOSITION_INTELLIGENCEMerge remote-tracking branch 'origin/fix/collection-layer-completenes…2026-09-27+3,932 −185counted
1b5648aPOSITION_INTELLIGENCEfix(collector): schedule the fetch-job pipeline, track source runs, s…2026-09-26+305 −3counted
2134b46Hubstaff-GitHub-MonitoringAdd systemd ingest jobs, deployment folder, and repo->project mapping2026-09-26+540 −0counted
3c0bf8cPOSITION_INTELLIGENCEMerge pull request #18 from 1Touch-dev/fix/collector-claim-due-sources2026-09-25+107 −3counted
5f1b06bPOSITION_INTELLIGENCEfix(collector): claim due sources atomically so overlapping polls don…2026-09-25+107 −3counted
e40c6e5POSITION_INTELLIGENCEMerge pull request #15 from 1Touch-dev/feat/register-prod-sources2026-09-25+246 −0counted
4a1b4daPOSITION_INTELLIGENCEMerge pull request #14 from 1Touch-dev/feat/deploy-intel-worker2026-09-25+1 −0counted
11ffc38POSITION_INTELLIGENCEfeat(collector): source catalog + live-tested registration tool2026-09-25+246 −0counted
bf5a44aPOSITION_INTELLIGENCEfix(deploy): ship requirements-squada.txt to the api env (#13)2026-09-25+8 −0counted
f545b88POSITION_INTELLIGENCEfeat(deploy): run intel-worker on the integration environment2026-09-25+1 −0counted
241c418POSITION_INTELLIGENCEMerge pull request #12 from 1Touch-dev/fix/collector-worker-env2026-09-24+35 −2counted
415b7b9POSITION_INTELLIGENCEAdded Deployment2026-09-24+0 −1counted
14cb6bePOSITION_INTELLIGENCEfix(settings): verify certs on rediss:// URLs so Celery accepts Elast…2026-09-24+28 −1counted
ab3f7c7POSITION_INTELLIGENCEfeat(deploy): run collector-worker on the integration environment2026-09-24+1 −2counted
5bb2154POSITION_INTELLIGENCEfix(deploy): install libxml2/libxslt headers for lxml; add Procfile.c…2026-09-24+8 −0counted
ff07e3eHubstaff-GitHub-MonitoringWire OPENAI_API_KEY into the daily-sync workflow's manual-dispatch path2026-09-24+1 −0counted
a72b9b9POSITION_INTELLIGENCEIntegration: merge all live feature branches into one staging baselin…2026-09-24+59,723 −204counted
fcdd7fdPOSITION_INTELLIGENCEMerge remote-tracking branch 'origin/Feature/media-bias-closed-loop' …2026-09-24+2,910 −41counted
9bc1ee9POSITION_INTELLIGENCEMerge remote-tracking branch 'origin/Feature/console' into staging2026-09-24+8,675 −103counted
92dce12POSITION_INTELLIGENCEMerge remote-tracking branch 'origin/Feature/brightdata-profiles' int…2026-09-24+4,046 −2counted
09bccc7POSITION_INTELLIGENCEfix(quality-gate): keep promotion and dedupe correct across both coll…2026-09-24+31 −3counted
f6e5a54POSITION_INTELLIGENCEMerge remote-tracking branch 'origin/Feature/Apify_intigration' into …2026-09-24+30,185 −49counted
8a81536POSITION_INTELLIGENCEMerge remote-tracking branch 'origin/Feature/incident-news-collection…2026-09-24+13,878 −8counted
123d614POSITION_INTELLIGENCEwip(honduras): snapshot uncommitted persona fusion, contracts/v2, dat…2026-09-24+162,220 −15counted
b408a5cHubstaff-GitHub-MonitoringFix citations having no sha/PR number to actually cite2026-09-23+13 −10counted
d0682f8Hubstaff-GitHub-Monitoringbootstrap-hubstaff.ts: use /members, not /activities/daily, for the r…2026-09-23+9 −17counted
8dc7ae3Hubstaff-GitHub-MonitoringClamp bootstrap-hubstaff.ts lookback to Hubstaff's 31-day API limit2026-09-23+6 −2counted
af7329cHubstaff-GitHub-MonitoringTwo-pass ranking narration: Claude judges, OpenAI simplifies, citatio…2026-09-23+174 −8counted
edc4400Hubstaff-GitHub-MonitoringRanking prose: plain language, no em/en dashes anywhere2026-09-23+116 −1counted
5e383a7Hubstaff-GitHub-MonitoringAdd per-project monitoring (frontend + backend + ranking) and fix Hub…2026-09-23+241 −2counted
c6f8731Hubstaff-GitHub-MonitoringCapture full commit message, not just the headline2026-09-23+8 −0counted
93f8c6fHubstaff-GitHub-MonitoringFix reconcile-identities.ts crash on employees with >1 GitHub identity2026-09-23+1 −1counted
cb9c31cHubstaff-GitHub-MonitoringFix AWS_ONLY validation killing the whole scan on the first account2026-09-23+28 −7counted
40d9497Hubstaff-GitHub-MonitoringFix TLS hostname verification for IP-only DATABASE_URL2026-09-23+10 −1counted
4799d08Hubstaff-GitHub-MonitoringHide the period switcher on Ranking, and reconcile remaining identities2026-09-23+201 −16counted
ba9b47bHubstaff-GitHub-MonitoringIsolate per-event failures in sync.ts instead of aborting the whole run2026-09-23+17 −4counted
94cd167Hubstaff-GitHub-MonitoringFix generate-ranking.ts crash on infra_events.occurred_at2026-09-23+7 −3counted
1f54313Hubstaff-GitHub-MonitoringFix AWS CLI v1/v2 EventTime format mismatch crashing every AWS script2026-09-23+35 −12counted
40f879dHubstaff-GitHub-MonitoringMulti-account AWS support, and weight infra activity in the ranking2026-09-23+354 −123counted
ce0efcdHubstaff-GitHub-MonitoringAnti-gaming: judge ranking evidence against team medians, not raw counts2026-09-23+53 −3counted
33c9a3eHubstaff-GitHub-MonitoringRank on GitHub + Hubstaff evidence directly — no task tracker required2026-09-23+171 −88counted
1b33fc6Hubstaff-GitHub-MonitoringFix generate-ranking.ts: fixed max_tokens truncated valid JSON on a b…2026-09-23+42 −15counted
35ac84cHubstaff-GitHub-MonitoringFix /method 500 — EXPLAIN map was missing the infrastructure component2026-09-23+19 −1counted
403a58aHubstaff-GitHub-MonitoringFix tasks/code_changes inserts crashing on re-sync across overlapping…2026-09-23+14 −2counted
b56f063Hubstaff-GitHub-MonitoringReplace hardcoded 2026-08/09 date fallbacks with a real rolling window2026-09-22+153 −39counted
741e3d0Hubstaff-GitHub-MonitoringFix bootstrap-hubstaff.ts's no-op ON CONFLICT DO NOTHING and dedupe l…2026-09-22+94 −1counted
aac136fHubstaff-GitHub-MonitoringFix another hardcoded date window — bootstrap-hubstaff.ts orphaned re…2026-09-22+11 −1counted
ac1bc4bHubstaff-GitHub-MonitoringFix package-lock.json for Linux — npm ci was failing on the deploy box2026-09-22+22 −13counted
a1d1254Hubstaff-GitHub-MonitoringFix an empty-string env default and widen the daily-sync timeout for …2026-09-22+6 −2counted
c9bc109Hubstaff-GitHub-MonitoringAdd daily automation, a rate-limited manual sync, and a Claude rankin…2026-09-22+909 −26counted

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.