Multi-Module Project

DUUMBI supports multi-module projects where each module has its own graph and can import functions from other modules.

Creating modules

Start with a project:

duumbi init myapp
cd myapp

Create a new module:

duumbi add "create a module called 'math_ops' with functions: abs(x: i64) -> i64, max(a: i64, b: i64) -> i64"

This creates .duumbi/graph/math_ops.jsonld alongside your main.jsonld.

Module structure

Each module is a separate .jsonld file in .duumbi/graph/:

.duumbi/
  graph/
    main.jsonld       # Entry point
    math_ops.jsonld   # Your math module
  config.toml

Cross-module calls

Reference functions from other modules using their full ID:

duumbi add "modify main to call math_ops/abs(-7) and print the result"

The AI generates a Call op with the cross-module reference duumbi:math_ops/abs.

Using stdlib modules

DUUMBI includes standard library modules, available as @duumbi/stdlib-math:

config.toml

[dependencies]
"@duumbi/stdlib-math" = "1.0"

Install dependencies:

duumbi deps install

Use stdlib functions in your program:

duumbi add "call stdlib-math/max(10, 20) and print the result"

Building multi-module programs

duumbi build automatically compiles all modules and links them:

duumbi build
./output

The compiler resolves cross-module references following the priority chain:

1. Workspace — .duumbi/graph/ (your own modules)
2. Vendor — .duumbi/vendor/ (pinned copies)
3. Cache — .duumbi/cache/ (downloaded from registry)

Dependency management

# Add a dependency
duumbi deps add @duumbi/stdlib-math

# List dependencies
duumbi deps list

# Show dependency tree
duumbi deps tree

# Audit lockfile integrity
duumbi deps audit

Next steps

• Use the intent system to generate entire multi-module programs from a description
• Learn about the module registry for publishing and sharing modules