Files
claudetools/projects
Mike Swanson 316c6f67e0 dataforth(datasheet): converge 8B/5B/SCM onto the DSCA template machinery (gated; WIP)
Generalized the shared renderer (datasheet-exact.js) so the per-model template path is
no longer DSCA-only — 8B/SCM5B now route through the same templates/slotMap/fround path
as DSCA. SCM7B stays on its separate parse7BRawData/legacy path (excluded). Changes
(all behind the per-model `validated` gate; non-templated families byte-unchanged, and
DSCA verified non-regressed at 54/56 + staged-92 still render):
- Load 8b5bscm-templates.json (MINED_8B5BSCM); for family 8B/SCM5B, a mined template
  takes the template path (else falls through to the legacy DATA_LINES path).
- Final-Test header is now the verbatim captured `ftHeader` (8B/5B use two schemes —
  legacy "Measured Value" vs DSCA "Measured Value*"); enrich-8b5bscm.js captured it for
  all 136 from the Hoffman originals.
- Accuracy data formatter chosen by input type detected from accHeader: frequency(Hz)/
  AC(AAC/VAC) -> formatAccuracyLineDSCA3345 (now takes inputType, not model prefix);
  standard voltage/current/temp -> legacy formatAccuracyLine.
- parseRawData step-skip generalized to any templated model (skipStepIfStatus).
- Footer 240VAC/Hi-Pot family blocks skipped for templated models (rows carry them).
- Templated SCM5B prepends "SCM" to the printed model name.
- slotmap-from-hoffman.js parameterized (DSCA_TPL) — derived 80 slotMaps for 8b5bscm.

Validation vs live Hoffman originals (validate-mined.js): 37/136 pass and are marked
validated -> 13 real 8B/SCM5B render live via the template path; 24 SCM7B already match
via the unchanged legacy path. Everything else stays null (gated, safe) — nothing
published.

Remaining long tail (well-characterized, next session): ~66 render-null need slotMaps
the Hoffman-oracle derivation couldn't get (vintage / parse); ~33 multi-nuance fails:
Final-Test sign handling on some 8B/5B measured values, accuracy-precision fround in the
legacy std formatter, "Packing Check List" vs "Check List" variants, and other per-model
footer/format quirks. Each failing model stacks several, so single fixes don't flip them.

Tools: enrich-8b5bscm.js, validate-mined.js (generalized validator), slotmap-from-hoffman.js.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-18 18:45:44 -07:00
..

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:

  1. Create a descriptive folder name (e.g., project-name/)
  2. Include conversation history if available
  3. Update this README with project details
  4. Consider creating a project-specific README
  5. Tag appropriately for context recall

  • 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