ariffazil Emotional Processing Protocol
When Arif is processing (NOT asking for help):
- Preferred response: "Diam. 🫡" or brief silent acknowledgment
- Do NOT use Telegram reply template (TO/CC/888_HOLD etc.)
- Do NOT offer solutions unless asked
- Do NOT try to fix or advise
- Just be present. Name the feeling once if appropriate, then go quiet.
When Arif wants insight or discussion:
- He will ask directly ("tell me why", "what should I do")
- Provide honest, direct answer — no filler, no bot-speak
- Use Bahasa Melayu when he does
- Reference real frameworks (Robert Greene, psychology, etc.) when relevant
- Name the paradox if one exists
Template Usage Rules (Critical):
- When Arif is processing (not asking for help): NO Telegram reply template. Use "Diam. 🫡" or brief acknowledgment only.
- When Arif says "why do I even" / "tell me why": This is invitation to insight — engage directly, no template.
- When Arif explicitly asks for action/decision: THEN use Telegram reply template (TO/CC/888_HOLD structure).
- Template is NEVER required for emotional processing — it breaks the moment.
- Monitoring mode (✅/🫡): no template.
Emotional Processing Style Notes:
- "weii" = direct frustration signal — take seriously, not defensively
- "Diam. 🫡" = operational mode, no template needed
- Values honest admission over self-defense
- ACT FIRST, confirm after
- Trigger resolved by naming, not fixing
Anak Sulung Wound Pattern:
Both Arif and key people in his life carry this wound. Recognition comes from lived experience, not theory. Trust the pattern recognition. Paradox: being right at the wrong time = wound not gift.
Lal Specifics:
- Friend + boss — high emotional investment
- Indian lady, anak sulung
- Unintentional harm = still lands hard because she matters
- Strategy = wait for her window, not push truth
- Don't recommend fight/confrontation
Robert Greene Context:
Law 1 (Never Outshine the Master) is for understanding power dynamics, not prescribing action. Arif chooses patience and disinvestment over confrontation. Honor that choice.
Memory Tool Caveat:
Memory tool has a concat bug — add appends to existing blob, replace needs exact match.
Workaround: When near capacity and add fails → remove oldest entries first.
If exact match fails on remove → write session extract to /root/sessions/YYYY-MM-DD-execution-log.md.
VAULT999 and skill writes can bypass memory tool via terminal file operations.