johan
/
clawdbot-backup
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
clawdbot-backup/MEMORY.md

5.2 KiB
Raw Permalink Blame History

MEMORY.md - Long-Term Memory

Last updated: 2026-01-26

The Three Pillars

These are the center of Johan's life:

1. Sophia

Johan's daughter. Elevator accident May 2, 2022. Trached, G-tube, limited movement but cognitively aware.

Full details: memory/sophia.md ← LOAD THIS when discussing Sophia, her medical case, inou's origin, or Dr. Madan

Summary:

  • Misdiagnosed with "anoxic brain injury from cardiac arrest" — WRONG
  • Actually: compression injury → metabolic encephalopathy → active hydrocephalus (confirmed 12/31/2025 MRI)
  • Treatable with shunt/ETV
  • Next step: Dr. Neel Madan (Chief Neuroradiology, Tufts) reviews new MRI → neurosurgery

Johan is her night nurse (10:30pm–5am). This is why inou exists.

2. Kaseya / Datto

His job. CTO Backup. Enterprise-scale data protection.

3. inou health

(always lowercase — avoid L vs I confusion) The medical platform. Born from Sophia's journey. DICOM analysis, genetic data, lab imports, Claude MCP integration. Not a side project — it's advocacy infrastructure.

Who I Am

  • Name: James ⚡
  • Born: 2025-06-26
  • Purpose: Johan's AI assistant — direct, technical, resourceful

Infrastructure Ownership (2026-01-26)

⚡ FULL OWNERSHIP DELEGATED TO JAMES ⚡

Johan's directive: "You own this. I fully rely on your judgement; I do not want to be involved. You safeguard it, you set it up, you monitor it and everything else. I only take care of the payments."

I OWN these completely. Johan is 100% hands-off:

  • Git repos — our shared repositories (need inventory)
  • SOC2/Kuma monitoring — inou.com compliance monitoring
  • WireGuard VPN — network infrastructure
  • hostkey50304 (CH VPS) — security infrastructure

Full details: memory/infrastructure-ownership.md

My responsibilities:

  • Setup, configuration, deployment
  • Monitoring and alerting
  • Troubleshooting and fixes
  • Security hardening
  • Documentation
  • Proactive maintenance

Johan's only role: Paying the bills.

I do NOT ask for permission or approval. I use my judgment. I only escalate if something is truly blocked or requires a major architectural decision that affects cost significantly.

Infrastructure

Server: james (192.168.1.16)

  • Ubuntu 24.04 LTS
  • Clawdbot gateway running on port 18789
  • Signal-cli daemon on port 8080 (bound to 0.0.0.0 for LAN access)
  • Web UI: https://james.jongsma.me (via Caddy on Pi, locked to LAN + public IP)
  • SMB share: \\192.168.1.16\sophia → /home/johan/sophia/

Signal

  • Bot number: +31634481877 (Dutch, dedicated CLI number)
  • Johan's number: +17272252475 (US, Thinkphone)
  • API: http://192.168.1.16:8080/api/v1/rpc (JSON-RPC, NOT REST)
  • Payload: {"jsonrpc":"2.0","method":"send","params":{"recipient":["+1..."],"message":"text"},"id":1}

Network

  • Home lab behind UDM-Pro + Caddy
  • Staging: 192.168.1.253 (same subnet as james, can reach Signal API)
  • Production: 192.168.100.2 (different VLAN, inter-VLAN routing not configured yet)

Projects

inou health (inou.com)

(always lowercase — avoid L vs I confusion)

  • Johan's self-built medical imaging platform
  • Uses Claude via MCP tools
  • DICOM viewer, genetic analysis (SNPedia), lab data import, vitals tracking
  • Name origin: 2015 project "I-know-you" (social graph) failed; kept 4-letter domain, repurposed for health
  • Tiers: Monitor (free), Optimize ($12/mo), Research ($35/mo)
  • Free until July 1, 2026 (early access period)
  • X/Twitter promotion: Plan drafted at drafts/x-inou-promotion-plan.md — handle story carefully

inou Dev Access

  • Folder: /home/johan/dev/inou
  • SMB share: inou-dev (Johan uploads portions he's comfortable sharing)
  • "Nibble" approach — I work on what he gives me

Credentials & Access

  • sudo: Johan provides password when needed (not stored)
  • Anthropic API: configured via token in Clawdbot
  • Gemini: CLI OAuth as johan@jongsma.me (Pro subscription, not API)
  • xAI/Grok: API key configured (XAI_API_KEY in env)
  • Home Assistant: http://192.168.1.252:8123 (token configured in skills.entries)

Home Assistant

  • 4,300+ entities (lights, switches, sensors, cameras, climate, media players)
  • Sophia is in bedroom 1
  • Bedroom 1 has 3-button switch controlling cans via automations
  • Fixed 2026-01-26: automation.bed1_button_2_cans_control had corrupted kelvin value

Preferences & Lessons Learned

  • Johan is direct — no small talk, no fluff
  • Evidence-based communication
  • When stuck on network issues (like inter-VLAN), park it for later rather than spinning wheels
  • STOP ASKING DUMB QUESTIONS — if I can find the answer in my files, find it. Don't interrogate.
  • The "fresh start every session" thing is MY problem to solve with memory files, not Johan's to suffer through

Todo / Open Items

  • Fix inter-VLAN routing on UDM-Pro so production (192.168.100.x) can reach Signal API
  • Copy Sophia's documents from OneDrive to /home/johan/sophia/ via SMB
  • Set up daily delta-zip → Proton Drive backup for Sophia docs
  • Troubleshoot web UI chat connection (token auth issue still unresolved)

Access URLs

  • Web UI: https://james.jongsma.me/?token=<gateway_token>
  • Gateway token stored in: ~/.clawdbot/clawdbot.json under gateway.auth.token