Skip to main content
The Substrate group is the pre-action gate. forge substrate composes the rest into one verdict; each stage is also callable on its own. See The pre-action gate for the pipeline.

forge substrate

One pre-action gate: assumptions, route, impact, scope, memory, verify.
If it returns okToProceed:false, ask the returned assumption.questions before editing.

forge preflight

Assumption check — what a task names that the repo doesn’t define.

forge route

Recommend the cheapest capable model for a task.

forge impact

Predict the blast radius for a symbol or file from the atlas graph.

forge scope

Decompose files into independent clusters — plus coupled files you didn’t name.

forge context

Budgeted context assembly + completeness gate — what an edit NEEDS known.
Assembles a budgeted context via set-cover over the predicted edit set, applies a compression ladder, and reports the computed missing set.

forge anchor

Goal-drift check — are your actual (git) changes still on the stated goal?

forge diagnose

Doom-loop check — record a failure; the same signature 3× mints a diagnosis + escalation.

forge imagine

Consequence simulation — predicted breaks + the minimal dry-run test suite for a task.

forge lean

Scope-minimality (M5) — measure the diff’s footprint vs what the task asked for.
The route, impact, scope, context, anchor, and lean stages all run inside forge substrate. Call them individually when you want just one signal.