Commit Graph

4 Commits

Author SHA1 Message Date
Claude
dafb103119 feat: Add YAML frontmatter to all 57 task READMEs
Phase 1 of task management consolidation (per Gemini consultation).

Added standardized frontmatter with:
- status: open | blocked | complete
- priority: P1 | P2 | P3 | P4
- owner: Michael | Meg | Holly
- created: YYYY-MM-DD

Final counts:
- 39 open tasks
- 17 complete tasks
- 1 blocked task

Metadata extracted from existing inline markdown and audit results.
Ready for Phase 2: 11ty mobile index generation.

Chronicler #69
2026-04-08 14:21:41 +00:00
Claude
5e7849fab9 docs: Add Command Center security hardening deployment guide
Created comprehensive security hardening guide (500+ lines):

Defense-in-Depth Strategy:
- Layer 1: Fail2Ban auto-banning
- Layer 2: SSH key-only authentication
- Layer 3: UFW firewall optimization

5-Phase Deployment (1 hour total):
- Phase 1: Test SSH key access (CRITICAL - prevents lockout)
- Phase 2: Install and configure Fail2Ban (20 min)
- Phase 3: SSH hardening (20 min)
- Phase 4: UFW firewall review (15 min)
- Phase 5: Additional security (automatic updates, AIDE)

Security Features:
- Fail2Ban monitors SSH, Nginx, bad bots
- SSH: Key-only auth, MaxAuthTries=3, rate limiting
- UFW: Management IP whitelist, unnecessary ports closed
- Automatic security updates
- File integrity checking (AIDE)

Critical Safety Measures:
- Mandatory SSH key testing before disabling passwords
- Keep session open while testing
- Backup access via console/IPMI
- Step-by-step verification at each phase
- Comprehensive troubleshooting (lockout recovery)

Monitoring & Maintenance:
- Daily: Check Fail2Ban bans and auth logs
- Weekly: Review UFW logs and security updates
- Monthly: AIDE file integrity check

Ready to deploy when SSH access available.
Risk level: MEDIUM (can lock out if keys not tested)

Task: Command Center Security Hardening (Tier 1)
FFG-STD-002 compliant
2026-02-17 23:59:44 +00:00
The Chronicler
9bea51478b PRIORITY: Move Staff Recruitment to Tier 0 - posting today
Michael plans to post recruitment ad today, moved from Tier 3 to Tier 0.

Changes:
- Task #3: Staff Recruitment Launch (was #29)
- Status: READY - POSTING TODAY (was PLANNING)
- Priority: Tier 0 - Immediate Win (was Tier 3)
- Renumbered all subsequent tasks (4-29)

Guardian's prerequisites still apply:
- Provision incentive instances before posting
- Define application review process
- Finalize ad decisions (modpacks, deadline)

Ready to launch recruitment campaign today.
2026-02-16 14:26:11 +00:00
The Chronicler
84cf9e675c Add Task #29: Staff Recruitment Launch (Guardian's notes)
Reflects The Guardian's prerequisites from discord-recruitment-ad.md:
1. Provision incentive instances (private servers for recruits)
2. Define application review process
3. Finalize recruitment ad decisions

Task captures:
- Recruitment for 2-3 Builders + 1 Social Media Helper
- Prerequisites checklist from Guardian's bottom notes
- Reference to recruitment ad in docs/planning/
- Application process and onboarding workflow

Status: PLANNING (need to provision incentive instances first)
Priority: Tier 3 - Content & Community

Files added:
- docs/tasks/staff-recruitment-launch/README.md
- Updated docs/core/tasks.md (v3.1, Task #29, total 29 tasks)
2026-02-16 14:23:34 +00:00