Menü
Use when working on the dodder/madder blob-store internals
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | features-madder_blob_stores |
| description | Use when working on the dodder/madder blob-store internals --- blob store ID parsing, the two-phase `MakeBlobStores()` discovery, config interfaces and the `ConfigKeyValues` key-value system, `info-repo` key resolution, archive vs loose blob initialization, or writing BATS tests that create / share / query blob stores. |
User-facing CLI behavior (commands, ID prefixes, encryption flag values) lives in the plugin copy of this skill. This file covers the implementation: source locations, init phases, config interfaces, and the BATS testing patterns the dodder/madder bats suite uses.
A blob store ID has an optional location prefix followed by a name. The prefix determines where on the filesystem the store lives.
| Prefix | Location | Filesystem root | Example |
|---|---|---|---|
| (none) | XDG user | $XDG_DATA_HOME/madder/blob_stores/ | shared |
. | CWD-scoped | $PWD/.madder/local/share/blob_stores/ | .default |
/ | XDG system | system data dir | /system |
~ | (compat) | same as unprefixed | ~default |
Key behavior: Unprefixed IDs default to LocationTypeXDGUser. The .
prefix creates CWD-scoped stores that live inside the repo directory. Two
IDs with the same name but different prefixes (e.g., default vs
.default) are different stores at different filesystem paths.
Source: go/internal/bravo/blob_store_id/ --- Id struct with
location + id fields, Set() parses prefix, String() omits prefix
for XDG user.
When -repo_id . is active (which remaps XDG dirs under .dodder/ in
CWD), MakeBlobStores() performs a two-phase discovery:
CloneWithoutOverride() (reads real XDG env vars).This is how cross-repo blob sharing works: a user-scoped store (e.g.,
shared) is visible to any repo that shares the same XDG environment,
regardless of whether those repos use -repo_id ..
Source: go/internal/india/blob_stores/main.go:75-95.
| Type string | Config struct | Description |
|---|---|---|
local | TomlV0, TomlV2 | Hash-bucketed local filesystem storage |
local-inventory-archive | TomlInventoryArchiveV0/V1/V2 | Packed archive format with optional delta compression |
| (sftp) | TomlSFTPV0, TomlSFTPViaSSHConfigV0 | Remote SFTP storage |
| (pointer) | TomlPointerV0 | Indirection to another store's config |
The default store type. Blobs stored as individual files in hash-bucketed
directories (e.g., blake2b256/3k/j7xgch6...). Configurable hash buckets
(default [2] = 2-char directory prefix), compression (default zstd),
encryption, and file locking.
Packs loose blobs into archive files with an index for fast lookup.
Requires a loose blob store for unpacked blobs --- either embedded
(created automatically under blobs/ subdirectory) or referenced via
loose-blob-store-id. Supports delta compression (bsdiff algorithm),
configurable max pack size, and independent encryption settings.
Two-pass initialization: MakeBlobStores() initializes non-archive
stores first, then archives, because archives may reference other stores
via loose-blob-store-id.
blob_store_configs.ConfigKeyValues(config) returns a map[string]string
of queryable keys. Available keys depend on which interfaces the config
implements:
blob-store-typehash_type-id, supports-multi-hashencryption, compression-typehash_buckets, lock-internal-filesloose-blob-store-id, max-pack-sizedelta.enabled, delta.algorithm,
delta.min-blob-size, delta.max-blob-size, delta.size-ratiohost, port, user, private-key-path,
remote-pathConfigKeyNames(config) returns sorted key names. Both are used by
info-repo for dynamic key lookup.
Source: go/internal/golf/blob_store_configs/key_values.go.
info-repo handles keys in two layers:
config-immutable,
config-path, dir-blob_stores, xdg.ConfigKeyValues): All other keys are looked
up in the config's key-value map. Unknown keys produce an error
listing available keys.With 0 args: defaults to config-immutable on the default store. With 1
arg: key on default store. With 2 args: store ID + key. With 3+ args:
store ID + multiple keys.
The -encryption flag (shared via setEncryptionFlagDefinition) accepts
none, generate (or empty), a file path, or a key string. Used by
blob_store-init, blob_store-init-inventory-archive, and repo init.
To share blobs across repos in tests (e.g., for import tests):
setup() {
load "$(dirname "$BATS_TEST_FILE")/common.bash"
export output
set_xdg "$BATS_TEST_TMPDIR"
# Create user-scoped store (unprefixed = XDG user location)
run_dodder blob_store-init shared
assert_success
# Init repo using the shared store
run_dodder init \
-yin <(cat_yin) -yang <(cat_yang) \
-lock-internal-files=false \
-repo_id . \
-encryption none \
-blob_store-id shared \
test
assert_success
}
set_xdg ensures both the outer and inner repos share the same XDG
namespace. The unprefixed shared ID resolves via XDG env vars, making
the store visible to any repo initialized with the same XDG environment.
run_dodder blob_store-info-repo compression-type
assert_output 'zstd'
# Query a specific store
run_dodder blob_store-info-repo .archive encryption
assert_output --regexp '.+'
run_dodder blob_store-init-inventory-archive -encryption generate .archive
run_dodder blob_store-write .archive <(echo content)
run_dodder blob_store-pack .archive
| Concern | Package |
|---|---|
| Blob store ID parsing | go/internal/bravo/blob_store_id/ |
| Config interfaces & key-value system | go/internal/golf/blob_store_configs/ |
| Store factory & initialization | go/internal/india/blob_stores/ |
| Directory layout & paths | go/internal/echo/directory_layout/ |
| CLI commands | go/internal/lima/commands_madder/ |
| Command components (flags, env) | go/internal/kilo/command_components_madder/ |
| BATS tests | zz-tests_bats/blob_store_*.bats, zz-tests_bats/info_repo.bats |
Guides day-to-day dodder and der operations including creating zettels, querying and filtering objects, checking out working copies, organizing content, syncing with remotes, and managing tags, types, and dormant objects. Activated by requests to create, edit, organize, query, show, checkout, checkin, push, pull, sync, tag, or otherwise operate on dodder repositories.
Use when working with object genres, adding genre filters to queries, parsing sigils like :z :t :e :k :b, or modifying genre-based dispatch. Also applies when encountering Genre byte type, genre bitwise operations, MakeGenre, or optimizedQueries maps.
Introduces dodder, a distributed zettelkasten and content-addressable blob store. Covers core concepts (zettels, object IDs, tags, types, blobs, the store), installation via Nix, a first-steps walkthrough including repository initialization and zettel creation, and the mental model for working with dodder. Activated when a user is new to dodder, asks what dodder is, wants to get started, install, set up, or learn how dodder works.
Use when working on the ZettelId internals
Use when creating, querying, or sharing dodder blob stores at the command line
Use when interacting with dodder ZettelIds (two-part IDs like `ceroplastes/midtown`), seeding a new repo via `dodder init -yin` / `-yang`, choosing predictable or random ID allocation, or interpreting "zettel ids exhausted" errors at the command line.