Mike Swanson
9c04c23ab0
Per the 5070 handoff (DSCA33-45-HOFFMAN-RECOVERY): the lost DSCA33/45 specs are
recoverable from Hoffman, not John. Wired the mined dsca33-45-templates.json (56
models) into the renderer:
- datasheet-exact.js: load DSCA3345_TEMPLATES; for family DSCA, the Hoffman-mined
template takes PRECEDENCE over the stale staged-extraction entry (which shadowed 25
models with accOut "?"/no accHeader). Emit the verbatim 2-line accHeader for these
families (Vin (mVAC)/Iin (AAC)/Frequency (Hz), Output (VDC)/(mADC)). Per-model
`validated` GATE: a DSCA33/45 model renders only after byte-matching its Hoffman
original; until then it returns null (skipped) so an unverified render can never
overwrite a pristine live original. DSCA_VALIDATE_MODE env opens the gate for the
validation harness only. Exposed rendersWithoutSpecs().
- render-datasheet.js: allow a null-specs render for DSCA33/45 (their spec files were
lost; template-driven) instead of bailing on missing specs.
- derive-dsca-slotmaps.js: DSCA_TPL env to target the 3345 templates; derived 43 slot
maps into them (22 models need none, 8 DSCA33 still below threshold).
- validate-dsca3345.js (new): renders each model's _srcSerial, fetches the live
Hoffman original (GET TestReportDataFiles/{serial}, deployed uploader token — no
vault needed), content-normalized compare; --apply marks validated.
STATUS: gate is CLOSED — 0 models validated, all DSCA33/45 still render null, nothing
published, no risk. Final-Test block + accuracy headers now byte-match the Hoffman
originals for all 56 models; the remaining blocker is accuracy-DATA numeric quirks that
must match to pass the gate:
- DSCA33 calc column stored in A but displayed in mADC (x1000); measured stored in
mA (not scaled) — an original-software unit quirk.
- sign conventions differ per layout (DSCA33 stim/calc/meas unsigned, error signed;
DSCA45 stim unsigned, calc/meas/error signed).
- DSCA45 frequency-input stim formatting.
These need per-layout reverse-engineering against the originals (the validation harness
is the oracle). 8 DSCA33 models (DSCA33-02/03/03A/04/04A/05/05A/1642) also lack a slot
map (below threshold). DSCA33-1948 + DSCA45-1746 (24 units) have no Hoffman original.
Cleanups: deleted superseded memory project_dsca33_45_spec_gap; struck the obsolete
"ask John" TODO 2 from the handoff note.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ClaudeTools Active Projects
Directory: D:\ClaudeTools\projects\
Purpose: Active development projects and related conversation archives
Last Updated: 2026-01-17
Overview
This directory contains active projects being developed or maintained as part of the ClaudeTools ecosystem. Unlike the imported-conversations/ directory which serves as an archive, projects here are actively worked on and may include both source code and conversation history.
Current Projects
MSP Tools (94 files, 20.1 MB)
Moved From: D:\ClaudeTools\imported-conversations\msp-tools/
Move Date: 2026-01-17
Status: Active development
Managed Service Provider (MSP) tooling and infrastructure projects, including conversation history and development artifacts.
Structure
msp-tools/
├── guru-rmm/ # 54 files, 14 MB
│ └── [JSONL conversation files] # RMM system development history
└── guru-connect/ # 40 files, 6.1 MB
└── [JSONL conversation files] # MSP integration development history
guru-rmm (54 files, 14 MB)
Description: Remote Monitoring and Management (RMM) system development conversations
Source: C:\Users\MikeSwanson\.claude\projects\C--Users-MikeSwanson-claude-projects-gururmm-guru-rmm
Key Topics:
- RMM system architecture
- Monitoring solutions
- Agent deployment
- Infrastructure management
- MSP automation
Project Type: MSP Infrastructure
guru-connect (40 files, 6.1 MB)
Description: MSP connectivity and integration tooling conversations
Source: C:\Users\MikeSwanson\.claude\projects\C--Users-MikeSwanson-claude-projects-guru-connect
Key Topics:
- Integration patterns
- API connectivity
- Service orchestration
- Client management
- Cross-platform integration
Project Type: MSP Integration
File Format
All conversation files are in JSONL (JSON Lines) format:
- Extension:
.jsonl - Format: Each line is a valid JSON object
- Content: Individual conversation messages from Claude
- Encoding: UTF-8
- Can be processed line-by-line for analysis
Usage
Accessing Project Files
# List all projects
ls -lh D:\ClaudeTools\projects\
# Browse MSP tools conversations
ls -lh D:\ClaudeTools\projects\msp-tools\guru-rmm\
# Count conversation files
find D:\ClaudeTools\projects\ -name "*.jsonl" | wc -l
# Search for specific topics
grep -r "FastAPI" D:\ClaudeTools\projects\
Integration with ClaudeTools
These conversations can be:
- Analyzed and indexed into context recall system
- Used to extract reusable code snippets
- Mined for technical decisions and patterns
- Converted into knowledge base entries
- Referenced for similar future projects
Adding New Projects
When adding new active projects to this directory:
- Create a descriptive folder name (e.g.,
project-name/) - Include conversation history if available
- Update this README with project details
- Consider creating a project-specific README
- Tag appropriately for context recall
Related Documentation
- imported-conversations/INDEX.md - Archive of all imported conversations
- imported-conversations/IMPORT_MANIFEST.json - Detailed import metadata
- .claude/CLAUDE.md - Main ClaudeTools project documentation
- SESSION_STATE.md - Current project state and development history
Project Organization
Active Projects (this directory):
- Currently under development
- May include both code and conversation history
- Subject to frequent updates
- Integrated with ClaudeTools development
Archived Conversations (imported-conversations/):
- Historical reference only
- Read-only archive
- Organized by project type
- Preserved for knowledge extraction
Future Projects
This directory will grow as new projects are added. Potential additions:
- guru-backup - Backup and recovery tooling
- guru-dashboard - MSP management dashboard
- integration-tools - Third-party integration utilities
- automation-scripts - MSP automation workflows
Statistics
Current Totals:
- Projects: 1 (msp-tools)
- Conversation Files: 94 JSONL files
- Total Size: 20.1 MB
- Subcategories: 2 (guru-rmm, guru-connect)
Breakdown:
- guru-rmm: 54 files (57.4%), 14 MB (69.7%)
- guru-connect: 40 files (42.6%), 6.1 MB (30.3%)
Notes
- This directory was created on 2026-01-17
- First project (msp-tools) moved from imported-conversations archive
- All conversation files preserved with original timestamps
- Original source paths documented in IMPORT_MANIFEST.json
Maintained By: ClaudeTools Project
Location: D:\ClaudeTools\projects
Documentation Status: Active