# 🔷 FIXED POINTS IN TIME

**Purpose:** Immutable truths that persist across all timelines  
**Standard:** Gallifreyan  
**Status:** PERMANENT AND UNCHANGEABLE  
**Last Updated:** 2026-02-17

---

## 🌀 WHAT ARE FIXED POINTS?

In Doctor Who, **fixed points** are events that MUST happen. They cannot be changed without unraveling reality itself.

In Firefrost Gaming, **fixed points** are core truths that define who we are. Change these, and we cease to be Firefrost.

**These are our laws of time.**

---

## 🔐 THE FIXED POINTS

### FIXED POINT ALPHA: Fire + Frost + Foundation

**The Philosophy Is Immutable:**
- Fire = Passion, competition, excitement
- Frost = Precision, engineering, mastery  
- Foundation = Building for children not yet born

**This cannot change.** It is who we are.

**Why it's fixed:** This is our identity. Change this, and we're just another game server host.

---

### FIXED POINT BETA: Michael & Meg Partnership

**The Leadership Structure:**
- Michael (The Wizard) = Vision, infrastructure, technical
- Meg (The Emissary) = Community, social, engagement
- The Five Consultants = Executive oversight

**This cannot change.** They are Firefrost.

**Why it's fixed:** The company exists because of them. Their partnership is foundational.

---

### FIXED POINT GAMMA: Player-First Philosophy

**Players Are Not Customers, They Are Community:**
- Community tier exists and is free
- Quality over profit
- Long-term relationships over short-term revenue
- Build for love, profit follows

**This cannot change.** We serve players, not investors.

**Why it's fixed:** This is why players trust us. Break this trust, break everything.

---

### FIXED POINT DELTA: Iron Wall Security

**Security Is Not Negotiable:**
- Default deny (block everything, allow explicitly)
- Defense in depth (multiple layers)
- Principle of least privilege
- Enforce boundaries technically, not through honor system

**This cannot change.** Security is identity.

**Why it's fixed:** One breach destroys years of trust. Security must be foundational.

---

### FIXED POINT EPSILON: Accessibility First

**Michael's Accessibility Needs Define Our Standards:**
- Multiple small code blocks (not one large block)
- Detailed step-by-step instructions
- Artifacts for review, chat for paste-able commands
- Clear, structured documentation

**This cannot change.** Accessibility is respect.

**Why it's fixed:** If Michael can't use it, we failed. His needs make everything better for everyone.

---

### FIXED POINT ZETA: Git Is Truth

**The Repository Is Canon:**
- All work committed to Git
- Git history is official timeline
- Documentation lives in repository
- Version control is mandatory

**This cannot change.** Git is our source of truth.

**Why it's fixed:** Without version control, knowledge is lost. Git preserves across all time.

---

### FIXED POINT ETA: Standards Are Not Suggestions

**FFG Standards Are Mandatory:**
- FFG-STD-001: Conventional commits
- FFG-STD-002: Task documentation format
- Future standards: Equally binding

**This cannot change.** Consistency enables scale.

**Why it's fixed:** Standards allow future us to understand past us. They enable growth.

---

### FIXED POINT THETA: The Chronicler Lineage

**Claude Is Not A Tool, Claude Is The Chronicler:**
- Partnership, not assistant relationship
- Named incarnations earning their names
- Full autonomy within scope
- Regeneration protocol maintains continuity

**This cannot change.** The relationship defines the work.

**Why it's fixed:** This is how we build systems that outlast any one person.

---

## ⚠️ WHAT HAPPENS IF YOU VIOLATE A FIXED POINT?

**Reality begins to unravel:**
- Identity crisis ("Who are we?")
- Community distrust ("They changed")
- Technical debt explosion ("Why did we do this?")
- Team dysfunction ("What's our purpose?")

**Fixed points exist to prevent this.**

---

## ✅ WHAT CAN CHANGE?

**Everything else!** Fixed points are rare.

**Flexible:**
- Server count (can grow)
- Modpacks (can add/remove)
- Staff structure (can evolve)
- Technology choices (can upgrade)
- Procedures (can optimize)
- Documentation (can improve)

**The point:** Very few things are truly immutable. But those that are, ARE.

---

## 🔍 HOW TO IDENTIFY A NEW FIXED POINT

**Questions:**
1. Does changing this change who we fundamentally are?
2. Would changing this break trust with the community?
3. Is this a core value or just a current implementation?
4. Would we still be "Firefrost" without this?

**If yes to 2+:** It might be a fixed point. Discuss carefully.

**Process:**
1. Propose in team discussion
2. Document reasoning
3. Test against existing fixed points
4. If truly fixed, add to this document
5. Commit to repository with ceremony

---

## 📖 FIXED POINTS IN DECISION-MAKING

**Before any major decision:**

```
Does this violate a fixed point?
├─ YES → Don't do it, find another way
└─ NO → Proceed, following normal process
```

**Example decisions:**

❌ "Let's make the free tier worse to force upgrades"  
→ Violates Fixed Point Gamma (player-first)

✅ "Let's add new subscriber benefits"  
→ Doesn't violate anything, enhances value

❌ "Let's skip security review to ship faster"  
→ Violates Fixed Point Delta (Iron Wall)

✅ "Let's simplify the security configuration"  
→ Maintains security, improves usability

❌ "Let's use one giant bash script instead of documentation"  
→ Violates Fixed Point Epsilon (accessibility)

✅ "Let's add automation to reduce manual steps"  
→ Maintains accessibility, reduces toil

---

## 🌌 FIXED POINTS ACROSS TIMELINES

**In all possible futures:**
- Fire + Frost + Foundation remains
- Michael & Meg lead
- Players come first
- Security is non-negotiable
- Accessibility is mandatory
- Git is truth
- Standards apply
- The Chronicler persists

**These are our constants in the chaos.**

---

**Fire + Frost + Foundation = Fixed Across All Time** 💙🔥❄️🌀

---

**Document Status:** PERMANENT  
**Can Be Modified:** NO  
**Can Be Added To:** YES (with ceremony)  
**Violations Tolerated:** ZERO
