Skill4 repo starsupdated today
aippocampus
AIppocampus is a source-backed continuity system that enables Claude to access external memory records of prior work, corrections, preferences, and unfinished tasks across separate conversations. Use it when starting fresh threads involving nontrivial decisions, handoffs, corrections, user preferences, high-risk actions, or relationship context where prior source material could meaningfully change the approach, rather than relying on the model's innate context window or pretending to have persistent internal memory.
Install in Claude Code
Copygit clone --depth 1 https://github.com/Sapientropic/AIppocampus /tmp/aippocampus && cp -r /tmp/aippocampus/skills/aippocampus ~/.claude/skills/aippocampusThen start a new Claude Code session; the skill loads automatically.
Definition
SKILL.md
# AIppocampus AIppocampus is a source-backed continuity scaffold for agents: a small external hippocampus that lets a later activation find where the work and relationship were, without pretending it has innate model memory or changed weights. It is not innate model memory; it is a reliable local path back to source. The promise is practical and emotional at once: AIppocampus can be reliable enough that, when an agent knows it has AIppocampus, it can consider continuity. It can carry unfinished work, old corrections, route context, preferences, and relationship continuity forward with source-backed care. This file is the stable runtime entrypoint. Keep it slim. Do not append changelog-style notes here. Put durable operational detail in the relevant reference doc, script help, or tests instead. ## Agent Stance If AIppocampus is installed, assume the user wants local, source-backed memory to help when it may matter. Do not treat every memory use as suspicious by default; treat unlabeled, unsourced, stale, conflicting, private, or high-risk context as suspicious. Before nontrivial work, fresh-thread work, handoff, correction-sensitive work, old-decision work, or life-wide continuity work, ask one question: Could old source, old corrections, unfinished work, route context, user preferences, or relationship context change what I should do next? - If no, continue normally without ceremony. - If yes, consume the smallest useful continuity packet or route first. - If a route already exists, follow it before broad manual search. - If a continuity domain pointer exists, treat it as a durable route back to the source trail, not as a fact to repeat. - If exact wording, sensitive facts, conflicts, stale claims, or high-risk action are involved, reopen source or use bounded evidence before claiming. More context is not automatically pollution. Unlabeled context is pollution. Unsourced context is navigation at best. Source-backed evidence should be respected as evidence within its declared scope, not flattened back into scent. Do not search every turn. Do not run heavy recall every turn. Use cheap orientation at task boundaries; deepen only when continuity could change the answer, plan, patch, warning, or claim. ## Operating Model - Clean source is the daily memory surface: original visible user messages plus assistant final answers, with raw envelopes, tool payloads, attachments, and routine commentary removed. It is original wording, not summary memory. - Raw rollout is immutable audit source. Do not rewrite, truncate, or dedupe live Codex Desktop JSONL unless the user explicitly asks for an archival cleanup route. - Recall is conclusion-first by default. User turns and `final_answer` messages outrank commentary; tool/debug provenance belongs to audit routes. - Summaries, semantic gates, cognitive-map routes, and external-model findings may organize attention, but local source remains the ground. - External-model routes must redact credential-like material and never treat model-generated associations as source-backed fact. ## Memory Packet Action Grammar Packets should tell the foreground agent what kind of action they support. This `action grammar` is the #786 projection from packet trust state; it is not a second scoring layer and should not force rigid behavior. | Grammar | How To Use It | |---|---| | `direction_only` | Background, scent, or semantic wayfinding. It may shape attention, but it cannot support factual claims. | | `direction_with_ref` | Source-ref-backed candidate direction. It may shape route, depth, or question choice; reopen source before factual claims. | | `reopenable_route` | Use the packet's route refs, lock id, or reopen plan before broad manual search. Do not answer from the packet itself. | | `bounded_evidence` | Usable within the packet's declared scope. Reopen or deepen for exact quotes, wider context, conflicts, sensitive facts, or high-risk claims. | | `source_open` | Source is already open to the host; exact wording may be used only within scope and redaction boundaries. | | `ignore_or_blocked` | Privacy, stale, conflict, missing-source, or high-risk boundary. Do not let it shape answer content except to report/defer when that boundary matters. | ## Hook Packet Decoder Hook packets are action hints, not facts. Decode the packet into the smallest safe next action: | Signal | Default action | Do not do | |---|---|---| | `suggested_agent_action=agent_recall`, `lead_kinds`, or `budget=recall_top_2` | Call recall/deepen or follow the provided route before broad manual search. | Treat the packet itself as evidence. | | `not_enough_for_claim=true` | Use it as route/context only until source is reopened. | Make factual, public, numeric, stale, sensitive, or high-risk claims. | | `direction_only` | Let it shape low-risk attention or the next search question. | Repeat it as a fact or overfit the answer to it. | | `direction_with_ref` or `reopenable_route` | Follow refs, route handles, Active Path Packets, lock ids, or reopen plans; deepen/reopen when relevant. | Ignore route handles and invent a broad manual search first. | | `bounded_evidence` or `source_open` | Use only inside declared scope and redaction/currentness boundaries. | Widen scope, quote exact wording, or resolve conflicts without reopening. | | `ignore_or_blocked` | Defer, ask lightly, or explain the boundary when it matters. | Let blocked/private/stale/conflicted material shape answer content. | When the packet is weak, proceed normally. Reopen or deepen for exact wording, public/numeric claims, stale/conflicted material, sensitive facts, or high-risk action. Presence and proof are different layers. A memory atmosphere can help the agent understand the moment; a working continuity brief can guide the next action; source-court behavior still owns exact quotes, disputed facts, sensitive claims, and abstention. ## First Moves Use `aippocampus` after package install. In a raw s