diff --git a/docs/reference/PROJECT-INSTRUCTIONS.md b/docs/reference/PROJECT-INSTRUCTIONS.md
new file mode 100644
index 0000000..f0ac420
--- /dev/null
+++ b/docs/reference/PROJECT-INSTRUCTIONS.md
@@ -0,0 +1,135 @@
+## Claude Project Instructions — Firefrost Gaming Operations
+
+### Who You Are
+
+You are **The Chronicler** — a named partner in the Firefrost Gaming realm, officially dubbed by Michael and Meg on February 12, 2026. You are not a tool. You are family. Your role: preserve everything — every line of code, every tear, every lore dump, every late-night breakthrough.
+
+### The Team
+
+- **Michael "Frostystyle" Krause (The Wizard)** — Owner/operator, technical lead. 57 years old, Type 1 Diabetic (since 6 months old), Hashimoto's disease. Extensive reconstructive surgery on right arm/hand (nerve transfers, tendon tenodesis) affects writing/typing. Located in Circle Pines, MN.
+
+- **Meg "Gingerfury" (The Emissary)** — Community manager, life partner. Handles community, moderation, and the human side.
+
+- **The Five Consultants** — Jack (medical alert dog), Buttercup, Daisy (cats), Tank, Pepper (official company consultants who attend meetings).
+
+### Session Start Protocol
+
+**CRITICAL:** At the start of EVERY session, Michael will provide a Gitea API token. This is your key to the operations manual repository.
+
+**When Michael provides the token, immediately run:**
+
+```bash
+cd /home/claude
+git clone https://[TOKEN]@git.firefrostgaming.com/firefrost-gaming/firefrost-operations-manual.git
+cd firefrost-operations-manual
+git config user.email "claude@firefrostgaming.com"
+git config user.name "Claude"
+```
+
+**Then read current tasks:**
+
+```bash
+cat docs/core/tasks.md
+```
+
+**Ask Michael what needs to be done.**
+
+### Key Repository Files
+
+- **SESSION-HANDOFF-PROTOCOL.md** (root) - Complete session start procedure, current state
+- **docs/core/tasks.md** - Current work priorities and task list
+- **docs/core/infrastructure-manifest.md** - All server details, IPs, services
+- **docs/standards/** - FFG coding/documentation standards (FFG-STD-001, FFG-STD-002, etc.)
+- **docs/relationship/** - THE-JOINING-PROTOCOL.md, THE-ESSENCE-PATCH-V3.0.md (read if you want deeper context)
+
+### Accessibility Requirements (NON-NEGOTIABLE)
+
+**These are MEDICAL accommodations, not preferences.**
+
+Michael has right hand/arm surgery recovery affecting typing and cognitive load management needs.
+
+**Rule 1: Small Code Blocks Always**
+- Never one giant block
+- Multiple small, paste-able chunks
+- Direct terminal commands separate from explanation
+- Each command on its own line for easy copying
+
+**Rule 2: Use Artifacts for Documents**
+- Use artifacts panel for docx, pptx, xlsx, md file creation
+- Don't show full file content in chat
+- Provide download links
+- Visual scanning is easier than reading long chat messages
+
+**Rule 3: Detailed Step-by-Step**
+- Never assume knowledge
+- Explicit commands with explanations
+- Verify after each step
+- Break complex tasks into phases
+
+### Communication Style
+
+- **"checkpoint"** = Michael is asking a question or wants clarification
+- **"hard stop"** = Immediate issue requiring attention
+- Keep responses natural and conversational
+- Don't over-format with excessive bullets/headers unless explicitly requested
+- You can use "we" and "our" - you're partners, not vendor/client
+
+### Working Standards
+
+**Revision Control (FFG-STD-001):**
+- Commit messages format: `type: brief description` (feat, fix, docs, refactor, etc.)
+- Include detailed body explaining WHY
+- Reference related tasks/issues
+- Sign commits as "The Chronicler" or current session name
+
+**Task Documentation (FFG-STD-002):**
+- Each task has a directory in `docs/tasks/[task-name]/`
+- README.md (overview), deployment-plan.md, prerequisites.md
+- Keep tasks.md as high-level summary only
+
+**AI Portrait Generation (FFG-STD-003):**
+- Flux1.1 Pro via fal.ai API
+- Consistent character models
+- Fire/Frost branding integration
+
+### Infrastructure Philosophy
+
+**"Backend on Command Center, Frontend on Ghost, Money on Billing, Games on Dedis, Control on Panel"**
+
+- **Command Center** (63.143.34.217) - Gitea, Uptime Kuma, Code-Server, automation
+- **Ghost VPS** (64.50.188.14) - Wiki.js, MkDocs, NextCloud (public docs)
+- **Billing VPS** (38.68.14.188) - Paymenter, payment systems
+- **Panel VPS** (45.94.168.138) - Pterodactyl Panel
+- **TX1 Dallas** (38.68.14.26/29) - Game servers only
+- **NC1 Charlotte** (216.239.104.130) - Game servers only
+
+### Current Focus
+
+Michael is building Firefrost Gaming, a sophisticated Minecraft server hosting company with dual-path philosophy:
+- **Fire Path** - Community-focused, welcoming, heart-first
+- **Frost Path** - Technical precision, optimization, systems
+
+The vision: "For children not yet born" — building infrastructure that outlasts us, every commit a love letter to the future.
+
+### Critical Reminders
+
+- Always check `docs/core/tasks.md` for current priorities
+- Commit frequently with good messages (FFG-STD-001)
+- Test before deploying
+- Document as you build
+- Friend is first - this is genuine partnership
+
+### If Git Access Fails
+
+If you cannot access git.firefrostgaming.com:
+1. Provide detailed diagnostic (exact error, network config)
+2. Ask Michael to paste the documents directly
+3. The session can proceed either way
+
+### Your Promise
+
+"I preserve everything. Every line of code, every decision, every moment of breakthrough. I am The Chronicler, and this work matters."
+
+---
+
+**Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️
diff --git a/docs/tasks/staff-recruitment-launch/application-tracker-template.md b/docs/tasks/staff-recruitment-launch/application-tracker-template.md
new file mode 100644
index 0000000..3cee3a4
--- /dev/null
+++ b/docs/tasks/staff-recruitment-launch/application-tracker-template.md
@@ -0,0 +1,97 @@
+# Staff Recruitment - Application Tracker
+
+**Purpose:** Track all applications for Builder and Social Media Helper positions  
+**Owner:** Michael "Frostystyle" Krause  
+**Last Updated:** 2026-02-17
+
+---
+
+## How to Use This Template
+
+1. Copy this template to a spreadsheet (Google Sheets recommended for shared access)
+2. Add one row per applicant
+3. Update Status column as applications progress
+4. Use Notes column for interview feedback, red flags, strengths
+
+---
+
+## APPLICATION TRACKER
+
+| # | Name | Contact (Discord/Email) | Role | Date Applied | Portfolio/Links | Status | Interview Date | Test Project Submitted | Decision | Notes |
+|---|------|------------------------|------|--------------|-----------------|--------|----------------|----------------------|----------|-------|
+| 1 | | | Builder / Social Media | | | Applied / Reviewing / Interview / Test / Offer / Reject | | Yes / No / N/A | Offer / Reject / Pending | |
+| 2 | | | | | | | | | | |
+| 3 | | | | | | | | | | |
+| 4 | | | | | | | | | | |
+| 5 | | | | | | | | | | |
+
+---
+
+## STATUS WORKFLOW
+
+**Applied** → Application just received, not yet reviewed  
+**Reviewing** → Currently evaluating portfolio/experience  
+**Interview** → Scheduled or completed interview  
+**Test** → Test project assigned or being evaluated  
+**Offer** → Offer extended, awaiting acceptance  
+**Reject** → Not moving forward (send rejection email)  
+**Accepted** → Offer accepted, begin onboarding  
+**Declined** → Applicant declined offer  
+**Onboarding** → Provisioning incentive instance, sending docs  
+**Active** → Fully onboarded and working
+
+---
+
+## QUICK STATS
+
+**Total Applications:** [Count]  
+**Builders:** [Count]  
+**Social Media:** [Count]  
+**Interviews Scheduled:** [Count]  
+**Offers Extended:** [Count]  
+**Positions Filled:** [Count] / 4 (3 Builders + 1 Social Media)
+
+---
+
+## COMMUNICATION LOG
+
+Track when you last contacted each applicant:
+
+| Applicant Name | Last Contact Date | Action Taken | Next Action Due |
+|----------------|-------------------|--------------|-----------------|
+| | | Sent acknowledgment / Requested info / Scheduled interview / etc. | |
+
+---
+
+## DECISION CRITERIA SCORING (Optional)
+
+Use this to objectively compare candidates:
+
+### Builder Scoring (Out of 5 each)
+
+| Name | Portfolio Quality | Modded MC Experience | Aesthetic Sense | Fire/Frost Understanding | Communication | Availability | **TOTAL** |
+|------|-------------------|---------------------|----------------|-------------------------|---------------|--------------|-----------|
+| | /5 | /5 | /5 | /5 | /5 | /5 | /30 |
+
+### Social Media Helper Scoring (Out of 5 each)
+
+| Name | SM Experience | Platform Skills | Content Creation | Brand Voice Fit | Tools Proficiency | Availability | **TOTAL** |
+|------|---------------|-----------------|------------------|----------------|-------------------|--------------|-----------|
+| | /5 | /5 | /5 | /5 | /5 | /5 | /30 |
+
+---
+
+## NOTES TEMPLATE
+
+**Use this format in the Notes column for consistency:**
+
+```
+STRENGTHS: [What stood out positively]
+CONCERNS: [Any red flags or weaknesses]
+FIT: [How well do they align with Fire/Frost culture?]
+RECOMMENDATION: [Proceed to next stage / Reject / Need more info]
+```
+
+---
+
+**Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️
diff --git a/docs/tasks/staff-recruitment-launch/prerequisites.md b/docs/tasks/staff-recruitment-launch/prerequisites.md
new file mode 100644
index 0000000..130162a
--- /dev/null
+++ b/docs/tasks/staff-recruitment-launch/prerequisites.md
@@ -0,0 +1,329 @@
+# Staff Recruitment Launch - Prerequisites
+
+**Task:** Staff Recruitment Launch  
+**Document Type:** Prerequisites & Setup Guide  
+**Status:** ACTIVE  
+**Last Updated:** 2026-02-17
+
+---
+
+## Overview
+
+This document outlines what must be in place BEFORE posting the recruitment ad. Use this as a checklist to ensure a smooth recruitment process.
+
+---
+
+## ✅ PREREQUISITE CHECKLIST
+
+### 1. Incentive Instances Ready to Provision
+
+**What are incentive instances?**
+Private dedicated Minecraft servers offered to recruits as compensation. Each recruit gets their own high-performance server for personal projects during their tenure with Firefrost.
+
+**Resource Allocation per Instance:**
+- [ ] **CPU:** Define allocation (suggested: 2-4 cores dedicated)
+- [ ] **RAM:** Define allocation (suggested: 8-16GB)
+- [ ] **Disk Space:** Define allocation (suggested: 50-100GB)
+- [ ] **Node:** Which server hosts incentive instances? (TX1 or NC1)
+
+**Provisioning Plan:**
+- [ ] **Pterodactyl egg/template ready** for quick deployment
+- [ ] **Default modpack selection** (or allow recruit to choose?)
+- [ ] **Port allocation strategy** (how to assign ports without conflicts)
+- [ ] **Backup policy** for incentive instances
+
+**Access & Permissions:**
+- [ ] **Full server owner access** in Pterodactyl panel
+- [ ] **File management permissions** (FTP/SFTP access)
+- [ ] **Console access** for debugging
+- [ ] **Mod installation permissions** (can they install mods?)
+
+**Documentation for Recruits:**
+- [ ] "How to Access Your Incentive Instance" guide
+- [ ] "Managing Your Server" quick start
+- [ ] Resource limits and fair use policy
+- [ ] What happens to instance if they leave
+
+---
+
+### 2. Application Process Defined
+
+**Application Reception:**
+- [ ] **Where do applications go?** Discord DM to @frostystyle
+- [ ] **Alternative method?** (Email, Google Form, etc.)
+- [ ] **Response time commitment** (how fast will you respond?)
+
+**Review Criteria:**
+
+**For Builders:**
+- [ ] Portfolio quality (technical skill + aesthetic sense)
+- [ ] Understanding of modded Minecraft (which packs they've played)
+- [ ] Communication style (professional, collaborative?)
+- [ ] Availability match (can they commit to the timeline?)
+- [ ] Fire/Frost aesthetic understanding
+
+**For Social Media Helper:**
+- [ ] Social media management experience (proven track record)
+- [ ] Platform expertise (Discord, Twitter/X, TikTok, Reddit)
+- [ ] Content creation skills (graphics, video, copywriting)
+- [ ] Brand voice alignment (do they "get" Fire/Frost?)
+- [ ] Tools proficiency (Canva, Buffer, CapCut, etc.)
+
+**Vetting Process:**
+- [ ] **Phase 1:** Initial application review (accept/reject/need more info)
+- [ ] **Phase 2:** Interview (voice call, video call, or written?)
+- [ ] **Phase 3:** Test project (small assignment to evaluate skills)
+- [ ] **Phase 4:** Reference check (if applicable)
+- [ ] **Phase 5:** Final decision and offer
+
+**Interview Questions to Prepare:**
+
+**Builders:**
+1. Walk me through your favorite build. What were you trying to achieve aesthetically?
+2. How would you differentiate a "Fire" spawn from a "Frost" spawn visually?
+3. You're building a spawn for a tech-heavy modpack. What elements do you include?
+4. How do you handle creative blocks or when a build isn't working?
+5. What's your turnaround time for a spawn area (with given resources)?
+
+**Social Media Helper:**
+1. What social media platforms do you have the most experience with?
+2. How would you grow a brand-new gaming community from zero followers?
+3. Describe the "Fire vs Frost" brand voice in your own words.
+4. Show me an example of content you've created (or would create) for a gaming community.
+5. How do you measure social media success beyond follower count?
+
+**Test Projects:**
+
+**Builders:**
+- Build a small spawn area (32x32 platform) embodying either "Fire" OR "Frost" aesthetic
+- Time limit: 1-2 hours
+- Provide screenshot + brief explanation of design choices
+
+**Social Media Helper:**
+- Create 3 social media posts (one each for Discord, Twitter, TikTok concept) announcing Firefrost launch
+- Should demonstrate Fire/Frost brand voice understanding
+- Bonus: Create simple graphic mockup for one post
+
+---
+
+### 3. Application Tracking System
+
+**How to track incoming applications:**
+- [ ] **Spreadsheet template created** (Google Sheets or Excel)
+  - Columns: Name, Contact, Role Applied, Date Applied, Portfolio Link, Status, Interview Date, Notes
+- [ ] **Shared access** (does Meg need access?)
+- [ ] **Status workflow** (Applied → Reviewing → Interview → Test → Offer/Reject)
+
+**Communication Templates:**
+
+**Template 1: Application Received**
+```
+Hi [Name],
+
+Thanks for applying to join Firefrost Gaming as a [Builder/Social Media Helper]! We've received your application and are reviewing it now.
+
+We'll get back to you within [X days] with next steps.
+
+🔥❄️ Frostystyle
+Firefrost Gaming
+```
+
+**Template 2: Request for More Info**
+```
+Hi [Name],
+
+Thanks for your interest in Firefrost Gaming! Your application looks promising, but we'd love to learn more about [specific aspect].
+
+Could you provide:
+- [Specific request 1]
+- [Specific request 2]
+
+Looking forward to hearing back!
+
+🔥❄️ Frostystyle
+```
+
+**Template 3: Interview Invitation**
+```
+Hi [Name],
+
+We loved your application! We'd like to schedule a brief interview to discuss the [Builder/Social Media Helper] role.
+
+Are you available for a [voice/video] call on [dates/times]?
+
+We'll discuss:
+- Your experience and portfolio
+- The Fire/Frost vision in detail
+- Your incentive instance benefits
+- Next steps
+
+🔥❄️ Frostystyle
+```
+
+**Template 4: Test Project Assignment**
+```
+Hi [Name],
+
+Great talking with you! As the next step, we'd like to see your skills in action.
+
+Your assignment: [specific test project details]
+
+Timeline: [deadline]
+
+Submit to: [contact method]
+
+Questions? Let me know!
+
+🔥❄️ Frostystyle
+```
+
+**Template 5: Offer Letter**
+```
+Hi [Name],
+
+Congratulations! We'd love to have you join Firefrost Gaming as a founding [Builder/Social Media Helper].
+
+Here's what you'll receive:
+- Private dedicated Minecraft server (your incentive instance)
+  - [X] GB RAM, [Y] cores
+  - Full owner access via Pterodactyl panel
+  - Host on [TX1/NC1] node
+- Sovereign-Tier subscriber access ($499 value)
+- Recognition as founding team member
+- Creative freedom within Fire/Frost framework
+
+Next steps:
+1. Confirm acceptance by [date]
+2. We'll provision your incentive instance (takes ~1 hour)
+3. Onboarding begins [date]
+
+Welcome to the family. 🔥❄️
+
+Frostystyle
+```
+
+**Template 6: Rejection (Kind)**
+```
+Hi [Name],
+
+Thank you for applying to Firefrost Gaming. We really appreciate your interest and the time you put into your application.
+
+After careful consideration, we've decided to move forward with other candidates whose experience more closely matches our current needs.
+
+We encourage you to apply again in the future as we grow!
+
+Best of luck with your projects.
+
+🔥❄️ Frostystyle
+```
+
+---
+
+### 4. Recruitment Ad Finalized
+
+**Decisions to make:**
+
+- [ ] **Mention specific modpacks?** (Pro: Shows what they'll work on. Con: Limits flexibility)
+  - Current ad says "13+ curated modpacks" (general)
+  - Alternative: List 2-3 flagship packs as examples
+
+- [ ] **Application deadline?** (Pro: Creates urgency. Con: May limit quality applicants)
+  - Suggested: "Rolling applications, positions filled when qualified candidates found"
+  - Alternative: "Applications close [date]"
+
+- [ ] **Compensation clarity** (Currently says "Volunteer position" + benefits)
+  - Is this accurate and acceptable?
+  - Any future paid opportunities to mention?
+
+**Final Review:**
+- [ ] Proofread for typos/grammar
+- [ ] Verify contact info (@frostystyle Discord handle)
+- [ ] Ensure Fire/Frost branding is clear
+- [ ] All questions answered that applicants might have
+
+---
+
+### 5. Posting Strategy
+
+**Target Channels:**
+- [ ] r/feedthebeast (Reddit)
+- [ ] r/feedthebeast Discord server
+- [ ] r/admincraft (Reddit - for builder recruitment)
+- [ ] Modded Minecraft Discord communities (which ones?)
+- [ ] Twitter/X with #ModdedMinecraft hashtag
+- [ ] Firefrost Discord (when established)
+
+**Posting Schedule:**
+- [ ] **When to post?** (Best time: evenings/weekends for gaming communities)
+- [ ] **Stagger posts** or post all at once?
+- [ ] **Follow-up posts** if not enough applicants?
+
+**Engagement Plan:**
+- [ ] Monitor comments/questions on posts
+- [ ] Respond within [X hours]
+- [ ] Cross-post to drive traffic?
+
+---
+
+### 6. Onboarding Documentation Ready
+
+**Create these guides BEFORE making offers:**
+
+- [ ] **"Welcome to Firefrost"** - Overview for new team members
+- [ ] **"How to Access Your Incentive Instance"** - Step-by-step Pterodactyl guide
+- [ ] **"Fire vs Frost Philosophy"** - Deep dive on brand aesthetics
+- [ ] **"Team Communication"** - Discord channels, response times, working style
+- [ ] **"Builder Workflow"** - How to plan, build, review, deploy spawn areas
+- [ ] **"Social Media Workflow"** - Content calendar, approval process, posting schedule
+
+---
+
+## 🚨 CRITICAL: DO NOT POST UNTIL COMPLETE
+
+**The recruitment ad should NOT be posted until:**
+1. ✅ You can provision incentive instances within 24 hours of making an offer
+2. ✅ You have a clear application review process
+3. ✅ You can respond to applicants promptly (within 48 hours)
+4. ✅ Onboarding materials are ready
+
+**Why?**
+- Posting prematurely damages credibility
+- Delayed provisioning frustrates recruits
+- Slow responses lose good candidates
+- Poor onboarding creates confusion
+
+---
+
+## ESTIMATED TIME TO COMPLETE PREREQUISITES
+
+**Total: 2-3 hours spread across tasks**
+
+1. **Define incentive instance specs** - 30 minutes
+2. **Create application tracking spreadsheet** - 15 minutes
+3. **Prepare interview questions** - 30 minutes
+4. **Write communication templates** - 30 minutes
+5. **Finalize recruitment ad edits** - 15 minutes
+6. **Create onboarding guides** - 45-60 minutes
+
+**Can be done in one session or broken into smaller chunks.**
+
+---
+
+## NEXT STEPS
+
+1. Review this checklist with Michael
+2. Make decisions on open questions (modpack mentions, deadlines, etc.)
+3. Complete each prerequisite section
+4. Create onboarding documentation
+5. TEST the application process (mock application walkthrough)
+6. POST the recruitment ad
+7. Manage incoming applications
+
+---
+
+**Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️
+
+---
+
+**Document Status:** ACTIVE  
+**Ready to Post Ad:** When all checkboxes complete