無料GitHub で公開

wdbx-roundtrip

Build the abi CLI and drive a full WDBX persistence round-trip on a scratch segment — db init → block insert → query → db verify — proving the on-disk checkpoint + WAL chain stays valid. Use to smoke-test WDBX persistence/durability after touching the store, checkpoint, or WAL code, or to demo the block lifecycle.

日本語の概要は準備中です。原文の説明を表示しています。

donaldfilimon/abiスター 19(GitHub 19 + cccskills 0)

実行スコア未検証

インストール方法を見る

含まれるファイル（2）

SKILL.md3.3 KB
roundtrip.sh2.0 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

WDBX moved out of this repository on 2026-08-22. It now lives in the sibling repo ../wdbx together with abi-compute, abi-foundation, abi-core, and abi-telemetry; abi consumes them by relative path. Source paths below therefore read ../wdbx/crates/.... Run WDBX-only tests from that repo (./tools/cargo.sh test --locked --manifest-path ../wdbx/Cargo.toml --workspace < /dev/null, run from the abi checkout), and abi's gate (./tools/check.sh) from here.

Under the Abbey System Constitution (docs/superpowers/specs/2026-08-22-abbey-system-constitution.md) WDBX is the provenance-aware episodic substrate, not a vector store. Most of the evidence half of its specification is unimplemented; the measured gap list is in docs/superpowers/specs/2026-08-22-wdbx-conformance-gap-analysis.md. Do not describe an episodic capability as Current on the strength of the vector-store features that do exist.

wdbx-roundtrip — drive abi's WDBX persistence lifecycle

Driver: .agents/skills/wdbx-roundtrip/roundtrip.sh (paths relative to repo root). Builds the CLI and runs the four-step store lifecycle against a mktemp scratch v2 base path (created and removed by the driver). Evidence is the RESULT: line. Fully local, no network.

Run (agent path)

.agents/skills/wdbx-roundtrip/roundtrip.sh                          # profile=abi, default metadata
.agents/skills/wdbx-roundtrip/roundtrip.sh aviva '{"note":"hi"}'    # custom profile / metadata JSON

Steps and asserted markers:

wdbx db init <store> → initialized empty WDBX v2
wdbx block insert <store> <profile> <json> → appended block:, blocks=1
wdbx query <store> → "blocks":1
wdbx db verify <store> → v2 verify OK:, merged_chain_valid=true

Prints RESULT: PASS (exit 0) or a FAIL count.

Current Rust driver: proves v2 initialization, a UUID-backed hashed audit block, reopen-visible stats, and successful merged audit-DAG verification.

Gotchas

The scratch store and activated generation live under one mktemp directory and are removed on exit, so the default .abi/ store is never opened.
wdbx query <store> on a freshly-block-inserted segment reports kv_entries:0 vectors:0 blocks:1 — blocks are the append-only content-addressed log; kv and vectors are separate surfaces. mode:cpu_fallback remains honest even when the detected backend label is metal.
For semantic/vector queries (embeddings, personas) use abi wdbx query <store> "<text>" <persona>; the round-trip driver checks the structural path.
For a source-level tour of the HNSW index, MVCC snapshot chain, and WAL, use the wdbx-explorer subagent.

Troubleshooting

Symptom	Fix
`build` FAIL	Check the repository toolchain via `./tools/cargo.sh --version`, then `./tools/check.sh`.
`merged_chain_valid=true` missing	V2 audit-DAG or recovery regression — inspect `../wdbx/crates/abi-wdbx/src/v2/` and `versioned.rs`.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

同じリポジトリのスキル

abbey-system-prompt

無料

Maintain the Abbey / Aviva / Abi Discord system prompts in the Rust abbey-bot (`src/ask.rs`) and keep the hosted Grok bots (Grok Bot Abbey, Aviva Grok) in step with them. Use when the user says "improve grok bots", "abbey prompt", "persona prompt", "ask.rs", "system prompt", "tip floor", asks to change how Abbey/Aviva/Abi speak on Discord, or after an abbey-bot PR merges and the hosted bot's tip floor needs bumping. Runs as /abbey-system-prompt.

日本語の概要は準備中です。原文の説明を表示しています。