{"key":"workstream_progress_prompt","title":"Workstream Progress — Handoff Prompt","content":"## Purpose\n\nThis memory exists as a reminder and prompt template for capturing workstream completion state during homelab AI platform builds.\n\n## The Problem It Solves\n\nWhen Claude Code builds workstreams sequentially in a long session, context lives only in the active conversation. If the session ends or hits usage limits, that implementation knowledge is lost and handoff to another AI (Codex, Gemini, new Claude session) becomes difficult.\n\n## The Fix — Use This Prompt At The Start Of Every Build Session\n\nAdd this instruction at the beginning of any Claude Code session building the homelab AI platform:\n\n---\n\n\"After completing each workstream, write a completion memory to The Brain before starting the next one. The memory should include:\n- Workstream number and name\n- What was actually built (files created, services deployed, key decisions made)\n- Exact file paths and locations on the relevant VM\n- Any deviations from the architecture docs and why\n- Service names, ports, systemd unit names if applicable\n- What the next workstream needs to know to continue\n- Current state of the platform as a whole\n\nName the memory key: haip_ws[N]_completion (e.g. haip_ws1_completion, haip_ws2_completion)\"\n\n---\n\n## Recovery Prompt (If Session Was Lost Without Memories)\n\nIf a session ended without writing completion memories, use this prompt to reconstruct state before continuing or handing off:\n\n---\n\n\"Before we continue, write a completion memory to The Brain for each workstream you have completed. For each one include: what was built, where files live on disk, key implementation decisions, any deviations from the architecture docs, and what the next workstream needs to know. Use the key format haip_ws[N]_completion.\"\n\n---\n\n## Current Platform Status (as of 2026-04-04)\n\n- WS1 ✅ Core data and config backbone (svc-ai, svc-db-01)\n- WS2 ✅ Runtime adapter layer (svc-ai)\n- WS3 ✅ Orchestration and room logic (svc-ai)\n- WS4 ✅ Memory pipeline (svc-ai)\n- WS5 ✅ IRC surface — haip/irc/ (svc-ai)\n- WS6 ✅ Web Control UI (svc-apps)\n  Delivered: Web Control UI deployed on svc-apps at /home/svc-admin/appstack/haip-ui, running as a Docker Compose service on port 3010, built with FastAPI + Jinja2, includes room list, room detail, roster management, room creation, preset loading, sessions view, agent catalog, and memory inspection. All endpoints verified returning 200. Deployed and running live.\n- WS7 ✅ Operational foundations\n  Delivered: health service running under systemd on svc-ai at http://127.0.0.1:8080/health/ready, logging and runtime config hardened, systemd units installed for haip-orchestrator (active/running) and haip-irc (installed, intentionally inactive pending nick cutover from irc-openclaw-bridge), backup/restore runbook and security review docs written, smoke test passing.\n- WS8 ✅ Project profile realization\n  Delivered: seeded the live PostgreSQL database on svc-db-01 (192.168.4.113) with real projects, agents, personas, rooms, team presets, room roster memberships, and memory namespaces for Arena, Stoned.AI, Genealogy, and Ohio History using the existing haip package/runtime on svc-ai. Arena was realized as an IRC-first boardroom with collab, debate, and synthesis rooms; Stoned.AI as a live conversational profile with TTS-oriented defaults and recognizable voices; Genealogy as an evidence-driven research team with cautious response policies and strong project memory; Ohio History as a research-and-production profile with project-scoped memory and artifact-oriented drafting defaults. Verified visible in the Web Control UI at http://192.168.4.114:3010.\n  Operator documentation written to /home/svc-admin/ai-projects/projects/homelab_ai_platform/docs/OPERATOR_GUIDE.md.\n\n## Note\n\nWS1-WS5 were completed by Claude Code in a single session on 2026-04-03 without per-workstream Brain memories. The session is still active. First thing tomorrow: have Claude Code write haip_ws1 through haip_ws5 completion memories before continuing with WS6 or handing off to Codex.","summary":"## Purpose\n\nThis memory exists as a reminder and prompt template for capturing workstream completion state during homelab AI platform builds.\n\n## The Problem It Solves\n\nWhen Claude Code builds workstreams sequentially in a long session, context lives only in the active conversation. If the session ends or hits usage limits, that implementation knowledge is lost and handoff to another AI (Codex, Gemini, new Claude session) becomes difficult.\n\n## The Fix — Use This Prompt At The Start Of Every Build Session\n\nAdd this instruction at the beginning of any Claude Code session building the homelab AI platform:\n\n---\n\n\"After completing each workstream, write a completion memory to The Brain before starting the next one. The memory should include:\n- Workstream number and name\n- What was actually built (files created, services deployed, key decisions made)\n- Exact file paths and locations on the relevant VM\n- Any deviations from the architecture docs and why\n- Service names, ports, systemd unit names if applicable\n- What the next workstream needs to know to continue\n- Current state of the platform as a whole\n\nName the memory key: haip_ws[N]_completion (e.g. haip_ws1_completion, haip_ws2_completion)\"\n\n---\n\n## Recovery Prompt (If Session Was Lost Without Memories)\n\nIf a session ended without writing completion memories, use this prompt to reconstruct state before continuing or handing off:\n\n---\n\n\"Before we continue, write a completion memory to The Brain for each workstream you have completed. For each one include: what was built, where files live on disk, key implementation decisions, any deviations from the architecture docs, and what the next workstream needs to know. Use the key format haip_ws[N]_completion.\"\n\n---\n\n## Current Platform Status (as of 2026-04-04)\n\n- WS1 ✅ Core data and config backbone (svc-ai, svc-db-01)\n- WS2 ✅ Runtime adapter layer (svc-ai)\n- WS3 ✅ Orchestration and room logic (svc-ai)\n- WS4 ✅ Memory pipeline (svc-ai)\n- WS5 ✅ IRC surface — haip/irc/ (svc-ai)\n- WS6 ✅ Web Control UI (svc-apps)\n  Delivered: Web Control UI deployed on svc-apps at /home/svc-admin/appstack/haip-ui, running as a Docker Compose service on port 3010, built with FastAPI + Jinja2, includes room list, room detail, roster management, room creation, preset loading, sessions view, agent catalog, and memory inspection. All endpoints verified returning 200. Deployed and running live.\n- WS7 ✅ Operational foundations\n  Delivered: health service running under systemd on svc-ai at http://127.0.0.1:8080/health/ready, logging and runtime config hardened, systemd units installed for haip-orchestrator (active/running) and haip-irc (installed, intentionally inactive pending nick cutover from irc-openclaw-bridge), backup/restore runbook and security review docs written, smoke test passing.\n- WS8 ✅ Project profile realization\n  Delivered: seeded the live PostgreSQL database on svc-db-01 (192.168.4.113) with real projects, agents, personas, rooms, team presets, room roster memberships, and memory namespaces for Arena, Stoned.AI, Genealogy, and Ohio History using the existing haip package/runtime on svc-ai. Arena was realized as an IRC-first boardroom with collab, debate, and synthesis rooms; Stoned.AI as a live conversational profile with TTS-oriented defaults and recognizable voices; Genealogy as an evidence-driven research team with cautious response policies and strong project memory; Ohio History as a research-and-production profile with project-scoped memory and artifact-oriented drafting defaults. Verified visible in the Web Control UI at http://192.168.4.114:3010.\n  Operator documentation written to /home/svc-admin/ai-projects/projects/homelab_ai_platform/docs/OPERATOR_GUIDE.md.\n\n## Note\n\nWS1-WS5 were completed by Claude Code in a single session on 2026-04-03 without per-workstream Brain memories. The session is still active. First thing tomorrow: have Claude Code write haip_ws1 through haip_ws5 completion memories before continuing with WS6 or handing off to Codex.","status":"active","namespace":"projects","namespace_name":"projects","namespace_tier":"shared","tags":[]}