Mike Swanson
1a0bcc80b0
Audit of .claude/memory found and fixed: - Broken link: Power Failure Runbook (../.claude/... -> ../...) - 8 orphaned memories not in MEMORY.md index (Graph CA/password-reset, vault-write-sequence, GURU-BEAST-ROG, 3x Cascades, identity proposal) -> now indexed under their sections, so they're discoverable - 5 files missing frontmatter -> added name/description/type - Duplicate index entry for reference_workstation_setup.md -> deduped - Trimmed the worst oversized index hooks (Syncro invoice line was 427 chars) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
4.8 KiB
name, description, type
| name | description | type |
|---|---|---|
| GuruRMM Development Principles | Every GuruRMM feature is full-stack (backend+API+UI+docs+scalability); product works without AI; the FEATURE_ROADMAP entry update is part of definition-of-done. Mirrors guru-rmm/docs/DESIGN.md. | project |
GuruRMM Development Principles
Created: 2026-04-29
Authority: Mike Swanson (owner)
Location: Documented in projects/msp-tools/guru-rmm/docs/DESIGN.md
Holistic Feature Development (MANDATORY)
When planning or implementing ANY GuruRMM feature, the complete stack must be considered and built:
Required Components for Every Feature:
- Backend/Agent Logic — core capability implementation
- API Endpoints — control and monitoring interfaces
- UI/UX — dashboard configuration, status display, management interface
- Documentation — user guides and operational docs
- Scalability Design — architected for future expansion
Example: Network Discovery Node
A complete implementation includes:
- Agent-side scanning capability (ICMP, ARP, SNMP)
- Server-side data storage and API endpoints
- Dashboard UI for:
- Designating which agent is the discovery node
- Viewing discovered devices
- Configuring scan schedules
- Setting IP ranges and exclusions
- Status indicators (discovery progress, last scan time)
- Future-proof data model supporting multiple discovery methods
Why This Matters:
- Completeness: Features without UI are unusable by non-API-expert admins
- User Experience: Configuration should be intuitive, not require documentation diving
- Consistency: Every feature should feel native to the product
- No Dead Ends: Design decisions shouldn't block obvious next steps
Features shipped without their UI/configuration interfaces are incomplete and will be rejected.
Living Roadmap (MANDATORY)
projects/msp-tools/guru-rmm/docs/FEATURE_ROADMAP.md is the single living record of intent — where the product is going AND where it has been. It is a status-and-plan tracker, NOT a write-once backlog. Convention: [ ] = planned, [x] = shipped (annotate with date).
Consult it going in, update it coming out — the roadmap update is part of definition-of-done:
- Before building: read the feature's roadmap entry for intent/scope. New work that isn't on the roadmap gets an entry first.
- When shipping or modifying a feature: update its roadmap entry in the SAME change — flip
[ ]→[x]with a date, or revise/add the item. A code change that ships or alters a roadmap feature WITHOUT touching FEATURE_ROADMAP.md is incomplete (same standard as shipping without UI). - Don't over-claim: an entry's text must match what's actually built. If only part is done, keep
[ ]and annotate the scope (e.g. "TCP probing shipped; ICMP/ARP/SNMP pending") rather than flipping.
/rmm-audit's roadmap pass is the backstop that reconciles drift — it is not the primary maintainer. Dev work keeps the roadmap honest; the audit catches what slipped. See feedback_rmm_dev_is_mike (RMM dev is Mike's).
AI-Optional Operation
GuruRMM must be fully functional without requiring AI agents (Claude, autonomous analysis tools) to operate.
Core Requirements:
- All functionality accessible via traditional dashboard/API
- Configuration and management through standard interfaces
- Usable by MSP techs with zero AI/ML knowledge
- Deterministic, reliable operation for production environments
AI Features Are Enhancements:
- Agentic analysis (AI-powered log analysis, anomaly detection, troubleshooting) — planned enhancement
- Agentic command routing (intelligent decision-making about command execution) — planned enhancement
- Users choose whether to enable AI features
- Product does not mandate AI usage
Why This Matters:
- Real MSPs need deterministic, reliable systems
- AI features can break, hallucinate, or be unavailable
- Core operations cannot depend on AI availability
- Production stability over experimental features
Application to Development
When Adding Features:
- ✅ Design the complete stack before starting implementation
- ✅ Include UI mockups in feature planning
- ✅ Consider future expansion in data model design
- ✅ Ensure feature works via dashboard without API knowledge
- ✅ Never assume AI availability for core functionality
When Reviewing Features:
- ❌ Reject backend-only implementations without UI
- ❌ Reject features that require API expertise to configure
- ❌ Reject designs that paint into architectural corners
- ❌ Reject features that require AI to function
Planning Questions:
- "How does an admin configure this in the dashboard?"
- "What does the status display look like?"
- "How do we expand this in v2/v3?"
- "Does this work if AI services are unavailable?"
These principles apply to ALL features — past, present, and future.