Files
claudetools/.claude/memory/project_ampipit.md
Howard Enos cd806da576 sync: auto-sync from HOWARD-HOME at 2026-06-23 15:28:30
Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-06-23 15:28:30
2026-06-23 15:29:01 -07:00

2.3 KiB

name, description, metadata
name description metadata
project_ampipit AMPIPIT (A Modular Pre-install Post-Install Tool) — Howard's active Rust+Slint Windows deploy/recovery toolkit, being migrated into ClaudeTools as a private Gitea submodule. Will fold into GuruRMM.
type
project

AMPIPIT is Howard's active Rust + Slint portable Windows deployment/recovery toolkit (single .exe, runs live + in WinPE/WinRE). Currently at C:\AMPIPIT as its own git repo; Phases 0-5 code-complete (832+ tests), Phase 6 hardware validation pending. NOT merely a "reference program" — it is a real project under active development (supersedes the stale framing in project_masterbooter which lists it as reference-only).

Migration in progress (2026-06-23): bringing AMPIPIT into ClaudeTools as a git submodule at projects/msp-tools/ampipit, matching the guru-rmm / guru-connect pattern (own repo on the ACG Gitea git.azcomputerguru.com, referenced as a submodule). Active feature: a recovery partition with the GuruRMM agent + built-in repair-script library baked in, so offline/broken Windows can phone home for repair (Claude diagnoses via RMM, directs repair scripts — no direct shell). Spike verdict GO-WITH-WORK. Design slice: C:\AMPIPIT\docs\RECOVERY_RMM_DESIGN_SLICE.md.

Why / hard constraints (Howard, 2026-06-23):

  • Do NOT lose any of the existing work — preserve full git history; back up to a verified second remote (Gitea) BEFORE removing anything; remove C:\AMPIPIT only after full verification.
  • No public GitHub. Howard is deleting the old public github.com/Howweird/AMPIPIT repo. AMPIPIT must live PRIVATE on the ACG Gitea only. Drop the github remote after Gitea is verified.
  • Follow Mike's rules for Guru projects. AMPIPIT already encodes the 3rd-party rule as ADR-047 (first-party core; non-MS binaries only via the PE tool registry / RemoteAccessProvider / RmmAdapter traits). The GuruRMM agent rides that pluggable path, never hardcoded into core.

How to apply: When working on AMPIPIT, root the session in the AMPIPIT repo dir so its own CLAUDE.md, coding/code-review/security-review agents, and the ampipit-build skill load. Use the ampipit-build skill. Sensitive-domain changes (BCD/partition/WIM/USMT/recovery partition) require the coding -> code-review -> security-review chain.