quantumclaw/clawhdf5
3
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Withdraw the ZeroClaw integration claims #10

Merged
osobh merged 2 commits from docs/withdraw-zeroclaw into main 2026-09-25 19:25:18 +00:00
Conversation 0 Commits 2 Files Changed 9
+51 -15
osobh commented 2026-09-25 16:15:23 +00:00
Owner
Copy Link
Copy Source

Summary

This withdraws the ZeroClaw integration claims, following the same check as the OpenClaw one (#9).

The claims were:

  • CLAUDE.md: ZeroClaw "imports this as a Cargo feature (clawhdf5 feature flag)" and uses clawhdf5 as its memory backend.
  • The agent crate called itself the "ZeroClaw agent memory HDF5 backend".
  • clawhdf5-migrate claimed to read "the ZeroClaw layout".

Checked on 2026-09-25 against ZeroClaw v0.8.5 (the latest release), the osobh/zeroclaw fork (also on v0.8.5), and both histories back to February 2026:

  • No clawhdf5 integration has ever existed in ZeroClaw: no feature, dependency or memory backend. ZeroClaw's backends are sqlite, lucid, postgres, qdrant, markdown and none, behind its own Memory trait.
  • The migrator's layout isn't ZeroClaw's. ZeroClaw's SQLite schema is a single memories table. The migrator's memory_chunks, sessions, entities and relations tables never existed in ZeroClaw, so it can't read a ZeroClaw database.

Decision: withdraw the claims. clawhdf5 is a standalone library with no framework integration.

Changes (docs and doc comments only; no behaviour changes)

  • CLAUDE.md: the purpose and integration sections now say there's no framework integration, and a dated note records the check.
  • Agent crate: the doc comment no longer says it's ZeroClaw's backend.
  • ZEROCLAW_VERSION: keeps its name and value, since it's the persisted edgehdf5_version tag. A doc comment says it's unrelated to ZeroClaw.
  • Migrator: its README, CLI help, reader docs and the README migration section describe its table layout as its own, not ZeroClaw's.
  • docs/openclaw.md: no longer calls ZeroClaw the integration target.
  • CHANGELOG: an upgrade note.

Test plan

  • fmt, clippy -D warnings (agent, migrate), 42 migrate tests
  • Gitea CI on this PR

🤖 Generated with Claude Code

## Summary This withdraws the ZeroClaw integration claims, following the same check as the OpenClaw one (#9). The claims were: - **CLAUDE.md:** ZeroClaw "imports this as a Cargo feature (`clawhdf5` feature flag)" and uses clawhdf5 as its memory backend. - **The agent crate** called itself the "ZeroClaw agent memory HDF5 backend". - **`clawhdf5-migrate`** claimed to read "the ZeroClaw layout". Checked on 2026-09-25 against ZeroClaw v0.8.5 (the latest release), the `osobh/zeroclaw` fork (also on v0.8.5), and both histories back to February 2026: - **No clawhdf5 integration has ever existed in ZeroClaw:** no feature, dependency or memory backend. ZeroClaw's backends are `sqlite`, `lucid`, `postgres`, `qdrant`, `markdown` and `none`, behind its own `Memory` trait. - **The migrator's layout isn't ZeroClaw's.** ZeroClaw's SQLite schema is a single `memories` table. The migrator's `memory_chunks`, `sessions`, `entities` and `relations` tables never existed in ZeroClaw, so it can't read a ZeroClaw database. **Decision:** withdraw the claims. clawhdf5 is a standalone library with no framework integration. ### Changes (docs and doc comments only; no behaviour changes) - **CLAUDE.md:** the purpose and integration sections now say there's no framework integration, and a dated note records the check. - **Agent crate:** the doc comment no longer says it's ZeroClaw's backend. - **`ZEROCLAW_VERSION`:** keeps its name and value, since it's the persisted `edgehdf5_version` tag. A doc comment says it's unrelated to ZeroClaw. - **Migrator:** its README, CLI help, reader docs and the README migration section describe its table layout as its own, not ZeroClaw's. - **`docs/openclaw.md`:** no longer calls ZeroClaw the integration target. - **CHANGELOG:** an upgrade note. ## Test plan - [x] fmt, clippy `-D warnings` (agent, migrate), 42 migrate tests - [ ] Gitea CI on this PR 🤖 Generated with [Claude Code](https://claude.com/claude-code)
osobh added 1 commit 2026-09-25 16:15:24 +00:00
docs: withdraw the ZeroClaw integration claims
CI / test-arm64 (pull_request) Successful in 1m5s
Details
CI / test (pull_request) Successful in 5m34s
Details
87d64588e5 
CLAUDE.md said ZeroClaw "imports this as a Cargo feature (clawhdf5
feature flag)" and uses clawhdf5 as its memory backend; the agent crate
called itself the "ZeroClaw agent memory HDF5 backend"; the migrator
claimed to read "the ZeroClaw layout". Checked on 2026-09-25 against
ZeroClaw v0.8.5 (its latest release), the osobh/zeroclaw fork (on
v0.8.5) and both histories back to February 2026:

- no `clawhdf5` feature, dependency or memory backend has ever existed
  in ZeroClaw; its backends are sqlite, lucid, postgres, qdrant,
  markdown and none, behind its own `Memory` trait;
- ZeroClaw's SQLite schema is a single `memories` table (id, key,
  content, category, embedding, created_at, updated_at); the
  migrator's memory_chunks/sessions/entities/relations layout never
  existed in ZeroClaw, so it cannot read a ZeroClaw database.

Decision: withdraw the claims (as with OpenClaw); clawhdf5 is a
standalone library with no framework integration. The migrator's
default layout is documented as its own. ZEROCLAW_VERSION keeps its name
and value (it is the persisted `edgehdf5_version` writer tag) with a
doc comment saying it is unrelated to ZeroClaw.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
osobh added 1 commit 2026-09-25 16:18:16 +00:00
docs: ClawBrainHub is the one verified consumer
CI / test-arm64 (pull_request) Successful in 1m3s
Details
CI / test (pull_request) Successful in 5m10s
Details
dd5b3f6633 
The previous commit said clawhdf5 has no integration at all. ClawBrainHub
(clawverse/clawbrainhub) does use it: cbh-core reads and writes .brain
files through the facade, cbh-scanner uses the facade, and cbh-cli uses
clawhdf5_agent::bm25::BM25Index, all via path dependencies on this repo.
Checked on 2026-09-25 against main: it builds on its pinned toolchain and
its 204 tests pass. CLAUDE.md now records that, and that path
dependencies mean API changes here reach it directly.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
osobh merged commit 75bdb53342 into main 2026-09-25 19:25:18 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
nsobh osobh scottb (Scott B.)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: quantumclaw/clawhdf5#10