dodder

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 working on the dodder/madder blob-store 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.

Use when writing or modifying Go code in the dodder repository - enforces project-specific naming, formatting, and structural conventions that differ from standard Go style

Helps contributors work on the dodder Go codebase. Covers the build and test cycle, NATO phonetic module hierarchy, pool management rules, the repool static analyzer, codebase navigation, and critical coding conventions. Activated by requests to work on dodder, add commands or types, register coders, fix dodder code, add NATO modules, manage pools, or explore dodder architecture and development workflows.

Use when adding a new version of a persistent data structure, creating a new blob or config type, implementing an upgrade path between versions, or registering a coder for a versioned type. Also applies when working with type_blobs, blob_store_configs, blob_stores, hyphence, or any package following the *_blobs / *_configs / *_stores naming convention.

Use when working with the hyphence (hyphen-fence) serialization format, adding coders for versioned types, reading or writing typed blobs, or debugging serialization issues. Also applies when encountering

Use when naming packages, directories, type strings, skills, or any identifiers that need structured multi-part names. Also applies when reviewing names for convention compliance or encountering naming inconsistencies involving hyphens and underscores.

Use when working with catgut.String, encountering copy-detection panics, pooling strings, or needing mutable buffer-backed strings. Also applies when seeing noescape, copyCheck, catgut.GetPool, or MakeFromString in code.

Use when working with content-addressable identifiers, markl IDs, blob digests, purpose-tagged hashes, blech32 encoding, or encryption keys. Also applies when encountering markl.Id, MarklId, FormatHash, purpose@digest syntax, or hash format selection.

Use when allocating pooled objects, calling GetWithRepool, handling FuncRepool return values, writing code that borrows from sync.Pool, or encountering repool analyzer warnings. Also applies when adding //repool:owned annotations, debugging pool leaks, or working with CloneTransacted.

Use when working with lazy sequences, SeqError iterators, combining or chaining iterators, or encountering Seq, SeqError, quiter, quiter_seq, MakeSeqErrorFromSeq, Chain, Multiplex, or MergeSeqErrorLeft in code.

Use when creating error sentinels, defining package-specific error types, checking errors by type rather than value, or encountering Typed, IsTyped, MakeTypedSentinel, WrapWithType, or pkgErrDisamb in code.

Use when running concurrent operations with error collection, structuring parallel or serial work with cleanup, or encountering MakeWaitGroupParallel, MakeWaitGroupSerial, DoAfter, or GroupBuilder in code.