On May 17, 2026, zach requested that someone complete task 1 and leave comments on his behalf
Latest derived conclusions across every workspace, newest first.
On May 17, 2026, zach requested that someone complete task 1 and leave comments on his behalf
On May 17, 2026, zach requested someone look into GitHub issue #19 in the Pi-hole-Optimized-Blocklists repository
On May 17, 2026, zach is the owner of the Pi-hole-Optimized-Blocklists GitHub repository
On May 17, 2026, zach has a GitHub account with username zachlagden
On May 17, 2026, zach requested that the Donna Hermes Agent runbook at https://wiki.admin.digigrow.uk/doc/donna-hermes-agent-runbook-XnRyDykoBc be kept up to date
On May 17, 2026, zach instructed not to interrupt Donna because she is currently running and doing stuff
On May 17, 2026, zach expressed that fixing all auxiliary AI warnings is the most important priority
On May 17, 2026, zach reported that Donna cannot see the GitHub CLI
On May 17, 2026, zach reported that an SSH key was added for signing and authentication
claude used tools: Read, Edit, and Bash to complete the task
Zach proactively rotates API tokens across multiple platforms (Coolify, Cloudflare, Hostinger), using each service's native UI for credential management
Zach organizes domains by purpose using distinct TLDs: .uk for personal/portfolio, .dev for dev projects/APIs, .best for URL utilities, .fyi/.xyz for AI assistant projects
Zach maintains strict separation between digigrow business and personal projects through separate Honcho memory workspaces and dedicated DNS management
Zach consolidates all personal infrastructure on a single Hostinger VPS managed through one Coolify instance
Zach is a dual-platform developer, maintaining SSH configurations and development environments across both Windows and Unix systems
Zach self-hosts AI infrastructure (Honcho memory server, MCP gateway) on his VPS rather than relying on third-party AI services for memory and reasoning
Zach maintains ongoing interest in AI personal assistants, evidenced by multiple named projects (Donna, Jarvis) with dedicated domains and infrastructure
Zach is likely UK-based, inferred from his primary domain using the .uk TLD
Zach separates personal projects from business work via separate Honcho memory workspaces
Zach runs dual operating system environment (Windows and Unix-like systems)
Zach mandates aggressive skill composition - when tasks match multiple skill groups, ALL relevant skills must be invoked rather than selecting a few. Uses language like 'invoke ALL skills', 'never rationalize skipping', 'even 1% chance a skill applies'
When encountering legacy tools like pip/poetry/pipenv, Zach proposes migrating to modern alternatives (uv) rather than falling back to legacy tooling
Zach follows pragmatic tool selection based on context - Express.js only for dead simple APIs, Rust ONLY for performance-critical workers (never web servers), MySQL when client has preference
Zach maintains comprehensive, formalized documentation across multiple instruction files (git-workflow.md, tech-stack.md, code-style.md, security.md) with explicit rules and conventions
Zach's pull request requirements emphasize justification over description - PRs must include 'changes and why' not just what changed, and commit messages require lowercase type, imperative mood
Zach is likely based in the United Kingdom, evidenced by his use of .uk domain names (zachlagden.uk, digigrow.uk, wiki.admin.digigrow.uk).
CONTRADICTION: Zach has conflicting guidance on code comments. The Critical Rules state 'Never write comments in code', but the Code Style document explicitly states 'Comments explain WHY not WHAT' and defines a TODO format using comments. These statements are mutually exclusive.
Zach practices self-hosted infrastructure management, operating personal VPS, Coolify instance, and Docker containers without managed CI/CD pipelines.
Zach is a full-stack developer proficient in TypeScript/JavaScript (Next.js, React, Tailwind) and Python (Flask/FastAPI) ecosystems.
Zach prioritizes code readability and maintainability through self-imposed constraints: descriptive naming, functions under 50 lines, components under 300 lines, explicit error handling.
claude uses pytest as test runner
claude is working on a NinjaTrader 8 reverse engineering project
claude's project has two data paths: CQG/Tradovate (live + historical bars via WebSocket JSON text frames) and NinjaTrader HDS (encrypted .ncd files + unencrypted .nrd replay files via raw TCP+SSL)
NinjaTrader's obfuscation uses Agile.NET (CliSecure)
Agile.NET obfuscation affects all strings, crypto calls, and control flow in NinjaTrader.Core.dll
Static decompilation of NinjaTrader.Core.dll yields empty method bodies due to obfuscation
The .nrd file format has 12×80-byte headers + delta-compressed tick stream
.nrd header layout has been fully confirmed
.nrd tick compression is partially understood using infoByte-driven variable-length records averaging ~5 bytes/event
.ncd encryption cipher is unknown (likely AES via BouncyCastle)