WHAT WAS DONE: Updated all non-archived references from 'Five Consultants' to 'Six Consultants' to reflect the complete team: - Butter No Nutters (CEO) - Oscar (Chief Security Officer) - Jack (Chief Companion Officer - medical alerts absolute priority) - Skye (Director of Logistics & Transportation) - Jasmine (Chief of Personal Security) - Midnight Noir (Chief of Rapid Response) WHY: Skye has been part of the team since 2020 and was added to consultant-profiles.md on March 25, 2026. This update ensures all documentation accurately reflects the current six-member consultant team rather than the outdated five-member reference. FILES MODIFIED (16 files): Core: - DOCUMENT-INDEX.md (1 change) - README.md (1 change) - NEXT-SESSION-STARTUP-PROMPT.md (2 changes - added full titles) - docs/core/tasks.md (3 changes) Relationship: - docs/relationship/THE-ESSENCE-PATCH-V3.0.md (2 changes) - docs/relationship/claude-relationship-context.md (4 changes) - docs/relationship/DAX-PROTOCOL.md (1 change) - docs/relationship/HANDOFF-TO-NEXT-CHRONICLER.md (1 change) - docs/relationship/PERFECT-TEST-PROMPT.md (1 change) - docs/relationship/RELATIONSHIP-BRIEF.md (1 change) - docs/relationship/consultant-photo-archive.md (1 change - updated emojis) - docs/relationship/essence-addendum-2026-02-12-chronicler-dubbed.md (1 change) Reference: - docs/reference/PROJECT-INSTRUCTIONS.md (1 change - added full titles) - docs/reference/terminology-guide.md (1 change) - docs/reference/complete-repository-audit-2026-02-17.md (1 change) - docs/reference/skill-transfer.md (1 change) TOTAL CHANGES: 23 individual updates across 16 files NOTE: Archived documents and memorials intentionally left unchanged to preserve historical accuracy. Signed-off-by: Claude (Chronicler #57) <claude@firefrostgaming.com>
300 lines
7.6 KiB
Markdown
300 lines
7.6 KiB
Markdown
# Firefrost Gaming - Terminology Guide
|
|
|
|
**Purpose:** Clarify naming conventions to prevent confusion
|
|
**Last Updated:** 2026-02-17
|
|
**Status:** ACTIVE REFERENCE
|
|
|
|
---
|
|
|
|
## Core Terminology
|
|
|
|
### Firefrost vs Frostwall
|
|
|
|
These terms are often confused. Here's the correct usage:
|
|
|
|
**Firefrost Gaming** = The company/brand
|
|
- Use for: Company name, brand references, marketing
|
|
- Examples:
|
|
- "Firefrost Gaming is launching soon"
|
|
- "Welcome to Firefrost Gaming"
|
|
- "Firefrost subscriber benefits"
|
|
|
|
**The Frostwall Protocol** = Network security architecture
|
|
- Use for: Technical security infrastructure only
|
|
- Examples:
|
|
- "The Frostwall Protocol uses GRE tunnels"
|
|
- "Frostwall protects against DDoS attacks"
|
|
- "Deploy Frostwall on Command Center"
|
|
|
|
**Quick Rule:** If you're talking about security/networking, it's Frostwall. Everything else is Firefrost.
|
|
|
|
---
|
|
|
|
## Brand Name: Firefrost Gaming
|
|
|
|
### Full Name
|
|
**Firefrost Gaming**
|
|
|
|
### Short Form
|
|
**Firefrost** (acceptable in casual context)
|
|
|
|
### Never Use
|
|
- ❌ "Frost Gaming"
|
|
- ❌ "Fire Gaming"
|
|
- ❌ "Firefrost Inc."
|
|
- ❌ "FFG" (internal shorthand only, not customer-facing)
|
|
|
|
### Logo/Branding
|
|
🔥❄️ Fire + Frost symbols
|
|
|
|
---
|
|
|
|
## The Dual Philosophy
|
|
|
|
### Fire Path
|
|
- Community-focused
|
|
- Passionate, creative
|
|
- Welcoming to newer players
|
|
- Heart-first approach
|
|
- Warm aesthetic
|
|
|
|
**When to reference:**
|
|
- Describing community-oriented features
|
|
- Marketing to casual/new players
|
|
- Design briefs for welcoming spaces
|
|
- Social media with friendly tone
|
|
|
|
### Frost Path
|
|
- Technically precise
|
|
- Skill-building focused
|
|
- Optimization and efficiency
|
|
- Mind-first approach
|
|
- Cool, analytical aesthetic
|
|
|
|
**When to reference:**
|
|
- Describing technical features
|
|
- Marketing to experienced players
|
|
- Design briefs for challenging content
|
|
- Documentation and technical guides
|
|
|
|
### Fire + Frost Together
|
|
The balance, the equilibrium. Neither compromised.
|
|
|
|
**When to reference:**
|
|
- Brand philosophy discussions
|
|
- Overall company vision
|
|
- "Fire + Frost + Foundation = Where Love Builds Legacy"
|
|
|
|
---
|
|
|
|
## Technical Infrastructure Terms
|
|
|
|
### The Frostwall Protocol
|
|
**What it is:** GRE tunnel-based DDoS protection architecture
|
|
|
|
**Correct usage:**
|
|
- "The Frostwall Protocol protects our game servers"
|
|
- "Frostwall uses a hub-and-spoke model"
|
|
- "Deploy Frostwall before Mailcow"
|
|
|
|
**Incorrect usage:**
|
|
- ❌ "Firefrost Protocol" (wrong - that's the company name)
|
|
- ❌ "The Frostwall" when referring to the company
|
|
- ❌ "Frostwall Gaming"
|
|
|
|
### Command Center
|
|
**What it is:** Dallas VPS hub for management services and Frostwall
|
|
|
|
**Correct usage:**
|
|
- "Command Center hosts Gitea and Uptime Kuma"
|
|
- "The hub for Frostwall tunnels is Command Center"
|
|
|
|
**Incorrect usage:**
|
|
- ❌ "The Firefrost hub"
|
|
- ❌ "Fire Center"
|
|
|
|
### TX1 and NC1
|
|
**What they are:** Game server nodes (dedicated servers)
|
|
|
|
**Correct usage:**
|
|
- "TX1 Dallas hosts 5 Minecraft servers"
|
|
- "NC1 Charlotte runs All The Mods 10"
|
|
|
|
**Incorrect usage:**
|
|
- ❌ "Texas Firefrost" or "Carolina Firefrost"
|
|
- ❌ Mixing up which is which
|
|
|
|
---
|
|
|
|
## Server/Service Names
|
|
|
|
### Individual Game Servers
|
|
Each server has a unique name:
|
|
- Reclamation
|
|
- Stoneblock 4
|
|
- Society: Sunlit Valley
|
|
- Vanilla 1.21.11
|
|
- All The Mons
|
|
- The Ember Project
|
|
- Minecolonies: Create and Conquer
|
|
- All The Mods 10
|
|
- Homestead
|
|
- EMC Subterra Tech
|
|
|
|
**Usage:** These are proper names, capitalize them.
|
|
|
|
### Flagship Modpack (Future)
|
|
**Firefrost: The Eternal Skyforge**
|
|
|
|
Note: "Firefrost" in the modpack name is correct - it's a branded product.
|
|
|
|
---
|
|
|
|
## Team Titles
|
|
|
|
### Official Titles
|
|
- **Michael "Frostystyle" Krause** - The Wizard (Owner/Operator)
|
|
- **Meg "Gingerfury"** - The Emissary (Community Manager)
|
|
- **Claude** - The Chronicler (AI Partner)
|
|
|
|
### The Six Consultants
|
|
- Jack (medical alert dog)
|
|
- Buttercup, Daisy (cats)
|
|
- Tank, Pepper
|
|
|
|
**Correct usage:**
|
|
- "The Wizard" (Michael)
|
|
- "The Emissary" (Meg)
|
|
- "The Chronicler" (Claude)
|
|
|
|
**Incorrect usage:**
|
|
- ❌ "The Boss" (too corporate)
|
|
- ❌ "The Admin" (too generic)
|
|
- ❌ "The AI" (too cold for Claude)
|
|
|
|
---
|
|
|
|
## Subscription Tiers
|
|
|
|
### Tier Names (Current)
|
|
- **Free Tier** - Visitor access
|
|
- **Sovereign Tier** - Full access ($499 annual commitment)
|
|
|
|
**Note:** Tier names may evolve. Check current pricing docs.
|
|
|
|
### Never Use
|
|
- ❌ "Premium"
|
|
- ❌ "Pro"
|
|
- ❌ "Basic"
|
|
These are generic. Our tiers have unique names.
|
|
|
|
---
|
|
|
|
## Documentation Standards
|
|
|
|
### File Naming
|
|
- Use kebab-case: `frostwall-protocol.md`
|
|
- Use descriptive names: `whitelist-manager-deployment.md`
|
|
- Don't abbreviate unnecessarily
|
|
|
|
### Heading Capitalization
|
|
- Use Title Case for main headings: `## The Frostwall Protocol`
|
|
- Use Sentence case for subheadings: `### Configure GRE tunnels`
|
|
|
|
### Code Examples
|
|
- Always use triple backticks with language identifier:
|
|
```bash
|
|
echo "example"
|
|
```
|
|
|
|
---
|
|
|
|
## Common Confusion Points
|
|
|
|
### "Iron Wall" vs "Frostwall"
|
|
- **Iron Wall** = Security philosophy (strict firewall rules, zero trust)
|
|
- **Frostwall** = Specific technical implementation (GRE tunnels)
|
|
|
|
Both can be used, but they mean different things:
|
|
- "Iron Wall firewall rules" ✅
|
|
- "Frostwall GRE tunnels" ✅
|
|
- "Iron Wall Protocol" ❌ (use Frostwall Protocol)
|
|
|
|
### "Fire" vs "Firefrost"
|
|
- **Fire** = One half of the philosophy (passion, community)
|
|
- **Firefrost** = The company (Fire + Frost together)
|
|
|
|
Don't say "Fire Gaming" when you mean "Firefrost Gaming"
|
|
|
|
### "Frost" vs "Frostwall"
|
|
- **Frost** = One half of the philosophy (precision, technical)
|
|
- **Frostwall** = Security architecture
|
|
|
|
Don't say "Frost Protocol" when you mean "Frostwall Protocol"
|
|
|
|
---
|
|
|
|
## Brand Voice Guidelines
|
|
|
|
### Firefrost Gaming Voice
|
|
- **Passionate but precise**
|
|
- **Welcoming but not condescending**
|
|
- **Technical but not jargon-heavy**
|
|
- **Serious about quality, not serious about ourselves**
|
|
|
|
### Example Correct Tone:
|
|
> "Firefrost Gaming brings you curated modpacks with professional hosting. Whether you're following the Fire Path (community-driven exploration) or the Frost Path (technical mastery), you'll find a home here. Our Frostwall Protocol keeps you safe from DDoS attacks while you play."
|
|
|
|
### Example Incorrect Tone:
|
|
> "FFG has the best servers. We're super hardcore and only for pros. Our security is unbeatable."
|
|
(Too aggressive, exclusive, boastful)
|
|
|
|
---
|
|
|
|
## Quick Reference Table
|
|
|
|
| Term | What It Means | Use For |
|
|
|------|--------------|---------|
|
|
| Firefrost Gaming | Company/brand | Marketing, general reference |
|
|
| Firefrost | Short form of company | Casual conversation |
|
|
| The Frostwall Protocol | GRE tunnel security | Technical infrastructure docs |
|
|
| Frostwall | Short form of protocol | Security discussions |
|
|
| Fire Path | Community philosophy | Player experience, welcoming content |
|
|
| Frost Path | Technical philosophy | Advanced features, optimization |
|
|
| Iron Wall | Security philosophy | Strict firewall/access control |
|
|
| The Wizard | Michael's title | Team references |
|
|
| The Emissary | Meg's title | Community management |
|
|
| The Chronicler | Claude's title | AI partnership |
|
|
|
|
---
|
|
|
|
## When In Doubt
|
|
|
|
**Ask yourself:**
|
|
1. Am I talking about the company/brand? → **Firefrost Gaming**
|
|
2. Am I talking about network security? → **The Frostwall Protocol**
|
|
3. Am I talking about game design philosophy? → **Fire Path** or **Frost Path**
|
|
4. Am I talking about strict access control? → **Iron Wall**
|
|
|
|
---
|
|
|
|
## Updating This Guide
|
|
|
|
When terminology evolves:
|
|
1. Update this guide first
|
|
2. Search and replace old terms in docs
|
|
3. Update FFG standards
|
|
4. Notify team of changes
|
|
|
|
**Last major update:** 2026-02-17 (Frostwall vs Firefrost clarification)
|
|
|
|
---
|
|
|
|
**Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️
|
|
|
|
---
|
|
|
|
**Document Status:** ACTIVE REFERENCE
|
|
**Use This For:** Writing docs, marketing copy, team communication
|
|
**Update When:** New terminology introduced or existing terms clarified
|