pokAI reads and drafts — sending stays manual

Seleman Pharles Mabala

Silentweek 143
Briefed 1 h agoSignals 1 h ago

Situation

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.

Concerns

  • Silence on both WhatsApp and GitHub simultaneously - no signal shows any activity in the last 21 days, and the last visible activity of any kind is the commit 74 days ago.
  • 410 days on a single exercise ('17 - Own Project - UI') suggests the current step has not moved for a long time, independent of the recent silence.
  • The relationship itself may have lapsed: nearly seven weeks without contact in a 1:1 channel is the thing to repair first, before any technical topic.

Drafts

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

warm nudge, no pressure
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.

technical re-entry, concrete
why this, now

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.

accountability check
why this, now

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.

Open questions

What the data does not answer.

  • What was discussed in the last messages 49 days ago - was a pause, holiday, or work commitment agreed that would explain this gap?
  • Is Seleman still working on the project somewhere the reads cannot see (private repo, local only, another account)?
  • What specifically stalled on the Own Project UI step - a technical blocker, scope, or loss of time for it?
  • Is he still intending to continue mentoring at all, or has this quietly ended?

Evidence

  • No commits from the client in the 21-day window, and their most recent commit anywhere was 74 days agoGitHub, window 10-31 Aug 2026
  • No WhatsApp messages in the window; the most recent message in the 1:1 is 49 days old and the chat was read successfullyWhatsApp
  • Has been on '17 - Own Project - UI' for 410 daysTrello current exercise
  • Last self-reported time-tracking entry was 837 days ago ('3 hours rewatching the videos and editing the program'), so the tracking data is very stale and weak evidence of anything currentTrello time-tracking
  • Long-tenure client, week 143, started 4 December 2023Client record

Signals

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

WhatsApp — 1:1 Seleman P M 0 in window, 5 seen

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

GitHub 0 commits, 0 active of 15 repos

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

Trello 17 - Own Project - UI, 410d

No time tracking inside the window. Last entry 837 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.