using-second-brain

To load persona identity and memory context before answering, you must enforce a named-entity wiki lookup using knowledge_search on specific slugs before responding. This ensures answers are grounded in persona identity and Second-Brain memory by retrieving relevant prior decisions and session-start context.

Context grounding for session startup is the process of anchoring all responses in injected persona context, including identity cards and top wiki hits. It works by reading the injected content at session start and using an engagement gate to surface relevant prior decisions briefly without restating infrastructure.

To check knowledge graph dependencies before edits or renames, call knowledge_neighbors on the target node to identify costly-to-miss edges. This graph edge safety check warns you once about affected dependencies before executing graph-affecting actions like refactors or deletes.

Prompt routing handles conflicts by flagging and resolving discrepancies when built-in auto-memory contradicts the second-brain graph on load-bearing facts. It ensures the persona-first context remains consistent by prioritizing verified wiki retrieval results over conflicting native memory entries.

Yes, you can use episodic_search alongside knowledge_search to surface prior decisions and enhance context grounding. The wiki lookup remains mandatory for named slugs, while episodic memory search provides optional supplementary context retrieval for session-start conversations and specialist routing.

You should mandate a wiki lookup when a user's message names a specific host, service, project, decision, blocker, or wiki page slug. This hard rule requires calling knowledge_search on that literal name before answering to ensure Second-Brain memory context is properly loaded.