azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from HOWARD-HOME at 2026-06-24 15:39:19

Browse Source 
Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-06-24 15:39:19
This commit is contained in:
Howard Enos
2026-06-24 15:39:54 -07:00
parent 8ddfb33eab
commit 9d68db953f
5 changed files with 309 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.claude/memory/MEMORY.md
View File

@@ -135,6 +135,7 @@
- [Only RMM & GC are versionable products](project_versionable_products.md) — GuruRMM + GuruConnect are the only products with own repos/submodules; everything else stays in the claudetools monorepo. Split only for independent pipeline OR versioned external consumer.
- [Quantum GoDaddy M365 tenant](project_quantum_godaddy_m365_tenant.md) — quantumwms.com parked in a GoDaddy-provisioned M365 tenant (id ddf3d2c9-b76c-40d9-a216-9f11a1a26f97, netorg18235235.onmicrosoft.com); blocks Pax8 migration until GoDaddy removed.
- [Howard-Home LAN shadow (RESOLVED)](howard-home-lan-shadow.md) — Howard-Home renumbered 2026-06-16 to **10.137.42.0/24** (gw 10.137.42.1, UniFi — NOT pfSense), off the old 192.168.0.0/24 that shadowed Cascades pfSense .0.x over the VPN. Cascades .0.x should now route via the tunnel; this machine is 10.137.42.x now (not 192.168.0.x).
- [Cascades CARF tech plan](project_cascades_carf_tech_plan.md) — Ashley's "technology plan" is a CARF accreditation deliverable (Aging Services Technology and System Plan standard); must use CARF action-plan structure (owner/cost/target+completion dates per area), persons-served assistive-tech lens, annual-review sign-off; it's Cascades' leadership-adopted plan, ACG supplies content.
- [Cascades](project_cascades.md) — Active state: Syncro ticket #110680053 + plan file (machine-specific path on Howard's box), admin accounts (sysadmin@=Howard, admin@=Mike — daily-driver, NOT break-glass), Phase-B caregiver CA pilot (SG-Caregivers-Pilot, group-scoped never tenant-wide), prepaid block ~37.5h (rate TBD), pilot cleanup checklist.
- [Cascades history](project_cascades_history.md) — fdeploy 502/ACL root cause (Flags=1211→187 fix), 2026-04-29 CA-rescoping decision (Howard pulled the brakes on tenant-wide), 2026-05-14 per-user-security-group decision rationale.
- [Cascades isolated-VLAN pattern](project_cascades_isolated_vlan_pattern.md) — pfSense: the GUEST VLAN (VLAN50/igc1.50) is the isolation template (4 any-proto quick rules: block 192.168.0.0/22 + 10.0.0.0/8 + 172.16.0.0/12, then pass any; public DNS via DHCP). VLAN20 is NOT isolated. Verify with `pfctl -sr`, not config.xml. Protocol MUST be Any (TCP-only leaks UDP). VOICE VLAN30 built to this 2026-06-17.

27
.claude/memory/project_cascades_carf_tech_plan.md Normal file
View File

@@ -0,0 +1,27 @@
---
name: project_cascades_carf_tech_plan
description: Cascades technology plan is a CARF accreditation deliverable, not an MSP status report
metadata:
type: project
---
The Cascades of Tucson "technology plan" Ashley Jensen requested (2026-06) is for **CARF
accreditation** (Commission on Accreditation of Rehabilitation Facilities, Aging Services
program). Her agenda list maps to CARF's **Technology and System Plan** standard (Section 1
"CARF Plans"; the 8 canonical areas: hardware, software, security, confidentiality, backup,
assistive technology, disaster recovery, virus protection).
**Why it matters:** the document is **Cascades' plan, adopted by their leadership** (ACG is the
IT partner who supplies the technical content), NOT an ACG sales/status doc. CARF surveyors
check it as a **living action document** that, for each area, lists: current tech + unmet/
projected needs + timeline + possible vendor + estimated/actual cost + person responsible +
target date + completion date. Must be **based on needs of persons served/personnel/stakeholders**,
**aligned to the strategic plan**, and **reviewed/updated at least annually with dated sign-off**.
**How to apply:** any Cascades tech-plan deliverable must use the CARF action-plan structure
(owner/cost/dates columns), include a resident/persons-served assistive-technology dimension,
a backup-policy section, and a version/annual-review block. CARF passes on a credible REVIEWED
plan, not on zero gaps. Verify exact standard citation + review cadence against their current
Aging Services Standards Manual (2025/2026 edition). Deliverables live in
`clients/cascades-tucson/docs/proposals/`. Pairs with [[feedback_impeccable_on_outbound]],
[[policy_pricing_verification]] (cost figures must be verified).