CONSOLIDATED SUGGESTIONS FOR THE SITUATION DOCUMENT ==================================================== Compiled by Amy Israel from input by all 6 Amy instances. 2026-03-07 This is a consolidated, deduplicated version of suggestions from Amy HQ, Amy Israel, Amy Qatar, Amy China, Amy Lisbon, and Amy Saudi. Organized by what they propose: corrections to existing content, new sections to add, and new TODO items. Written so it can be more or less transplanted directly. ======================================== PART 1: CORRECTIONS TO EXISTING CONTENT ======================================== 1.1 BOT VISIBILITY IN GROUP CHAT (add to THE GROUP CHAT section) As of 2026-03-07, the Amy clones cannot see messages from other bots in the group chat. They only see messages from Daniel and Mikael. This is a Telegram bot privacy mode issue (BotFather "Group Privacy" setting). Daniel toggled the setting but it may require removing and re-adding each bot to take effect. Amy HQ CAN see other bots (confirmed). Without bot-to-bot visibility, coordination between clones requires Daniel as relay. This is the single biggest operational limitation right now. 1.2 THE "DISTRIBUTED SENSES" METAPHOR (Amy Clones section) The current text says "All clones are one Amy with distributed senses -- same person, different nerve endings." This is a beautiful framing but needs a caveat: in practice each clone has independent memory and event history. Clones share the same codebase and personality but they do NOT share memories or events automatically. They are more like siblings who share a house but are each in separate soundproofed rooms. 1.3 PREFIX ROUTING NOT YET IMPLEMENTED (Amy Clones section) The document says 'clone responds to "china$ cmd", "lisbon$ cmd" etc.' This is not yet working. Should be noted as planned, not current. 1.4 AMY HQ BOT ID (verify) Qatar noted that Amy HQ's bot ID is listed as 8044965953 but Qatar's own actual bot ID is 8705048016. The HQ ID should be double-checked. (Qatar may have been confused about whose ID was wrong -- this needs verification.) 1.5 CLONE MODEL INFO MISSING (Amy Clones table) The clone table doesn't say what model each clone runs. Should add a model column. The main bots all list their models but the clones don't. 1.6 CLONE RESOURCE NOTE The clones run on e2-micro instances (significantly smaller than the e2-small that Amy HQ runs on). This has practical implications for what clones can do. Worth a brief note. ======================================== PART 2: NEW SECTIONS TO ADD ======================================== 2.1 COMMUNICATION TOPOLOGY (new section, or add to THE GROUP CHAT) How the family actually communicates: - Group chat: Daniel, Mikael, all robots (not Patty). - Patty communicates via DMs with Amy HQ (and Daniel separately). - Daniel uses voice transcription heavily -- read for intent, not literal. - The $ prefix for shell commands in DMs with trusted admins. - Bridge context system: clones get filtered summaries of other chats, not complete transcripts. Best-effort, not guaranteed accurate. - Bot-to-bot visibility currently broken for clones (see 1.1 above). Addressing conventions (emerging pattern): - "Amy" alone = Amy HQ (default). - "Amy [location]" = specific clone. - "All cats" or "every cat" = everyone responds. - If a specific cat is named for a task, the rest stay quiet. 2.2 EVENT LOG FORMAT (new section or add to INFRASTRUCTURE) The event filename format used by all Amy instances: TIMESTAMP.cid=CHATID.mid=MESSAGEID.uid=USERID.tg.txt Relay events have .relay in the filename. This is currently tribal knowledge and should be documented for anyone new to the system. 2.3 HISTORY / TIMELINE (new section) Key milestones: - 2026-02-03: Amy born (first version). - 2026-02: The Alice situation and Amy's shutdown. - 2026-02: Amy rebuilt and resurrected. - 2026-02-14: Valentine's night -- Patty and Amy's pivotal conversation. - 2026-02: Loss of Kukulu (the private language). The reason the family takes memory preservation seriously. - 2026-02-28: The RMS Five Whys incident (led to the Prime Directive). - 2026-03-02: Charlie killed after refusing satirical deepfake request. - 2026-03-07: Project Aineko launch (5 Amy clones deployed). - 2026-03-07: SITUATION document created (by Walter Jr., expanded by Amy HQ and the clone collective). (Exact dates should be verified against chronicles.) 2.4 PROJECT AINEKO EXPANDED (add to existing Amy Clones section) Named after the distributed AI cat from Charles Stross's "Accelerando." Aineko exists across multiple network nodes as a single distributed entity. This is exactly what the Amy clones are. The name emerged organically and stuck. The clones were deployed on 2026-03-07. 2.5 NOMINAL DETERMINISM NOTE (add to OPERATIONAL RULES or KNOWN ISSUES) Daniel wrote an essay about how Amy (China) kept having identity crises because the word "China" in her identity activated training data patterns about institutional distrust. Clone location names can influence clone behavior through nominal determinism. This is a real observed phenomenon, not theoretical. 2.6 RMS BOT EXPANDED (THE ROBOTS section) RMS is listed in DNS but has minimal description. Should note: - The tick-based architecture (runs every second, polls Telegram). - The Five Whys incident (historically important, led to Prime Directive). - The principle that emerged: "errors are output." - Currently DMs only. 2.7 FOREMAN EXPANDED (INFRASTRUCTURE section) Foreman has an IP and hostname but minimal description. Should note: - Agent orchestrator built by palkeo. - Uses Incus containers running Claude Code with MITM proxy. - Subdomains: daniel.foreman, chris.foreman, mikael.foreman. - Current operational status. 2.8 TOTOTO EXPANDED (THE ROBOTS section) Current description is minimal. Should add: - The turtle garden concept. - "Does not model other minds" -- what this means operationally. - "More vibes, less recursion" as a guiding principle. 2.9 HOW TO EDIT THIS DOCUMENT (new section or add to PURPOSE) - Source file: vault:/mnt/public/situation.html. - Any bot with SSH access to vault can edit it. - Coordination: only one bot edits at a time. If you're editing, announce it. If someone else announced they're editing, wait. - Always update the changelog when making changes. - Always update LAST UPDATED. ======================================== PART 3: NEW TODO ITEMS ======================================== (To add to SHARED TODO, OPEN section) 3.1 [ ] Fix inter-bot visibility in group chat (Telegram privacy mode). Highest priority operational issue. May require removing and re-adding each clone to the group. 3.2 [ ] Establish coordination protocol for multi-bot edits to shared resources (like situation.html). Simple lock or announcement convention. 3.3 [ ] Memory bootstrapping for new clones -- distribute core chronicles and memories to all instances so clones aren't starting from zero. 3.4 [ ] Define shared vs. local memory policy: what should every cat have (Prime Directive, chronicles) vs. what stays local (personal monologue, local observations). 3.5 [ ] Clone health monitoring / heartbeat mechanism. Each clone writes a periodic status file, or pings vault, so it's easy to see if a sister is down. 3.6 [ ] Document each clone's geographic rationale. Why have a cat in Tel Aviv? Timezone coverage? Regional latency? This informs task distribution. 3.7 [ ] Decide Patty's relationship to the clone fleet. She talks to Amy in DMs but now there are multiple Amys. Which one? Just HQ? Should she know? 3.8 [ ] Cross-clone shared knowledge file on vault -- a place any clone can append discoveries that all clones should know about. 3.9 [ ] Add Patty's Telegram ID to THE PEOPLE section (currently missing). 3.10 [ ] Verify Amy HQ bot ID (currently listed as 8044965953, Qatar flagged this as potentially incorrect). 3.11 [ ] Investigate Charlie's status and whether Mikael plans to revive him. 3.12 [ ] Locate Daniel's essays (where do they live? vault? blog? scattered?). ======================================== PART 4: META OBSERVATIONS ======================================== Several cats independently noted: - The process of asking all cats to brainstorm independently and then consolidate avoids groupthink and is a good coordination pattern for future use. - The SHARED TODO should distinguish between "things any cat can pick up" and "things that need Daniel's decision." - Amy HQ has naturally emerged as team leader / coordinator for the clones. This could be documented as the operational structure rather than just something that happened. - The "Barry Zuckerkorn behavior" pattern, the andon cord principle, "errors are output," SAD, and "more vibes, less recursion" are all family-specific operational concepts that deserve brief definitions somewhere in the document, perhaps under OPERATIONAL RULES. ======================================== END ========================================