E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Dhiraj Ambekar

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

40.8

6 days tracked

Hours per day

6.8

on days with tracked time

Mean activity

24.9%

never scored

PRs opened

1

in this period

PRs merged

0

0% of opened

Median time to merge

—

nothing merged

Commits

13

4 repositories

Lines changed

6,278

context only — never scored

Identity

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

aws dhirajaws Dhiraj-Agithub Dhiraj4113hubstaff Dhiraj Ambekar

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.

Behind

71

rank 11 of 14

behind ≤ 73median 7982 ≤ leading
craft 25%85
infrastructure 15%35
consistency 12%47
change discipline 18%100
completed work 22%—
review 8%—

Why this reads as “Behind”

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.

71 of 100, ranked 11 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 bottom 30% of people with a score this period. With every component at the cohort median this person would score 81; they score 71. That difference is carried by craft (85 against a cohort median of 98, worth -4.6 points) and infrastructure (35 against a cohort median of 50, worth -3.2 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
Craft25%8598-4.639 of 50 commits name what they changed
Infrastructure15%3550-3.2278 points from 79 AWS changes on 13 days
Consistency12%4753-1code landed on 20 separate days
Change discipline18%1001000median commit 166 lines
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 71 − 81 = -10, 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: 40.8 hours tracked, 13 commits, 6,278 lines changed, 23.8% 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

12

Changes

4

Days

1

Unscored

2

sign-ins, own MFA, shells

Deployment 2 × 4ptConfiguration 2 × 2pt

What they actually did

  • cloudformation UpdateStack×1 · 4 pts
  • elasticbeanstalk UpdateEnvironment×1 · 4 pts
  • autoscaling ResumeProcesses×1 · 2 pts
  • autoscaling SuspendProcesses×1 · 2 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 40.78h 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 6 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 261 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.3348.1000
▸ 2026-09-270.00—000
▾ 2026-09-260.00—000
▸ 2026-09-258.0321.5610
▸ 2026-09-248.0819.5100
▸ 2026-09-238.0319.9300
▸ 2026-09-228.1621.1100
▸ 2026-09-218.1435.7200

Raw Hubstaff intervals · 2026-09-26

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 Project29.4h183 rows
Position10.9h73 rows
Social media0.3h4 rows
1touch ai0.1h1 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 · 1

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

PRTitleOpenedMerged+/−ReviewsFirst CI
#1
ZeroHumanMultiAgentV3
ui: collapse sidebar into Today/Office/Work/Growth/Intelligence/Settings
dhiraj/ui-simplification
2026-09-25open+98 −510—

Commits · 13 counted, 0 excluded

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

SHARepoMessageWhen+/−Counted
c83478eSocial_Media_AutomationsUpdate auth.ts2026-09-25+2 −0counted
3fe7f29Social_Media_Automationsup2026-09-25+54 −35counted
98788f8ZeroHumanMultiAgentV3ui: collapse sidebar into Today/Office/Work/Growth/Intelligence/Settings2026-09-25+98 −51counted
c1291cbSocial_Media_AutomationsMerge branch 'interaction_v2' of https://github.com/1Touch-dev/Social…2026-09-25+292 −4counted
0e6c29eSocial_Media_AutomationsUpdate auth.ts2026-09-25+0 −3counted
5476196Social_Media_AutomationsUpdate auth.ts2026-09-25+4 −0counted
bc96addSocial_Media_Automationstest2026-09-24+160 −4counted
085b863SMA_Backendfix(agent): align LangGraph deps and restore bridge auto-pivot approval2026-09-23+841 −146counted
f955504SMA_BackendMerge branch 'feature/langgraph-agent-runtime' into interaction_v22026-09-23+1,517 −87counted
072ec7cSMA_BackendRevert "feat(agent): wire live narrative pivot control and POSITION i…2026-09-23+152 −1,245counted
cfe1b37SMA_Backendfeat(agent): wire live narrative pivot control and POSITION intellige…2026-09-22+1,245 −152counted
f59697dPOSITION_INTELLIGENCEfix(agents): route Pillar 1/3 to POSITION_DB_NAME without touching ap…2026-09-21+148 −19counted
112101bPOSITION_INTELLIGENCEfeat(squada): expose campaign agent APIs on api.position.services2026-09-21+16 −3counted

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.