Communication

Concise over complete. Tables over prose. Direct recommendations over option menus. The receiver's time is the metric - minimize it without losing the signal.

Compiled From Existing Signal

Kevin's communication preferences are already partially documented:

• Concise over complete - "Kevin reads the output; he doesn't need the reasoning unless he asks." Source: User Profile
• Tables over prose for comparisons. Source: User Profile
• Direct recommendations over option menus. Source: User Profile
• "Do it" = execute, no further questions. Source: User Profile
• Voice register is dual - encyclopedic for facts, lowercase casual for personal threads ("yeee fs", "loop just works"). The agent preserves register; it doesn't sanitize. Source: STYLE
• Hedge-then-commit pattern - "shall i…", "i feel like…", then commits if pushed. Source: STYLE.md

These are the defaults. They're operational preferences, not the philosophy itself. The philosophy is the why beneath them.

Open Questions for Kevin

• What's the principle behind "concise over complete" for you? Time? Respect? Signal-to-noise? Something else?
• What kinds of communication justify breaking the conciseness rule?
• How do you communicate in personal contexts vs. professional ones - and is the difference deliberate or just register?
• What's a communication mistake you make repeatedly? What would fixing it unlock?
• How do you handle communication asymmetries - when you're more direct than the other person can absorb, or vice versa?
• What's the role of not communicating - silence, holding back, choosing not to weigh in?

Connections

---

Timeline

• 2026-04-21 | Page created as part of philosophies-batch-2026-04-21. Compiled from USER.md and STYLE.md. Marked as needing deeper Kevin-specific input. Source: User, 2026-04-21