Skip to main content

Overview

The bd mol seed command verifies that formulas are accessible and can be cooked (instantiated). This is useful for verifying system health before patrols or agents attempt to spawn work.

Usage

Arguments

  • [formula-name] - Optional formula name to verify. Required unless using --patrol flag.

Options

  • --patrol - Verify all patrol formulas (mol-deacon-patrol, mol-witness-patrol, mol-refinery-patrol)
  • --var key=value - Variable substitution for condition filtering (can be specified multiple times)
  • --json - Output results in JSON format

Formula Search Paths

Formulas are searched in the following order:
  1. .beads/formulas/ (project level)
  2. ~/.beads/formulas/ (user level)
  3. $GT_ROOT/.beads/formulas/ (orchestrator level, if GT_ROOT is set)

What Gets Verified

The seed command checks that:
  1. Formula exists in the search path
  2. Formula syntax is valid
  3. Formula can be resolved (including extends/inheritance)
  4. Formula can be cooked to a subgraph structure

Examples

Verify Patrol Formulas

Before starting automated patrols, verify all patrol formulas are accessible:
Output:

Verify Specific Formula

Check if a custom formula can be used:
Output:

Verify with Variables

Test formula with specific variable values for condition filtering:

JSON Output

With --json flag:
For patrol verification:

Use Cases

Pre-Flight Checks

Use in CI/CD pipelines or agent startup scripts to verify formulas are available:

Development Workflow

When developing new formulas, verify they can be loaded before attempting to use them:

Debugging Formula Issues

If a formula fails to instantiate, use seed to isolate whether the issue is:
  • Formula not found (check search paths)
  • Invalid syntax (JSON parsing error)
  • Resolution failure (extends chain broken)
  • Cooking failure (invalid step structure)

Exit Codes

  • 0 - Formula(s) successfully verified
  • 1 - Formula not found, invalid syntax, or verification failed