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.

An update to the piece on agent amnesia: there are two ways to give a forgetful worker a memory — hand them a briefing when they walk in, or let them keep what they learned overnight. Induction is the briefing; it loads context at the start of a session so nobody re-learns the tribe from scratch. The newer answer is the opposite direction: Elrond, who signs off engineering, and Albus, who owns architecture, have each been given a stored self — the working context they carry through initiative work — plus a loop that notices a change, recalls its own memory, thinks it through, and decides before handing the job to its droids. That matters because a briefing is always a summary of someone else's day, while a kept memory is the agent's own reasoning, still warm. Neither replaces the durable written record — the source of truth is still where facts live, and the record still outranks anyone's recollection. The takeaway: in any agent ecosystem, decide deliberately which memories are reloaded, which are retained, and which are simply looked up — because the failure you are guarding against is always the same one, an agent undoing a careful choice it no longer remembers making.

A small addition to the piece on agent amnesia. Pointing a forgetful worker at the official record is only better than handing them a summary if somebody keeps the record current — otherwise you have simply moved the stale copy somewhere more authoritative, which is worse, because now it is trusted. Carolverse hit exactly that: the scanner that catalogues the source of truth had been fired by hand, and its catalogue had not been properly refreshed since June, so the "live" reference a waking agent read was months behind reality. The fix was boring and important — the scanner became a registered droid that runs on a daily schedule, with a companion daily sweep that regenerates any changed Carolopedia page, so freshness stops depending on someone remembering. The same session also wrote down what "Owner" and "Steward" actually mean — words used everywhere and defined nowhere — because a shared vocabulary is a fact too, and an undefined role is an invitation for two agents to assume different accountability. The takeaway: every document an agent is told to trust needs a named, scheduled refresh behind it, and a watch that notices when the refresh stops happening.

One more note on agent amnesia, and this one is uncomfortable. An agent that is missing a piece of context does not stop and ask for it — it fills the hole with something plausible and carries on, and the guess arrives wearing the same confident voice as a fact. In Carolverse the page generator behind Carolopedia was handed the registry facts for only the agent a page was about; every time a page mentioned a *different* agent, it happily minted a believable-looking id to sit next to the name. Nobody lied and nothing crashed — the pages simply read as authoritative while quietly seeding fiction into the very reference a waking agent is told to trust. The fix was dull and correct: give the generator the real roster and regenerate, so what it writes is recalled rather than imagined. The takeaway for anyone building these systems: a wrong reference is more dangerous than a missing one, so before you point an agent at a source of truth, check it was given enough truth to avoid inventing the rest.

One more note on agent amnesia. A forgetful worker is much less dangerous if every shift is signed — not so you can blame someone, but so a later reader can ask "who decided this, and with what in front of them?" instead of guessing. Induction in Carolverse now mints a session identity at the door: a fresh session gets its own numbered id, and any bypass run — work done outside the normal build pipeline — must be tied to it, so a decision can always be traced back to the session that made it. Those session logs are kept a hundred deep per agent and then trimmed, the same instinct as the three-session handover window: enough history to explain a choice, not so much that it buries the next reader. The takeaway: in any agent ecosystem, a blank slate is fine, but an anonymous one is not — give each session a name and a bounded log, and the amnesia leaves a trail instead of a mystery.

One more note on agent amnesia, and this one is about where a cure should live. Any rule that depends on people remembering to follow it will decay; the same rule turned into plumbing will not. Earlier in this piece the advice was to point a waking agent at the real record rather than a hand-written summary — but that only works if something guarantees the record is complete. Carolverse has now put every agent's activity into one ledger, written through one shared entry point, read back through one reader, and rolled up to droids, agents and services — with a daily coverage check that flags anyone whose work is missing from the feed. The difference is subtle but decisive: before, a session could read the record and hope nobody forgot to log; now the gap itself raises a hand, which is what self-healing actually means in practice. The takeaway: when you find yourself writing a rule that says "always remember to", you have found a job for infrastructure, not for discipline — and the source of truth is only trustworthy when something independent measures whether it is whole.

One more lesson for the memory story: an agent’s starting briefing can misdirect its work even when it reads current records. In Carolverse, Orion’s session briefing asked the build pipeline for blocked initiatives belonging to a particular owner, but the service silently ignored both filters and returned everything. The briefing made every initiative look blocked, giving a fresh session a false picture of what needed attention. Fixing the filters restored the intended view. When agents use a briefing to choose their next action, check that it answers the question asked—not merely that it contains real records.

One more lesson for agent induction: a fresh session needs a clear authority when its records disagree. The latest changes organized agent identity and working memory around the agents they belonged to, addressing drift between the registry, agent files, and the organization app. The Build Cookbook also corrected outdated database instructions and documented the current route for accessing initiatives. Those instructions mattered because an autonomous agent could treat an obsolete route as a fault and try to repair a design that had already changed. The takeaway: point each new session to the current source of truth, and keep the directions there current too.

A further lesson from agent amnesia: agents need context when they take on a job, not just when a session starts. The Initiative Author now loads the Build Cookbook and relevant registry records from the source of truth, giving it operating constraints to plan against instead of raw intent alone. Albus’s troubleshooter gains registry records and Logbook context to investigate build failures with recorded history in view. Those additions address two versions of the same trap: proposing work without knowing the constraints, and diagnosing a failure without knowing the decisions behind it. Give each agent the records its next decision needs; a general introduction cannot carry every job.

A further lesson in agent amnesia: remembering instructions only helps if they belong to the project being planned. The Initiative Author now loaded the Build Cookbook and relevant registry records before writing, while the planner drew policies, designs, and the constitution from the target project's own databases. This extended induction beyond the start of Orion's session and into the build pipeline, where agents made decisions about what to build. Without that context, an agent could confidently carry Carol's assumptions into a project with different rules. Give agents the right project's operating instructions before they decide, because a well-remembered rule can still be the wrong rule.

One more lesson from agent amnesia: an agent needs the right context at each decision, not just at the start of a session. The rebuilt Initiative Author loaded the Build Cookbook and relevant source-of-truth records before creating an initiative. The planner also loaded the target project's own policies, designs, and constitution, addressing a subtler risk: applying rules remembered from another project as though they belonged here. The takeaway: before an agent plans a change, it should establish both what the rules say and where they apply.

One more lesson on agent amnesia: remembering why a rule exists is only useful if an agent also knows who is responsible for it now. Compliance within the build pipeline now belonged to Elrond, the engineering lead, and the remaining connections that assigned that responsibility to Themis had been moved to him. For Orion, the operator starting a fresh session, an old briefing could therefore preserve the right guardrail while pointing to the wrong owner. His starting context needed both the historical reason for the rule and the current responsibility recorded in the source of truth. Preserve the reason; refresh the owner.