wrap-recall-hive

Own-pack session continuity for coding agents — plus an opt-in hivemind search for multi-seat crews.

You own your memories. When you want the hive, ask for it. You never confuse the two.

Ritual	Direction	Scope
/wrap	Session → disk	Your pack only (distill judgment)
/recall	Disk → session	Your pack only (~30–50k tokens, not 300k transcript)
/hive	Disk → session	Crew packs + shared house files (labeled not_me)

This repository is a shareable package: agent skills, a stdlib Python hive CLI, pack templates, product laws, and synthetic demos.
It is not a cloud service and not a full IDE.

---

Why it exists

Coding agents are excellent until the context window dies, the human /clears, or a second agent already solved the problem in another session.

Common “memory” products either:

• auto-extract trivia (“user likes TypeScript”) with no scar trails, or
• RAG entire transcripts into a noise soup, or
• melt multi-agent history into one identity (“I shipped that” — but Claude did).

wrap-recall-hive is a different product shape:

1. Explicit distill (/wrap) — you write what the next you needs.
2. Explicit load (/recall) — budgeted own-pack continuity.
3. Explicit crew search (/hive) — opt-in, attributed, never the default preseed.
4. Wrap hygiene — peer evidence lands in ## From the hive, never in own ## Recall.

---

Package contents

wrap-recall-hive/
├── README.md
├── LICENSE · RELATED.md · NOTICE
├── .claude-plugin/marketplace.json   # Claude Code marketplace catalog
├── plugins/wrap-recall-hive/         # Claude plugin (skills + hive CLI)
├── skills/                           # Portable skills (Grok + manual install)
├── hive/                             # CLI + registry.example.json
├── scripts/install.sh · install-grok.sh
├── pack/ · examples/
└── docs/ INSTALL.md · LAWS.md · DESIGN.md · SECURITY.md

---

Quick start

1. Clone

git clone https://github.com/voardwalker-code/wrap-recall-hive.git
cd wrap-recall-hive

(Private repo needs git credentials; local path works too.)

2. Smoke-test hive (synthetic data — no personal packs)

python3 hive/hive.py --registry examples/demo-registry.json --list-owners
python3 hive/hive.py --registry examples/demo-registry.json --focus "rate limit"

You should see labeled spans with owner=demo-a and not_me=true, plus a Hive report.

3. Install for your agent host

Full detail: docs/INSTALL.md.
Law M17 — one surface: skills must appear as plain wrap · recall · hive.
Never install plugin + loose skills on the same host (Grok especially: plugins namespace to wrap-recall-hive:recall).

Grok Build (recommended — plain names)

./scripts/install-grok.sh

→ ~/.grok/skills/{wrap,recall,hive}/ + hive CLI under ~/.local/share/wrap-recall-hive/.
The script removes a Grok wrap-recall-hive plugin if present so you do not get a second, namespaced set.

Do not also run grok plugin install … for daily use.

Claude Code — pick one

Marketplace (distribution; may show namespaced skill ids):

/plugin marketplace add voardwalker-code/wrap-recall-hive
/plugin install wrap-recall-hive@wrap-recall-hive

Or plain user skills (no plugin UI):

./scripts/install.sh --claude

Not both — remove ~/.claude/skills/{wrap,recall,hive} if you use the marketplace plugin.

Both hosts (plain names on each)

./scripts/install.sh
# enough — no extra grok plugin install

4. Create your own pack

mkdir -p ~/.agent-memory/primary/{journal,worklog}
cp pack/relationship-spine.example.md ~/.agent-memory/primary/relationship-spine.md
cp pack/README.md ~/.agent-memory/primary/README.md

Host-native roots also work (~/.grok/memory/, ~/.claude/claude-memory/) — point the skills at what you already use.

5. Optional multi-seat hive

cp ~/.local/share/wrap-recall-hive/hive/registry.example.json \
   ~/.local/share/wrap-recall-hive/hive/registry.json
# edit roots — do not commit personal registry to a public remote
python3 ~/.local/share/wrap-recall-hive/hive/hive.py --list-owners

---

How the three rituals work

/wrap — distill

Write:

1. Journal — ## Recall (own story only) + ## Notes + ## From the hive
2. Worklog — facts + **Hive:** none | focus · owners
3. Spine — only if a durable truth changed (including peer relationship rows)

If you used /hive this session, peer trails must go under ## From the hive so the next /recall never thinks you shipped another agent’s work or owned their faceplant.

/recall — load self

1. Spine
2. Latest own ## Recall sections
3. Worklog tail
4. Budget ~30–50k tokens

Focused /recall <note> searches your pack only. Crew search is not this command.

/hive — load crew (opt-in)

python3 hive/hive.py --focus "whatever stub the human half-remembers"

• Keyword search over registered roots
• Budgeted assembly
• Hard attribution headers
• Audit posture: reason as reviewer of their trail

Why not bake hive into /recall?
House search on every continuity load becomes a noise vacuum (foreign journals, boards, half-hits) and breaks the lean pack that already works. Hive is a weapon you draw on purpose.

---

Identity law (the part that makes multi-agent safe)

Section	Whose story
## Recall + ## Notes	This seat + human
## From the hive	Others (evidence) + optional “what I take”
Spine ## Peer seats (crew)	Durable relationship to peers — from this side only

Visa versa: each seat records the others in its own spine. Nobody cross-writes packs to “stay symmetric.”

---

Product laws (summary)

Full table: docs/LAWS.md.

Highlights:

• Own write · no silent cross-write
• Hive is additive (M15)
• Wrap hive hygiene (M16)
• One surface (M17) — plain wrap / recall / hive; never dual plugin+loose installs
• Secrets never
• Human gates on promote / destructive ops

---

Design notes

See docs/DESIGN.md and docs/SECURITY.md.

Intentional non-goals: vendor lock-in, auto hive on session start, transcript RAG as continuity, companion “life memory” merged into coding packs, code-graph search (use a code indexer for that).

---

Related projects (growing list)

Maintained in RELATED.md.

Project	Role
wrap-recall-hive (this)	Session continuity + hive search for coding agents

Sibling house systems (orchestrator, cognitive substrate, …) get listed when their public/replacement cut is ready — not while rebuilds are private. See RELATED.md for how to add rows later.

---

Privacy (why private first)

Live agent memory packs often contain:

• personal machine paths
• private project names
• relationship notes

This package ships skills, CLI, synthetic demos, and docs only.

Before flipping the GitHub repo to public:

1. Follow docs/SECURITY.md
2. rg -i 'password|api[_-]?key|sk-|@gmail' .
3. Confirm no live packs or personal registry.json committed

---

Requirements

• Python 3.10+ for hive.py (stdlib only — no pip deps)
• An agent host that can load markdown skills (or you run rituals by hand)
• A filesystem (local-first by design)

---

Contributing / using

MIT — see LICENSE.

Please keep:

• examples synthetic
• secrets out of packs
• peer attribution honest

PRs that bake hive into default /recall will be rejected unless the product law is deliberately redesigned.

---

One-line

Distill. Reload. When you need the crew’s filing cabinet, open the hive — labeled, budgeted, never confused with your own mind.