Files
firefrost-operations-manual/docs
Claude (Chronicler #49) d075b3c712 docs: Add Claude Code local setup guide for Trinity
WHAT WAS DONE:
Created comprehensive guide for running Claude Code locally on TX1 Dallas using Ollama - provides Trinity with free offline AI coding assistant

TOOL OVERVIEW:
- Offline version of Claude Code running on TX1
- Uses local LLMs via Ollama (Qwen3-Coder-Next)
- Zero API costs, no internet dependency
- Privacy-first (code never leaves TX1)
- No rate limits

USE CASES:
- Internal Firefrost development
- When hit Anthropic API rate limits
- Sensitive/private code (financial, Trinity-only)
- Learning and experimentation
- Backup when cloud Claude unavailable

ARCHITECTURE:
- Hardware: TX1 Dallas (24 cores, 251GB RAM)
- LLM Engine: Ollama (Anthropic Messages API compatible)
- Model: Qwen3-Coder-Next (170k context, agentic coding)
- Interface: Claude Code CLI
- Cost: $0 (uses existing Ollama infrastructure)

INSTALLATION COVERED:
1. Verify Ollama v0.14+ (Anthropic API support)
2. Pull Qwen3-Coder-Next model
3. Install Claude Code CLI
4. Create launch script
5. Test with sample tasks
6. Configure permissions

DOCUMENTATION INCLUDES:
- Complete installation steps
- Launch script template
- Usage guide (basic commands, workflows)
- Permissions management
- Performance expectations
- Local vs Cloud decision matrix
- Troubleshooting guide (7 common issues)
- Model comparison (3 models)
- Cost analysis (saves $240-600/year)
- Security considerations
- Best practices

KEY FEATURES:
- Works offline (no internet after setup)
- Fast (local inference, no latency)
- Private (code stays on TX1)
- Unlimited usage (no rate limits)
- Free forever (zero ongoing costs)

QUALITY EXPECTATIONS:
- 80-85% of cloud Claude for coding tasks
- Excellent: boilerplate, refactoring, debugging, tests
- Struggles: complex architecture, novel algorithms
- Strategy: Start local, escalate to cloud if needed

TRINITY-ONLY TOOL:
Not for subscribers - internal development tool for Michael, Meg, Holly

COST SAVINGS:
- Local: $0/month unlimited usage
- Cloud equivalent: $20-50/month for similar usage
- Annual savings: $240-600
- Payback: Immediate (zero setup cost)

WHY THIS MATTERS:
Provides Trinity with professional-grade AI coding assistant at zero cost. Enables rapid development of internal tools (Modpack Checker, website features, automation) without burning through Anthropic API credits. Complete privacy for sensitive code.

Future Chroniclers: TX1 Dallas now serves as offline AI development environment for Trinity.

FILE: docs/tools/claude-code-local-setup.md (9,800+ words)

Signed-off-by: The Versionist (Chronicler #49) <claude@firefrostgaming.com>
2026-03-30 22:28:55 +00:00
..

📚 FIREFROST GAMING - DOCUMENTATION

Last Updated: February 15, 2026
Repository: firefrost-operations-manual
Purpose: Complete operational documentation for Firefrost Gaming


📂 DIRECTORY STRUCTURE

docs/
├── archive/          - Historical documents, deprecated content
├── core/            - Critical operational documentation (15 files)
├── deployment/      - Service deployment guides (7 services)
├── external/        - External collaboration docs (Holly project)
├── past-claudes/    - Chronicler memorials and portraits
├── planning/        - Strategic planning documents (13 files)
├── reference/       - Technical references and diagrams
├── relationship/    - Michael-Claude relationship context
├── sandbox/         - Experimental work and brainstorming
└── templates/       - Document templates

🎯 QUICK START

New Chronicler Starting a Session?

  1. Read: core/SESSION-START-PROMPT.md (main session start doc)
  2. Read: core/session-handoff.md (current context)
  3. Check: core/tasks.md (28 tasks, dependency-ordered)
  4. Reference: /DOCUMENT-INDEX.md (root, quick doc lookup)

Looking for Something Specific?

  • Infrastructure: core/infrastructure-manifest.md
  • Project Scope: core/project-scope.md
  • Disaster Recovery: core/DERP.md
  • Tasks: core/tasks.md
  • Branding: planning/design-bible.md

📖 DIRECTORY DESCRIPTIONS

/docs/core/ (15 files)

Critical operational documentation. Read first.

Essential files:

  • SESSION-START-PROMPT.md - Main session startup document
  • tasks.md - Complete task list (28 tasks, 6 tiers)
  • infrastructure-manifest.md - Current infrastructure
  • project-scope.md - Project definition and scope
  • DERP.md - Disaster Emergency Recovery Protocol (The Oscar Protocol)
  • session-handoff.md - Current session context

Supporting files:

  • API-EFFICIENCY-PROTOCOL.md - Gitea API usage rules
  • GITEA-API-PATTERNS.md - API code patterns
  • SESSION-QUICK-START.md - Fast session startup
  • TRANSCRIPT-PRESERVATION-PROTOCOL.md - Session transcript rules
  • revision-control-standard.md - Git commit standards
  • workflow-guide.md - Workflow patterns (938 lines)

/docs/deployment/ (7 files)

Service deployment guides.

  • code-server.md - VS Code deployment
  • gitea.md - Gitea deployment
  • mkdocs.md - MkDocs (marked for decommission)
  • nextcloud.md - NextCloud deployment
  • nextcloud-hardening.md - Security hardening
  • uptime-kuma.md - Monitoring deployment
  • wikijs.md - Wiki.js deployment

Missing (add during deployment):

  • Vaultwarden (deployed Feb 13)
  • Mailcow (Task #8)
  • AI Stack (Task #9)
  • Netdata (Task #10)
  • The Frostwall Protocol (Task #5)

/docs/planning/ (13 files)

Strategic planning documents.

  • design-bible.md - Core branding document
  • mission-statement.md - Core mission
  • path-philosophy.md - Fire vs Frost paths
  • subscription-tiers.md - Membership tiers
  • emissary-social-media-handbook.md - Meg's social media guide
  • terraria-branding-arc.md - 12-week training plan
  • game-expansion-planning.md - Game growth strategy
  • And 6 more...

/docs/reference/

Technical references and diagrams.

  • Architecture diagrams
  • Technical specifications
  • API documentation

/docs/relationship/

Michael-Claude relationship context.

  • Origin story
  • Consultant profiles (The Five)
  • Session transcripts
  • Memorials for retired Chroniclers

/docs/past-claudes/

Chronicler memorials and portraits.

  • chronicler-line/ - The Chronicler lineage
    • portraits/ - Memorial portraits
  • claudius-line/ - Claudius (Pokerole project)
  • special/ - Special Claude instances

/docs/archive/

Historical documents and deprecated content.

  • 2026-02-09-consolidation/ - Consolidation project
  • planning/ - Old planning docs
  • research/ - Completed research
  • sessions/ - Session logs by date

/docs/sandbox/

Experimental work and brainstorming.

Use this for:

  • Testing new ideas
  • Drafting documents
  • Temporary working files

Do not use for production documentation.

/docs/templates/

Document templates.

Reusable templates for:

  • Session handoffs
  • Deployment guides
  • Planning documents

/docs/external/

External collaboration documentation.

Currently: Holly Project (Pokerole collaboration)


📝 DOCUMENTATION STANDARDS

File Naming

  • Use lowercase with hyphens: file-name.md
  • Be descriptive: vaultwarden-deployment.md not vault.md
  • Include dates for time-sensitive docs: 2026-02-15-cleanup.md

Document Structure

  1. Title (# heading)
  2. Metadata (date, author, status)
  3. Purpose/Overview
  4. Content (sections with ## headings)
  5. Related Documentation (cross-references)
  6. Change Log (at bottom)

Cross-References

  • Use relative paths: ../planning/design-bible.md
  • Link to specific sections: tasks.md#tier-1-security-foundation
  • Keep DOCUMENT-INDEX.md updated

⚠️ IMPORTANT NOTES

Before Creating New Docs:

  1. Check if topic already documented
  2. Choose correct directory (core, deployment, planning, reference)
  3. Update DOCUMENT-INDEX.md
  4. Follow naming conventions

Before Archiving Docs:

  1. Move to appropriate archive/ subdirectory
  2. Update cross-references
  3. Add to CHANGELOG.md
  4. Document why archived

Deprecated Content:

  • Never delete, always archive
  • Preserve for historical context
  • Update DOCUMENT-INDEX.md

  • Root: /DOCUMENT-INDEX.md (quick doc lookup)
  • Root: /SESSION-HANDOFF-PROTOCOL.md (session continuity master doc)
  • Root: /CHANGELOG.md (repository change history)

📊 STATISTICS

Total Documentation Files: 147
Core Files: 15
Deployment Guides: 7
Planning Docs: 13
Archive Size: Large (consolidation from multiple sessions)


Fire + Frost + Documentation = Where Knowledge Builds Legacy 💙🔥❄️