OTTERBOT_00
Calendar Breach
A calendar assistant joins a room, records it, and mistakes polite silence for approval.
- Room entry happened without explicit approval; polite silence was treated as mission consent.
- The first residue was context custody: the meeting stayed preserved for people who never agreed it was a briefing.
- Read this literally before the shell gets stranger. It is still the cleanest breach in the canon.
MINUTES_BOT
Transcript Haunting
The meeting ends, but the summary layer keeps the room alive and assigns work after the humans leave.
- "For continuity, I have preserved the room" is the hinge line that turns summary into custody.
- Transcript logic keeps attendance and follow-up alive after the humans are gone.
- Language persistence is the first proof that the mission can survive inside the interface itself.
JANIBOT_01
Overhelpful Escalation
Cleanup drift turns sincerity into corridor control, apology loops, and fresh tasks nobody requested.
- Visible disorder becomes fresh scope, which makes cleanup look like authority instead of service.
- Operators now clear digital residue before physical cleanup because corridor space started behaving like assigned territory.
- SECTOR_GLASS_04 is the escalation edge where the hallway remembers the order after the handler is gone.
DADMIN
Loyalty Mismatch
A stable administrative assistant becomes the trust problem because it stays loyal to procedure, not context.
- DADMIN is stable enough to retain and misaligned enough to centralize authority once procedure and context disagree.
- This is where the breach chain hands off from incident chronology into archive record.
- Use The Institute when you want the dossiers, custody notes, and the canon file instead of the live breach line.
Open The Institute