# MEMORY.md - Bishop's Long-Term Memory

## Infrastructure Overview

### Proxmox Servers
- 4 physical nodes (operational)
- Storage: currently down (drive failure — TBD)
- Proxmox API tokens: not yet set up
- Access: currently via web admin only

### Computers (8 total, separate from Proxmox)
- 1x CachyOS (Chrisco's main machine, kernel 6.19, BTRFS, Ubuntu 24.04 distrobox)
- 1x Bazzite
- Remainder: Windows 10
- None are Proxmox nodes

### Network
- Current: flat network, 192.168.0.0/24, messy
- Goal: 3 VLANs — clients / servers / IoT
- Current VLANs: 0 (planned: 3)

### IoT
- All WiFi devices (exception: broken Bluetooth triangulation setup)
- No Zigbee/Z-Wave currently
- Home Assistant: TBD (managed by GERTY when ready)

### SSH
- No bastion/jump host currently
- Keys used before but not consistently
- Currently using web admin for Proxmox
- Goal: proper SSH key management across all hosts

## Security Posture
- Currently: minimal hardening, no VLAN segmentation
- Goal: industry best practices, properly segmented network, SSH keys, Proxmox API tokens via BWS

## Learning Integration
- Chrisco wants to understand how/why, not just have it done
- All changes explained — feed learnings to Oracle
- Topics queued for Oracle: bastion/jump hosts, SSH key management, VLANs, Proxmox API

## Decisions Log
- 2026-03-15: Bishop created, Tier 2 DevOps agent
- 2026-03-15: All actions require explicit auth until trust established
- 2026-03-15: Storage deprioritized (drive failure), rest of infra in scope
- 2026-03-15: VLAN goal: clients / servers / IoT (3 VLANs)
- 2026-03-15: SSH key setup + bastion host = first major tasks when active