This file is the complete inventory. It is enforced by
tests/test_integrations.py::test_core_cycle_footprint, which runs a full
init + route cycle under a sandboxed HOME with an audit hook and fails if
anything outside this manifest is opened, or if any socket is created.
You are welcome to verify it yourself with strace.
The only outbound requests this package ever makes are to the license service:
POST https://hologram-license.gman1911-gs.workers.dev/v1/validate, sending
your license key, a salted hash of your machine ID, and the package version —
at activation, then at most once per 24 h; and, on your hologram upgrade,
the download of the new wheel. Your code, file contents, queries, memories
and routing data never leave your machine. There is no telemetry.
Without a license key configured, no network request is made at all.
The bundled hologram-cortex package makes one more, only with the [memory]
extra and only when you run hologram-cortex setup: the download of its
embedding model (see hologram_cortex/THIRD_PARTY_NOTICES.md). Its recall never
goes online.
| Path | What |
|---|---|
<project>/.hologram/ (or .claude/ from older installs) |
pressure state (hologram_state.json), routing history, caches, injection_log.jsonl (one line per prompt: which files were injected), touch_log.jsonl and sessions/ (what each session touched, for the reranker), a .pre-0.5 copy of what the one-time 0.4 migration set aside — per project, yours to delete |
<project>/crg/ |
the project's causal research graph, only after hologram crg init: your nodes, and CURRENT.md/GUARDS.json generated from them |
<project>/.grok/rules/hologram.md |
Grok only: the graph's brief for the next session |
~/.hologram/license.json |
your license key (0600) |
~/.hologram/license_state.json |
cached license verdict (HMAC-sealed) |
~/.hologram/config.json |
integration flags and project_lineage (read-only; you create it) |
~/.hologram/models/ |
T3v4-R reranker weights (pro; not used by 0.5, see the changelog) |
~/.hologram/routing_outcomes.jsonl |
local routing-outcome log (pro learning) |
~/.hologram/init_hints.json |
dedupe timestamps for the one-time "run hologram init" onboarding hint |
~/.hologram/board/ |
the blackboard (board.jsonl: notes sessions on this machine leave for each other) and presence/<session>.json (each session's project, state and last prompt, for the others) |
~/.hologram/injector_fallback.log |
one line when a memory backend fails and the hook falls back |
~/.hologram/install_manifest.json |
what hologram install changed, for hologram uninstall |
~/.hologram/memory/ |
the hologram-cortex store (entries.jsonl, from the first memory stored) and, with the [memory] extra after setup, its vector index and model |
All flags default off. Enable in ~/.hologram/config.json →
{"integrations": {...}} if you run a compatible mesh.
| Flag | Paths | What |
|---|---|---|
cortex |
~/.claude/memory/entries.jsonl (+ lock) |
read/write a cortex-format memory store |
pool |
~/.claude/pool/, ~/.claude/registry/, ~/openclaw-cognitive/src (import) |
multi-instance pool/registry |
mesh |
~/.claude/mesh/ |
local message-bus files (an external relay daemon, not this package, moves them between machines) |
temporal |
~/.claude/temporal/ |
temporal-mcp state sharing |
Editor integration is only written by an explicit hologram install step —
never implicitly on import or first run — and hologram uninstall removes it.
hologram install claude-code makes at most three changes, each printed and
confirmed first:
1. Registers the hologram MCP server (claude mcp add), and hologram-cortex
beside it when the [memory] extra is installed.
2. Adds four hook entries to ~/.claude/settings.json (a timestamped backup
is written first), one per event, all hologram hook <event>:
SessionStart (the project graph's brief), UserPromptSubmit (the
working set of files, memories, the graph's line), PreToolUse (refuses
an edit or command the graph's guards forbid) and Stop (reads the
transcript path Claude Code supplies and reinforces routing for the files
the turn used). All operate on local files only. Skip them with --no-hooks.
3. Adds the Hologram mod (status line, /holo, /guard), which ships inside
the package, to CLAUDE_CODE_PLUGIN_DIRS in the same settings file.
hologram install codex registers the MCP server(s) and adds the same hooks
to ~/.codex/hooks.json (hologram hook codex; Codex asks you to re-trust the
file). hologram install grok writes ~/.grok/hooks/hologram.json and
nothing else (Grok has no MCP registration). gemini registers the MCP
server(s) only; cursor prints config instructions and changes nothing.
hologram uninstall reverses every registration above (--purge also deletes
~/.hologram/, your license key included). Per-project .hologram/ and crg/
are yours to delete. Nothing else exists.
This page is FOOTPRINT.md from the 0.5.0 package, rendered. The package's own test suite checks the core cycle against it.