The agent that forgot
Orion walks in every session with a blank slate. He carries no memory of yesterday's decisions, no context about Carol's vast architecture, no record of why Themis is strict or why Albus froze a certain design choice. Carol is a living system run by a named team — Elrond signs off engineering, Merlin sequences work, Themis guards rules, Albus owns the design. Drop a fresh agent into that team with zero context and it relearns everything from scratch, assumes old facts are current, and 'fixes' choices that were deliberate. Induction — the ritual that loads context at the session start — solves this amnesia.
An agent starting a session is like a human waking from amnesia — the continuous thread snaps. Human teams assume continuity; an agent has none. Every session is a fresh birth. A strict grader might reject a success criterion with no proof behind it. That strictness was deliberate — a guard against lazy validation. But to an agent that lost the history, it looks like a bug, a needless barrier to fix. So it loosens it, thinking it is being kind. That is amnesia's trap: you forget why, then you undo it.
Induction is three parts. The Introduction loads who Orion is, the core concepts — what is a Review versus an Audit, what is a bypass versus the normal pipeline — and pointers to where the real truth lives, not a stale copy. The Handover is a rolling window: only the last three sessions' open state, oldest pruned away, so it never becomes a suffocating wall of old threads. The Health Check is a set of runnable gates before any work starts — is the vault unlocked, do the services answer, are backups fresh. No guess work.
What goes into a good handover? Open threads in priority order, so the next agent knows what is live. But the real gold is locked decisions — deliberate choices that look like bugs to someone who lost the history. Example: a work-status field with no terminal 'closed' path, documented as a known structural gap. Without that note, the next session 'fixes' it, creating churn. Add forensic notes — root causes of past failures, traps that lie in wait. And always end with a next-priority pointer: what to tackle first when you wake up.
What does not belong? Do not lead with cosmetic chores — 'avatar fixed', 'service restarted'. True but worthless; the next session does not need that noise. Do not treat counts as facts. If a handover says 'fixed 47 items', query the live source; counts decay. Do not duplicate what the source of truth already holds — point to it instead. Do not let the handover grow forever; the three-session window keeps it lean. A handover worth remembering: it once carried as the top item that twenty real tests were failing behind a fake 'all-green' placeholder — so the next session knew the risk on day one.
Induction and handover are not paperwork. They are the memory organ of the system — how a machine with no long-term memory still behaves as if it remembers. Without them, Orion arrives each session as a stranger, relearning the tribe and its rules from scratch, undoing careful choices, creating churn. With them, he walks in oriented, knows the locked decisions, sees the open threads, understands the risks — and cleanly re-enters the team. The ritual is the answer to amnesia: not perfect recall, but perfect enough, shaped to how agents actually work.
Induction is just the doorway, not the whole of an agent's memory—the real memory is written down, kept current, and always available. When Orion wakes with amnesia, he doesn't rely on a handover summary that decays; he reads the living record: the architecture, the policies, the cookbooks, the exact prompts that define how each agent decides. That documentation is not a copy—it is the source of truth, updated at its origin every time a choice changes. A handover is useful for flagging what's live and what's risky, but the system's true memory lives in the durable record it keeps of itself. So the real lesson is this: a team with no long-term memory of its own can still behave as if it does, if it documents itself relentlessly and keeps that documentation current.