Documentation
¶
Overview ¶
Package molecules handles loading template molecules from molecules.jsonl catalogs.
Template molecules are read-only issue templates that can be instantiated as work items. They live in a separate molecules.jsonl file, distinct from work items in issues.jsonl.
Hierarchical Loading ¶
Molecules are loaded from multiple locations in priority order (later overrides earlier):
- Built-in molecules (shipped with bd binary)
- Town-level: $GT_ROOT/.beads/molecules.jsonl (if orchestrator detected via GT_ROOT)
- User-level: ~/.beads/molecules.jsonl
- Project-level: .beads/molecules.jsonl in the current project
Key Properties ¶
- Templates are marked with is_template: true
- Templates are read-only (mutations are rejected)
- bd list excludes templates by default
- bd molecule list shows the catalog
Index ¶
Constants ¶
View Source
const MoleculeFileName = "molecules.jsonl"
MoleculeFileName is the canonical name for molecule catalog files.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type LoadResult ¶
type LoadResult struct {
Loaded int // Number of molecules successfully loaded
Skipped int // Number of molecules skipped (already exist or errors)
Sources []string // Paths that were loaded from
BuiltinCount int // Number of built-in molecules loaded
}
LoadResult contains statistics about the molecule loading operation.
type Loader ¶
type Loader struct {
// contains filtered or unexported fields
}
Loader handles loading molecule catalogs from hierarchical locations.
Source Files
Click to show internal directories.
Click to hide internal directories.