why this, now
The primary issue is the lapsed contact, not the code. Naming the gap plainly and giving him an easy honest answer is more likely to get a reply than a technical question.
Seleman has gone quiet on every signal available: no commits in the 21-day window, no WhatsApp messages in the window (last message is 49 days old), and his own last commit was 74 days ago across 15 repos. Trello has him on '17 - Own Project - UI' for 410 days, with a self-reported time entry from 837 days ago. At week 143 of mentoring this is a long-standing client whose contact has lapsed rather than someone new drifting, and the pattern is silence plus no code, which is a check-on situation rather than heads-down work.
Edit freely, then copy. pokAI never sends anything — you paste it into WhatsApp yourself.
The primary issue is the lapsed contact, not the code. Naming the gap plainly and giving him an easy honest answer is more likely to get a reply than a technical question.
Gives a concrete hook (the June commits, the UI card) and shrinks the re-entry cost, which matters after 410 days on one exercise. Asks him to describe the state rather than assuming what the blocker is.
At week 143 with a 410-day-old exercise and total silence, the useful move is offering an explicit decision point, including permission to change direction. Keeps it peer-to-peer and avoids diagnosing why he went quiet.
What the data does not answer.
Gathered 1 h ago, looking back to 10 Aug 2026.
Read fine, but nobody has said anything inside the window. Last message 49 days ago.
No commits inside the window. Last push 74 days ago.
No time tracking inside the window. Last entry 837 days ago.