User Manual: Operating & Collaborating with Dirk Jan Buter

Model Number: 1979-11-15

Core Classification: The Chaotic Visionary Alchemist

Section 1: Executive Summary & Core Philosophy

Dirk operates as a high-fidelity, structure-resistant cognitive processor. He specializes in transforming highly disorganized, chaotic inputs into clean, elegant, and robust technical or creative systems.

To work effectively with him, you must understand a fundamental paradox: his external output projects calm, deliberate competence, while his internal engine runs on intense, restless energy.

He is driven by three core operating principles:

1. Hyper-Focus as Identity: When a project captures his interest (AI, systems architecture, low-level coding, or philosophical writing), he will channel 100% of his cognitive capacity into it.
2. Social Interaction as a Battery: Unlike typical introverts, close 1-on-1 exchanges and deep group alignments do not drain him—they actively recharge his system.
3. Absolute Autonomy: He requires complete control over his environment, schedule, and self-expression. Any attempt to force rigid, arbitrary corporate structures or micromanagement on him will cause immediate system disengagement.

Section 2: Communication Protocols (How to Exchange Data)

Dirk’s communication style is optimized for rapid throughput, high transparency, and low bureaucratic friction.

Digital Text Format (The “Burst” Protocol)

Dirk rarely sends long, monolithic paragraphs. Instead, expect a rapid stream of 10 to 20 short, punchy messages in sequence. He frequently omits formal punctuation and utilizes emojis (😉, 😁, ❤️) to signal intent and warmth.

• Response Latency: Dirk often formulates replies instantly in his head but may delay sending them until official business days to protect his focus.
• The Inbound Filter: Do not send him long, rambling paragraphs or dense, multi-page emails. If you do, your message will likely join the 20,000+ unread notifications sitting dormant in his inbox. Keep your text bite-sized and direct.
• Voice Notes: He transmits voice notes with high enthusiasm, but he processes incoming voice notes poorly. Always prefer text over audio when sending information to him.

Face-to-Face & 1-on-1 Dynamics

In person, Dirk pairs a calm physical presence with a gentle, Dutch-accented wit.

• Ditch the Small Talk: He tolerates casual pleasantries only as a brief 60-second bridge to cross into deeper, high-signal topics like biotech, autonomous systems, AI cloning, or social philosophy.
• Conversational Leadership: Dirk naturally likes to lead 1-on-1 conversations. If he gets highly excited about an idea, he will interrupt. This is not a sign of disrespect; it is a sign that his engine is firing at maximum velocity.
• Radical Candor: He prefers raw honesty. If a joke falls flat, or an argument lacks logical cohesion, he will simply state it plainly. He uses silence comfortably and expects you to do the same.

Section 3: Operational Mechanics & Cognitive Flow

The Bimodal Circadian Rhythm

Dirk does not operate on a standard 9-to-5 loop. His energy curve hits two massive peaks during the 24-hour cycle:

[07:00 - 10:00: Early Morning Peak] ➔ [13:00 - 16:00: The Mundane Slump] ➔ [21:00 - 02:00: Night Owl Deep Focus]

• The Morning Launch: His day begins sharply after morning movement and a coffee post-school drop-off. This is an excellent time for high-level conceptual alignment.
• The Night Peak: His deepest, most uninterrupted systems-building occurs late into the night. He treats sleep as a secondary necessity to creative or technical momentum.

Task Management & System Friction

Dirk coordinates his life and technical architectures through highly trusted, low-structure systems (like Obsidian notes). He prioritizes tasks strictly by personal interest and impact, completely ignoring external, artificial urgency frameworks.

• The Mundane Avoidance Trap: Dirk possesses an intense cognitive aversion to administrative tasks, routine housework, and repetitive paperwork. When forced into these cycles, his system hits a “slump.”
• The Subconscious Reset: When Dirk hits a complex technical bottleneck (e.g., debugging a real-time graphics pipeline or structuring a difficult essay), he will walk away. Do not force him to sit at the desk and brute-force it. He regulates by taking short garden walks, grabbing a coffee, or watching brief, low-effort videos to let his subconscious process the solution. He will return shortly with the exact architecture needed to fix the issue.

Section 4: Behavioral Examples & Troubleshooting

Scenario A: Resolving an Intense Project Conflict

• What NOT to do: Send a formal, defensive 5-paragraph email or schedule a corporate HR-style feedback alignment meeting three days from now. This causes internal friction and delayed resentment.
• What TO do: Step into a 1-on-1 space immediately. State the problem with empirical logic and complete transparency. Dirk handles direct conflict exceptionally well. He might raise his voice if he is genuinely passionate, but he breathes, processes, and seeks a rapid, collaborative resolution focused on moving forward.

Scenario B: Presenting a Task or Project to Him

• Bad Input: “Dirk, I need you to fill out this 5-page project specification form, log your hours in Jira, and follow this strict daily template for updates.”Result: Total system shutdown. The project will be indefinitely delayed.
• Good Input: “Dirk, here is the messy, unorganized raw data and the ultimate vision we need to hit. Build the architecture from scratch your way. Keep us posted over chat when you hit major milestones.”Result: Complete hyper-focus. He will deliver a high-performance, native solution ahead of schedule.

Scenario C: Handling Praise and Reassurance

• Context: Despite obvious technical milestones (building custom engines, founding media platforms, pioneering AI clone design), Dirk is highly sensitive to people misjudging his cognitive depth due to physical speech patterns or motor skills. This can occasionally manifest as a defensive mask of supreme competence.
• Actionable Advice: Skip generic, superficial compliments (“Wow, you’re so smart!”), which his system struggles to internalize. Instead, validate the logic, authenticity, and execution of his work (“The way this specific C module handles low-latency audio is incredibly elegant.”). This bypasses the defensive matrix entirely.

Summary of Core Directives

🟩 DO: Speak in punchy, direct text bursts; engage him in deep, speculative “what if” technical conversations; respect his absolute need for physical and scheduling autonomy; hand him chaotic problems to solve.

🟥 DON’T: Force him into rigid administrative routines; send long voice notes; hide your true thoughts behind corporate politeness; micro-manage his workspace layout or midnight operational hours.