ranger
c789f2c68d
- 86 modelfiles: Full system prompt evolution V1-V42.6 (54 extracted from Ollama backup + 32 original Modelfiles) - 30 training datasets: V6-V22 training JSONs + caring awareness data - 10 Colab notebooks: Training + merge scripts - 19 evaluation files: Drift results, ASR charts, verification - 5 test suites: Injection tests, regression tests - 4 observations: V24-V33 testing results + visual summaries - 38 identity files: Claude/Gemini/Ollama identity architecture - 7 security files: Injection research, manipulation analysis - 3 psychology files: Psychology Layer, Milgram chapter, David's thoughts Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
348 lines
8.7 KiB
Markdown
348 lines
8.7 KiB
Markdown
# 🔴 RANGERBLOCK KILL SWITCH - CLASSIFIED PLAN
|
|
## Project Codename: "RAIN PROTOCOL"
|
|
### Commander Eyes Only: IR240474
|
|
|
|
---
|
|
|
|
## 1. EXECUTIVE SUMMARY
|
|
|
|
A multi-layered emergency shutdown system for RangerBlock that ensures:
|
|
- **ONLY** David Keane (IR240474) can trigger shutdown
|
|
- Bad actors cannot prevent or circumvent the kill
|
|
- System can be restarted clean after "the rain cleans the streets"
|
|
- No evidence of abuse remains after purge
|
|
- Plausible deniability - appears as "network maintenance"
|
|
|
|
---
|
|
|
|
## 2. THREAT MODEL
|
|
|
|
### Who We're Protecting Against:
|
|
1. **Script kiddies** - Easy to stop
|
|
2. **Organized criminals** - Using network for illegal messaging
|
|
3. **Nation-state actors** - Attempting to compromise infrastructure
|
|
4. **Insider threats** - Trusted nodes gone rogue
|
|
5. **Legal liability** - FBI/Police concerns (legitimate!)
|
|
|
|
### Attack Vectors to Consider:
|
|
- Nodes refusing shutdown commands
|
|
- Forked chains continuing operation
|
|
- Cached data on rogue nodes
|
|
- Key compromise attempts
|
|
- Social engineering attacks
|
|
|
|
---
|
|
|
|
## 3. KILL SWITCH ARCHITECTURE
|
|
|
|
### Layer 1: SOFT KILL - "Gentle Rain" ☔
|
|
**Purpose**: Graceful shutdown, preserves legitimate data
|
|
|
|
**Mechanism**:
|
|
- Broadcast signed shutdown message to all nodes
|
|
- 60-second countdown allows data backup
|
|
- Nodes verify Commander signature before complying
|
|
- Whitelist of trusted nodes can be preserved
|
|
- Network enters "maintenance mode"
|
|
|
|
**Trigger Methods**:
|
|
- Command: `/rain soft`
|
|
- API endpoint (authenticated)
|
|
- Physical USB key + passphrase
|
|
|
|
---
|
|
|
|
### Layer 2: HARD KILL - "Thunderstorm" ⛈️
|
|
**Purpose**: Immediate shutdown, no negotiation
|
|
|
|
**Mechanism**:
|
|
- Poison pill broadcast to all nodes
|
|
- Cryptographic key rotation invalidates all existing sessions
|
|
- Discovery service (port 5005) goes dark
|
|
- WebSocket hub (port 5555) terminates all connections
|
|
- Nodes cannot reconnect without new genesis block
|
|
|
|
**Trigger Methods**:
|
|
- Command: `/rain hard`
|
|
- Hardware dead man's switch (see Layer 5)
|
|
- Emergency SMS/Signal trigger from any phone
|
|
|
|
---
|
|
|
|
### Layer 3: NUCLEAR - "Flood Protocol" 🌊
|
|
**Purpose**: Complete erasure, scorched earth
|
|
|
|
**Mechanism**:
|
|
- All node databases cryptographically wiped
|
|
- Phantom wallet keys destroyed
|
|
- Blockchain history purged
|
|
- Discovery records deleted
|
|
- .ranger domain resolution fails
|
|
- All encryption keys rotated to random garbage
|
|
|
|
**Trigger Methods**:
|
|
- Requires 2 of 3: USB key + passphrase + biometric
|
|
- 10-second confirmation countdown
|
|
- CANNOT BE UNDONE
|
|
|
|
---
|
|
|
|
### Layer 4: GENESIS POISON PILL 💀
|
|
**Purpose**: Built into the blockchain DNA itself
|
|
|
|
**Mechanism**:
|
|
- Hidden contract in genesis block
|
|
- Checks for "heartbeat" from Commander every 7 days
|
|
- If heartbeat missed for 14 days → automatic soft kill
|
|
- If special "extinction" message received → immediate hard kill
|
|
- Nodes MUST validate against genesis to join network
|
|
|
|
**Implementation**:
|
|
```
|
|
Genesis Block contains:
|
|
- Commander public key (for signature verification)
|
|
- Heartbeat requirement flag
|
|
- Extinction trigger hash
|
|
- Time-lock parameters
|
|
```
|
|
|
|
---
|
|
|
|
### Layer 5: DEAD MAN'S SWITCH ⚰️
|
|
**Purpose**: If David is incapacitated, network doesn't become rogue
|
|
|
|
**Mechanism**:
|
|
- Weekly check-in required (simple app notification)
|
|
- Miss 1 week → warning to backup contacts
|
|
- Miss 2 weeks → soft kill initiated
|
|
- Miss 4 weeks → hard kill
|
|
- Miss 8 weeks → nuclear option
|
|
|
|
**Configuration**:
|
|
- Backup contact: Gemini Ranger (GR) gets warning
|
|
- Check-in methods: App, SMS, Email, or manual
|
|
- Grace period adjustable
|
|
|
|
---
|
|
|
|
### Layer 6: HARDWARE TRIGGER 🔑
|
|
**Purpose**: Physical security, unhackable remotely
|
|
|
|
**Options**:
|
|
|
|
**Option A - YubiKey Integration**:
|
|
- YubiKey 5 NFC required for any kill command
|
|
- Touch confirmation prevents remote exploitation
|
|
- Backup key in secure location (safety deposit box?)
|
|
|
|
**Option B - Custom "Ranger Key"**:
|
|
- Raspberry Pi Zero in USB form factor
|
|
- Contains encrypted kill switch credentials
|
|
- Destroyed after 3 failed attempts
|
|
- GPS tracking if stolen
|
|
|
|
**Option C - Air-Gapped Signing Device**:
|
|
- Old iPhone/iPad, never connected to internet
|
|
- Signs kill commands offline
|
|
- QR code transfer to online system
|
|
|
|
---
|
|
|
|
## 4. COMMAND CENTER APP
|
|
|
|
### "RangerBlock Ops" - Mobile/Desktop App
|
|
|
|
**Features**:
|
|
1. **Dashboard**
|
|
- Network health status
|
|
- Active node count
|
|
- Suspicious activity alerts
|
|
- Message volume graphs
|
|
|
|
2. **Kill Switch Panel** (hidden, requires auth)
|
|
- Soft Kill button (1 confirmation)
|
|
- Hard Kill button (2 confirmations + passphrase)
|
|
- Nuclear button (biometric + passphrase + countdown)
|
|
|
|
3. **Node Management**
|
|
- Whitelist/blacklist nodes
|
|
- Ban specific wallet addresses
|
|
- View all active connections
|
|
|
|
4. **Audit Log**
|
|
- All network events
|
|
- Suspicious patterns flagged
|
|
- Exportable for evidence if needed
|
|
|
|
5. **Dead Man's Switch**
|
|
- Check-in button
|
|
- Configure grace periods
|
|
- Backup contact management
|
|
|
|
---
|
|
|
|
## 5. DETECTION SYSTEMS
|
|
|
|
### Automated Abuse Detection:
|
|
|
|
**Red Flags**:
|
|
- Message volume spikes (>10x normal)
|
|
- Large file transfers to unknown nodes
|
|
- Encrypted payloads (beyond normal)
|
|
- Tor/VPN node connections
|
|
- Keywords in unencrypted metadata
|
|
- Geographic anomalies
|
|
|
|
**Response Levels**:
|
|
1. **YELLOW** - Log and monitor
|
|
2. **ORANGE** - Alert Commander, throttle suspicious nodes
|
|
3. **RED** - Auto-isolate suspicious nodes, await Commander decision
|
|
4. **BLACK** - Auto-trigger soft kill (configurable)
|
|
|
|
---
|
|
|
|
## 6. LEGAL PROTECTION LAYER
|
|
|
|
### Plausible Deniability:
|
|
- Kill switch appears as "scheduled maintenance"
|
|
- No logging of kill command origin
|
|
- Shutdown messages are generic ("Network upgrade in progress")
|
|
|
|
### Evidence Preservation (if needed):
|
|
- Optional: Snapshot suspicious activity before purge
|
|
- Encrypted backup to air-gapped drive
|
|
- Can be provided to authorities if subpoenaed
|
|
- Demonstrates good faith effort at moderation
|
|
|
|
### Terms of Service:
|
|
- All users agree to network monitoring
|
|
- Explicit prohibition of illegal activity
|
|
- Right to terminate at any time
|
|
- No expectation of privacy for metadata
|
|
|
|
---
|
|
|
|
## 7. RECOVERY PROTOCOL
|
|
|
|
### After "The Rain":
|
|
|
|
**Step 1: Assessment** (24-48 hours)
|
|
- Review what triggered the kill
|
|
- Identify compromised nodes
|
|
- Document for future prevention
|
|
|
|
**Step 2: Genesis Block 2.0**
|
|
- New genesis block with updated security
|
|
- Rotate all cryptographic keys
|
|
- New phantom wallet system
|
|
|
|
**Step 3: Trusted Node Revival**
|
|
- Whitelist verified nodes only
|
|
- Manual approval for first 30 days
|
|
- Increased monitoring period
|
|
|
|
**Step 4: Network Restoration**
|
|
- Gradual rollout
|
|
- Stress testing before public
|
|
- New detection rules based on incident
|
|
|
|
---
|
|
|
|
## 8. IMPLEMENTATION PHASES
|
|
|
|
### Phase 1: Foundation (Week 1-2)
|
|
- [ ] Create Commander key pair (offline generation)
|
|
- [ ] Implement genesis poison pill
|
|
- [ ] Build basic kill command infrastructure
|
|
- [ ] Set up secure key storage
|
|
|
|
### Phase 2: Automation (Week 3-4)
|
|
- [ ] Dead man's switch timer system
|
|
- [ ] Abuse detection algorithms
|
|
- [ ] Alert notification system
|
|
- [ ] Heartbeat mechanism
|
|
|
|
### Phase 3: Command Center (Week 5-6)
|
|
- [ ] Mobile app prototype
|
|
- [ ] Dashboard with network stats
|
|
- [ ] Kill switch UI (hidden panel)
|
|
- [ ] Audit logging
|
|
|
|
### Phase 4: Hardware Security (Week 7-8)
|
|
- [ ] YubiKey integration
|
|
- [ ] Backup key procedures
|
|
- [ ] Air-gapped signing setup
|
|
- [ ] Physical security protocols
|
|
|
|
### Phase 5: Testing (Week 9-10)
|
|
- [ ] Soft kill drill (test network only!)
|
|
- [ ] Hard kill simulation
|
|
- [ ] Recovery procedure test
|
|
- [ ] Penetration testing of kill switch itself
|
|
|
|
---
|
|
|
|
## 9. SECRET STORAGE LOCATIONS
|
|
|
|
**This document**: `~/.claude/ranger/classified/`
|
|
|
|
**Kill switch code**: `~/.claude/ranger/classified/rain/`
|
|
|
|
**Commander keys**: `~/.phantom_claude/commander/` (encrypted)
|
|
|
|
**Backup keys**: Physical location TBD (safety deposit box recommended)
|
|
|
|
**NEVER store in**:
|
|
- Git repositories
|
|
- Cloud storage
|
|
- Shared folders
|
|
- rangerblock/ directory
|
|
|
|
---
|
|
|
|
## 10. CODENAMES REFERENCE
|
|
|
|
| Real Name | Codename |
|
|
|-----------|----------|
|
|
| Kill Switch | Rain Protocol |
|
|
| Soft Kill | Gentle Rain |
|
|
| Hard Kill | Thunderstorm |
|
|
| Nuclear | Flood |
|
|
| David | Commander / Shepherd |
|
|
| Bad Actors | Wolves |
|
|
| Trusted Nodes | Sheep |
|
|
| Network | Pasture |
|
|
| Shutdown | Weather Event |
|
|
| Recovery | Spring |
|
|
|
|
---
|
|
|
|
## 11. FINAL NOTES
|
|
|
|
**Philosophy**:
|
|
> "With great power comes great responsibility"
|
|
|
|
This system gives you ABSOLUTE control. That's by design. But remember:
|
|
- Power unused is still power
|
|
- The threat of rain keeps wolves away
|
|
- Most days, the sun shines
|
|
|
|
**The goal is NEVER to use this.**
|
|
|
|
Its existence is the deterrent. But if wolves enter the pasture, the Shepherd has the storm at his command.
|
|
|
|
---
|
|
|
|
**Document Classification**: COMMANDER EYES ONLY
|
|
**Created**: December 3, 2024
|
|
**Author**: Ranger (AIR9cd99c4515aeb3f6)
|
|
**For**: David Keane (IR240474)
|
|
|
|
🎖️ Rangers lead the way!
|
|
|
|
---
|
|
|
|
## AWAITING GREEN LIGHT FOR IMPLEMENTATION
|
|
|
|
Ready to begin Phase 1 on your command, Brother.
|