gluon plan

gluon plan compiles intent, component discovery, and compositions into an immutable execution DAG.

Usage

gluon plan \
  --intent intent.yaml \
  --output plan.json

When the intent declares compositions.sources, plan resolves those sources automatically and writes <intent-dir>/.gluon/compositions.lock.yaml.

Common examples

Generate a JSON plan:

gluon plan -i examples/intent.yaml -o plan.json

Generate YAML instead:

gluon plan -i examples/intent.yaml -o plan.yaml -f yaml

Filter to one environment:

gluon plan -i examples/intent.yaml --env staging

Preview the dependency graph while compiling:

gluon plan -i examples/intent.yaml --view dag

Focus on changed components:

gluon plan -i examples/intent.yaml --changed --base main

Flags

Flag	Meaning
--intent, -i	Intent file path
--output, -o	Output plan path
--format, -f	Output format: json or yaml
--debug	Enable debug logging during planning
--env, -e	Restrict compilation to one environment
--view, -v	Render a view such as dag, dependencies, or component=<name>
--changed	Enable change-aware filtering
--base	Base git ref for change detection
--head	Head git ref for change detection
--files	Explicit changed-file list
--uncommitted	Scope to uncommitted changes
--untracked	Scope to untracked files

Output contract

The generated plan contains explicit jobs, dependency edges, step phases, labels, and runtime metadata. Read plan schema for the full structure.

Use --config-dir only when you need to load legacy folder-shaped compositions instead of intent-declared packages.