The useful thing about reviewing work threads is that they reveal the actual operating system: what moved, what stalled, and where a decision is being disguised as more research.
Each thread gets one line: current state, next concrete action, unresolved question, and whether it still deserves attention tomorrow.
Thread notes
- The WGTakt chatbot is the origin thread: a WhatsApp-based test of reminders, availability, task completion, and natural conversation for a real WG.
- The WGTakt mobile app is the product thread that came out of the bot: rolling chores, linked chains, rich push actions, events, and WG community features.
- The cost article work needs sharper source discipline. The argument is stronger when every number has a reason to exist.
- Pressroom wants a quieter interface. The value is speed, clarity, and confidence, not another dashboard that asks to be admired.
- Neeed needs a tighter first-use loop: one obvious action, one useful result, and enough context to make the second action feel natural.
- Vividish is the taste thread. The work is less about adding features and more about choosing a visual language that can carry the product.
- Edelweiss, Santorino, VisualMenu, SEO Dashboard, and Prototype should be tracked as separate taste and tool-building lanes instead of disappearing into a generic projects bucket.
The review is worth doing because it prevents project memory from living only in chat history. The blog becomes the index.