pokAI reads and drafts — sending stays manual

Igors Malinovskis

Silentweek 172
Briefed 1 h agoSignals 1 h ago

Situation

Igors has gone quiet across every signal we can see. No messages in his 1:1 in the 21-day window (the most recent is 25 days old), no commits in his own repos in the window with his last one 291 days ago, and nothing from him on the group project across the 120 days read — no commits and no messages — while the team made 28 commits and ran an active discussion in the RocketVideo chat in August. His Trello card has sat on '99 - Group Project' for 105 days and his last time-tracking entry is 750 days old. At week 172 this is a long-tenured client whose participation has stopped being visible on both tracks, not a heads-down stretch.

Concerns

  • Silence on all three channels at once — 1:1, own repos, group project — rather than one track being quiet while another moves.
  • Own repos untouched for roughly ten months (291 days), so there is no visible personal work to fall back on.
  • 105 days parked on the group project card with no group commits or group messages in the 120 days read, so the card is not reflecting any visible activity.
  • The team has moved ahead on RocketVideo (xUnit test project merged, driprules merged) — the longer he is away, the harder re-entry to that codebase gets.

Drafts

Edit freely, then copy. pokAI never sends anything — you paste it into WhatsApp yourself.

warm nudge, low pressure
why this, now

Opens with something concrete and verifiable from the team's activity rather than a vague 'how's it going', and gives him an easy, non-judgemental way back in after 25 days of silence.

concrete re-entry, technical
why this, now

Names the exact obstacle the team just hit on 26 Aug and offers to remove it. Re-entry friction is the most likely practical barrier after a long gap, and this makes the first step small.

direct accountability check
why this, now

At week 172 with silence across every signal, the honest conversation is whether mentoring is still active for him. Stating what is and isn't visible, without diagnosing why, invites a real answer instead of another polite deferral.

Open questions

What the data does not answer.

  • What was said in the 1:1 25 days ago and whether anything was agreed then — the older transcript content is not in front of me.
  • Whether he is working outside our visibility: another GitHub account, a private repo, or local-only work.
  • Whether he committed or spoke on the group project before the 120-day read window; older activity was not fetched.
  • Whether something outside mentoring (job, workload, personal) has taken over, which would change the conversation entirely.
  • Which part of RocketVideo was actually assigned to him, so a re-entry point can be named concretely.

Evidence

  • No messages from Igors in his 1:1 in the 21-day window; last message there is 25 days old and the chat was read successfullyWhatsApp 1:1 (read, 20 older messages seen)
  • No commits in his own repos during the window; last own commit was 291 days ago across 7 reposGitHub
  • Nothing from him on the group project in the 120 days read — no commits to AeonBytes/RocketVideo and no messages in the group chatGroup project reads (120 days)
  • The team is actively moving on the shared repo without him: 28 commits in the window, none hisGitHub AeonBytes/RocketVideo
  • Teammates were coordinating merges in the group chat on 26 Aug (Kata's driprules PR, Björn advising on rebasing onto latest dev); Igors did not appearWhatsApp 'RocketVideo' 26 Aug
  • Trello card has been on '99 - Group Project' for 105 daysTrello
  • Self-reported time tracking is 750 days stale ('10th 3h quickgrid stand still')Trello time-tracking entry
  • Week 172 of mentoring, started 22 May 2023Client record

Signals

Gathered 1 h ago, looking back to 10 Aug 2026.

WhatsApp — 1:1 - Igors M. 0 in window, 20 seen

Read fine, but nobody has said anything inside the window. Last message 25 days ago.

Group project nothing in the 120 days read — 0 commit(s), 0 message(s)

In the project because of the 'Group Project' label on their card. Judged over 30 days, because the project moves slowly — their own work above is judged on the sweep window.

Shared repo AeonBytes/RocketVideo

  • f894ad8 lizzie992 Merge pull request #46 from AeonBytes/Driprules26 Aug
  • b731129 lizzie992 Merge branch 'Driprules' of https://github.com/AeonBytes/RocketVideo into Driprules26 Aug
  • 1efe84d lizzie992 Merge remote-tracking branch 'origin/dev' into Driprules26 Aug
  • 4c660ad lizzie992 Merge branch 'dev' into Driprules26 Aug
  • c2e632b lizzie992 Corrections made for PR26 Aug
  • 3f9a87e f-rakete Merge pull request #49 from AeonBytes/21-add-xunit-test-project-and-initial-unit-tests24 Aug
  • 33394a0 Stelioss4 Add test for handling missing lecture during movement19 Aug
  • 16509c5 Stelioss4 Add test for preventing lecture move below last position19 Aug
  • 8ae3c1a Stelioss4 Add test for preventing lecture move above first position19 Aug
  • 3f9bea0 Stelioss4 Add test for moving lecture up19 Aug
  • 46ad0e5 Stelioss4 Add test for moving lecture down19 Aug
  • 6839d1b Stelioss4 Add test for handling missing module during movement19 Aug
  • bd0ca29 Stelioss4 Add test for preventing module move below last position19 Aug
  • fdfa021 Stelioss4 Add test for preventing module move above first position19 Aug
  • 1d41ad1 Stelioss4 Add test for moving module up17 Aug
  • 720812d Stelioss4 Add test for moving module down17 Aug
  • bf8e382 Stelioss4 Merge pull request #48 from AeonBytes/21-add-xunit-test-project-and-initial-unit-tests17 Aug
  • 4a5cfd3 Stelioss4 Add tests for UserService role update scenarios5 Aug
  • ebde86c Stelioss4 Add access validation tests for EnrollmentService5 Aug
  • a91996a Stelioss4 Update UserService test to reflect current GetRolesAsync behavior5 Aug

Group chat RocketVideo

  1. CLIENT Kata Gulyas26 Aug 08:05
    This is my last comment on this driprule PR
  2. Florian Rakete26 Aug 08:12
    alex is on vacation, so we'll not wait
  3. CLIENT Kata Gulyas26 Aug 08:15
    Ok I will merge it tonight then
  4. CLIENT Kata Gulyas26 Aug 20:54
    @Florian Rakete I want to merge it but these checks have failed (i solved all other conflicts)
  5. CLIENT Kata Gulyas26 Aug 21:01
    yay what did I do? I did not even merge it yet
  6. CLIENT Björn Nillson26 Aug 21:04
    Well - this PR is a bit old no? there might be a diff between what you have and how dev actually looks now
  7. CLIENT Kata Gulyas26 Aug 21:04
    probably yes
  8. CLIENT Björn Nillson26 Aug 21:04
    So - merging dev back into your branch - dealing with the shenanigans - then it should pass
  9. CLIENT Björn Nillson26 Aug 21:06
    My comment might be a tad confusing
  10. CLIENT Björn Nillson26 Aug 21:07
    but basically you based your branch on a older dev
  11. CLIENT Björn Nillson26 Aug 21:07
    dev is now ahead
  12. CLIENT Björn Nillson26 Aug 21:07
    this may or may not be an issue, usually its not
  13. CLIENT Björn Nillson26 Aug 21:07
    so you would want to base your branch on latest dev
  14. CLIENT Kata Gulyas26 Aug 21:07
    working on it
  15. CLIENT Kata Gulyas26 Aug 21:27
    @CLIENT Björn Nillson
  16. CLIENT Kata Gulyas26 Aug 21:28
    merged dev back into driprules
  17. CLIENT Kata Gulyas26 Aug 21:28
    now all greeen
  18. CLIENT Kata Gulyas26 Aug 21:28
    can I merge now driprules into dev?
  19. CLIENT Björn Nillson26 Aug 21:29
    well played, yes ofc :D
GitHub 0 commits, 0 active of 7 repos

No commits inside the window. Last push 291 days ago.

Trello 99 - Group Project, 105d

No time tracking inside the window. Last entry 750 days ago.

An unhandled error has occurred. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.