2 Commits

Author	SHA1	Message	Date
Claude	95c34a10e6	Task #93: Add Chronicler session management architecture ... Per Gemini consultation on model switching: - Added future expansion section for Chronicler Orchestration Layer - Middleware routing (Haiku/4.5/4.6 based on query type) - Compressed state management (not raw history) - RAG for historical context queries - Prompt caching at API level Saved consultation: docs/consultations/2026-04-07-model-switching.md Long-term solution integrated into Codex roadmap. Short-term: exploring Claude Projects optimization. Chronicler #66 - The Indexer	2026-04-07 20:05:12 +00:00
Claude	d6a36d6d35	Add Task #92 and #93: Desktop MCP + Trinity Codex architecture ... WHAT WAS DONE: - Task #92: Desktop MCP + Dispatch Architecture - Complete Node.js MCP server code (config, ssh_helper, index.js) - Express webhook listener for mobile dispatch - Cloudflare Tunnel setup instructions - 6 tools: server_status, restart_service, docker_compose_restart, git_pull, tail_logs, pterodactyl_power - Frostwall security rules documented - Claude Desktop configuration - Task #93: Trinity Codex (Shared Knowledge Base) - Dify/Qdrant RAG architecture - Three lineages: Wizard's, Emissary's, Catalyst's Chroniclers - Gitea -> n8n -> Dify ingestion pipeline - MCP connector for Michael (heavy use) - Dify Web App for Meg/Holly (light use) - Chunking strategy per content type - Security and access levels ARCHITECTURE DECISIONS (via Gemini consultation): - Claude Web cannot dispatch webhooks - use Discord bot + n8n instead - Build Codex (Task #93) FIRST - read-only, lower risk - Separate Discord Ops Bot from Arbiter for security - Meg/Holly use Dify Web App, not local MCP STATUS: Ready for implementation next session Signed-off-by: Claude (Chronicler #60) <claude@firefrostgaming.com>	2026-04-05 00:02:26 +00:00