feat: add wiki knowledge layer (Phase 0 + Phase 1 seed)

Implements LLM-compiled wiki layer between raw session logs and live
CONTEXT.md, inspired by Karpathy's knowledge base workflow. Adds wiki/
directory structure, article templates, spec docs, and seeds first two
articles (Cascades of Tucson, GuruRMM) from 60+ session logs.

Updates CLAUDE.md to check wiki first on all context-loading triggers.
Captures verified ACG IP/hostname map and Neptune physical-location
clarification (Dataforth D2, subnet overlap TODO) in memory.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-05-24 15:42:38 -07:00
parent 435e921300
commit cd80f5e447
19 changed files with 1533 additions and 6 deletions

56
wiki/_templates/client.md Normal file
View File

@@ -0,0 +1,56 @@
---
type: client
name: <slug>
display_name: <Human Readable Name>
last_compiled: YYYY-MM-DD
compiled_by: <session_id>
sources: []
backlinks: []
---
# <Client Display Name>
## Profile
- **Contract type:** Managed | Break-fix | Project | Prepaid block
- **Key contacts:** Name (title, email/phone)
- **Billing rate:** $X/hr
- **Hours remaining (if prepaid):** N hrs as of YYYY-MM-DD
- **Active ticket:** Syncro #XXXXX
## Infrastructure
### Servers & Services
| Host | IP | Role | OS | Notes |
|---|---|---|---|---|
### Email & Identity
- **M365 tenant:** tenant.onmicrosoft.com
- **MX / mail flow:** ...
- **MFA status:** ...
### Network
- **ISP / WAN:** ...
- **Firewall:** ...
- **VPN:** ...
## Access
- SSH: `ssh user@IP` (key in vault: `clients/<name>/...`)
- RDP: IP:port
- Admin URL: ...
- Vault path: `clients/<name>/`
## Patterns & Known Issues
*(Recurring ticket types, common failure modes, things that always come up)*
## Active Work
*(Current open projects or tickets — brief, link to CONTEXT.md or ticket# for detail)*
## History Highlights
*(Major incidents, big projects, key decisions — one-liners with dates)*
## Backlinks
*(Other wiki articles related to this client)*

View File

@@ -0,0 +1,31 @@
---
type: pattern
name: <slug>
display_name: <Pattern Name>
last_compiled: YYYY-MM-DD
compiled_by: <session_id>
sources: []
backlinks: []
---
# <Pattern Name>
## Rule
*(One-sentence statement of the pattern — the thing to always do or never do)*
## Why
*(Why this rule exists — the incident, constraint, or hard-learned lesson behind it)*
## How to Apply
*(When and where this applies. Edge cases. What "good" looks like vs. what to avoid)*
## Examples
*(Session log references where this played out — dates and brief context)*
## Backlinks
*(Projects, clients, or systems where this pattern is especially relevant)*

View File

@@ -0,0 +1,50 @@
---
type: project
name: <slug>
display_name: <Human Readable Name>
last_compiled: YYYY-MM-DD
compiled_by: <session_id>
sources: []
backlinks: []
---
# <Project Display Name>
## Summary
*(What it is, current maturity, who uses it, what problem it solves)*
## Architecture
### Components
| Component | Location | Tech | State |
|---|---|---|---|
### Key Files & Repos
- **Repo:** gitea link
- **Config:** path
- **Logs:** path
- **API:** URL
## Development
### Current Focus
*(Active dev areas, recent decisions, in-flight work)*
### Patterns & Anti-Patterns
*(Code patterns enforced, anti-patterns discovered, reasons — reference memory entries where applicable)*
### Build & Deploy
*(How to build, how to deploy, what to watch for, rollback procedure)*
## Active State
*(Brief current state — link to CONTEXT.md for live detail; do not duplicate live state here)*
## History Highlights
*(Major milestones, pivots, incident resolutions — one-liners with dates)*
## Backlinks
*(Other wiki articles related to this project)*

42
wiki/_templates/system.md Normal file
View File

@@ -0,0 +1,42 @@
---
type: system
name: <hostname>
display_name: <Hostname>
last_compiled: YYYY-MM-DD
compiled_by: <session_id>
sources: []
backlinks: []
---
# <Hostname>
## Identity
- **Hostname:** ...
- **IP:** ...
- **Role:** ...
- **Location:** Physical | VM on <host>
- **OS:** ...
- **Tailscale IP:** ... (if applicable)
## Specs
*(CPU, RAM, disk, NIC — or VM config: vCPU, vRAM, virtual disk)*
## Services
| Service | Port | Notes |
|---|---|---|
## Access
- **SSH:** `ssh user@IP` (key in vault: `infrastructure/<name>/...`)
- **RDP:** IP:port (if applicable)
- **Console:** iDRAC / Proxmox / Unraid UI / etc.
- **Vault path:** `infrastructure/<name>/`
## Known Issues & Quirks
*(Historical problems, workarounds, things that have surprised us — the stuff not in any doc)*
## Backlinks
*(Projects running on this system, clients whose infra lives here)*