Primary deep-work environment for coding agents, repo work, and long-running implementation loops.
Tech Stack / Hardware
Hardware
The hardware and runtime surfaces behind Viggo Meesters’ workflow: Mac deep work, Windows/WSL execution, and mobile command capture.
Current shape
Quiet local cockpit for Telegram/Hermes work, Windows files, vault mirror reads, and pragmatic automation.
Telegram-first quick command bus for capture, reminders, voice, repo instructions, and lightweight review.
Why this belongs in the stack
Hardware is listed only when it changes how work gets done: quiet local execution, reliable command input, mobile capture, or long-running agent loops.
It matters when a machine, input device, or always-on runtime surface becomes part of the default workflow.
What stays out
Do not list every accessory. Keep only durable surfaces that explain the operating setup.
Vault structure, schemas, validation, and agent capture routes live under Personal Knowledge System, not here.
How it earns a place
Devices belong here when it is a recurring command surface, execution host, or capture surface. Remove accessories that do not explain the operating model.
The hardware layer is current when the listed machines map to real daily roles: deep work, quiet WSL execution, mobile capture, or long-running agent work.
It matters when the default coding machine, WSL cockpit, mobile command surface, or always-on execution host changes enough that a visitor would misunderstand the operating setup.
Concrete example
The Windows/WSL machine is not listed as generic hardware; it matters because it is the quiet Telegram/Hermes cockpit with access to Windows files and bounded vault mirror reads.