Skip to content
Forgecroft Docs

What to Do Next

You have a verdict on a real diff. The next moves make those verdicts richer, stricter, and present everywhere a change is made.

Seed your system map for richer blast-radius

Section titled “Seed your system map for richer blast-radius”

First verdicts are instant, but until your system map is seeded the gate reports an honest empty blast-radius (import_graph_not_built / no_components_resolved_for_diff) — Controls still match and gate, but the change is not yet placed in your real code structure.

Seed it to get blast-radius that reflects your import graph:

  1. Derive — walk your source tree locally to produce a seed_proposals.json artifact. The derivation runs client-side with no LLM and no network; your source never leaves your environment.
  2. Import — submit the artifact via POST /proposals/import with a codebases:write-scoped key.
  3. Approve — review and approve the pending proposals in the console. Once applied, the gate’s blast-radius reflects your real graph.

Seeding guide →

Move from warn to block

Section titled “Move from warn to block”

If you started in mode = warn, the gate reports verdicts without failing the build. Once you have watched a few pull requests and trust the verdicts, set mode = block in .forgecroft so a no_go actually stops a merge.

A no_go means the change violates a Control. The right response is to produce a different change — or, if the violation is genuinely warranted, request a time-bound Exception with a recorded reason.

CI Gate semantics →

Wire the gate into your coding agents

Section titled “Wire the gate into your coding agents”

The same forgecroft_evaluate call runs inside Claude Code, Codex, or Cursor through the Forgecroft MCP server. The agent evaluates its own diff mid-loop, before pushing, and self-corrects on each fix_hint — so most no_go changes never reach a pull request.

Coding Agents →

Understand the model behind the verdict

Section titled “Understand the model behind the verdict”

Every verdict comes from traversing your graph of Systems, Components, and Controls — no model on the read path. Reading the model makes the coverage notes and blast-radius legible.

Automate beyond CI

Section titled “Automate beyond CI”
  • CLI — run evaluations and manage the gate from the command line
  • Go SDK — build integrations against the Forgecroft API
  • API Reference — the full endpoint surface