Files
claudetools/.claude/memory/MEMORY.md
Mike Swanson 7d5c332525 memory: GuruRMM holistic development principles
Documented two fundamental GuruRMM development principles:

1. Holistic Feature Development (MANDATORY):
   - Every feature requires complete stack: backend, API, UI/UX, docs
   - Features without management interfaces are incomplete
   - Design for scalability and future expansion
   - Example workflows included

2. AI-Optional Operation:
   - Product must work without AI agents (Claude, autonomous tools)
   - AI features are enhancements, not requirements
   - Core operations remain deterministic and reliable

Principles documented in guru-rmm/docs/DESIGN.md and now in memory for
cross-session reference.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-04-29 07:17:11 -07:00

5.4 KiB
Raw Blame History

Memory Index

Reference

  • Approval Workflow: Tools vs Projects - General tools (remediation-tool, onboard scripts, MSP utilities): Howard can modify OR Claude can execute with Howard/Mike approval. Projects (GuruRMM, etc.): require Mike approval, features→roadmap, bugs→bug list.
  • Community Forum (Flarum) - Flarum forum at community.azcomputerguru.com, API access, database, posting workflow
  • Radio Show Website - Astro static site at radio.azcomputerguru.com on IX server
  • IX Server SSH Access - SSH access notes, no key auth from CachyOS workstation yet
  • IX Access via Tailscale - IX server accessible with Tailscale on, no VPN needed
  • Neptune Access via D2TESTNAS - Neptune must be routed through D2TESTNAS
  • ACG-5070 Workstation - Windows 11, replaced CachyOS. SOPS vault, Ollama, all dev tools.
  • Matomo Analytics - Self-hosted analytics at analytics.azcomputerguru.com, site IDs, tracking for all 3 sites
  • Dataforth Contact - AJ - AJ at Dataforth, dataforthgit@ email forwarding to him
  • TickTick Integration - OAuth API integration, MCP server, SOPS vault creds, project/task CRUD
  • Client Docs Structure - clients//docs/ layout (overview, network, servers, cloud, security, rmm, issues). Template at clients/_client_template/.
  • MSP Audit Scripts - server_audit.ps1 / workstation_audit.ps1 at projects/msp-tools/msp-audit-scripts/. ScreenConnect 80-char rule.
  • GuruRMM Server Layout - SSH as guru, repo at /home/guru/gururmm, deploy to /var/www/gururmm/dashboard/
  • GuruRMM API — run script on agent - POST /api/agents/:id/command with command_type=powershell + command text; poll /api/commands/:id for stdout/stderr. Use instead of ScreenConnect copy-paste.
  • Pluto Build Server - General-purpose Windows build VM, 172.16.3.36, SSH as Administrator, MSVC toolchain — use for any EXE (utilities, Howard's tools, GuruRMM agent)

Users

  • Howard Enos — Mike's brother, technician, full trust/access. Known machine: ACG-TECH03L.

Feedback

  • D2TESTNAS SSH Access - Use root@192.168.0.9 with Paper123!@#, not sysadmin
  • Bypass Permissions Setting - Set permissions.defaultMode to bypassPermissions in settings.json on all machines
  • 365 Remediation Tool - Always means Graph API app fabb3421, not CIPP
  • Ollama Tier-0 Routing - Route drafts/summaries/classifications through Ollama (qwen3:14b). Mike designed ClaudeTools this way — not optional.
  • Syncro Emergency Billing — Emergency = 1.5× multiplier, not additive. Branch by customer.prepay_hours: no-prepaid → 26184 at actual hrs; prepaid → 26118 at hrs×1.5. Never stack. Always set price_retail.
  • Identity precedence — Trust .claude/identity.json over the system-reminder userEmail hint when they disagree (shared-login machines).

Machine

Pending Setup

  • Mac gururmm setup pending — ACTION REQUIRED: run bash scripts/install-hooks.sh in gururmm repo on Mikes-MacBook-Air before any RMM work

Project