Rgctl on Shaaf's blog

Enforcing Architecture with rgctl Policy Checks

Wed, 09 Sep 2026 00:00:00 +0000

Enforcing Architecture with rgctl Policy Checks

rgctl (Reachability Graph Control) indexes a codebase into a compact knowledge graph – functions, classes, calls, inheritance, communities – and serves deterministic, structured answers to questions about architecture, impact, and data flow. You run rgctl discover . once, and every subsequent query (blast-radius, metrics, gql) returns sub-millisecond results from the persisted graph. Agents and humans get the same exact facts. No re-reading source files, no confident guesses, no context window gymnastics.

Introducing rgctl: A Code Knowledge Graph for Engineering Teams and Agents

Mon, 07 Sep 2026 00:00:00 +0000

Introducing rgctl: A Code Knowledge Graph for Engineering Teams and Agents

Modern codebases are too large to hold in your head. They are also too large for most LLM context windows. When a coding agent needs to answer “what breaks if I change this function?” on a repository with 50,000 functions, its options are limited: grep through files, read a handful of them, and produce a confident answer that may be structurally wrong.

I Created a Code Graph of Magento 2 for AI Agents

Thu, 03 Sep 2026 00:00:00 +0000

I Created a Code Graph of Magento 2 for AI Agents

Reachability Graph Control (rgctl) indexes a repository once into a compact graph — functions, classes, calls, inheritance, communities — then serves deterministic JSON queries. Agents get structural facts without loading 25,000 PHP files into context.

I wanted to know whether rgctl could give a coding agent the same kind of map I wish I had on day one of a Magento engagement: where modules live, what calls what, which neighborhoods cluster together, and what breaks if I touch a service class — without pretending the framework’s dependency injection container is fully visible to static analysis.

Blast Radius for Agent-Assisted Development on Kubernetes

Wed, 02 Sep 2026 00:00:00 +0000

Blast Radius for Agent-Assisted Development on Kubernetes

Reachability Graph Control (rgctl) - AI coding agents default to reading files sequentially. That burns context, misses structure, and produces confident wrong answers about impact and dependencies. rgctl indexes the whole repository once into a rich graph with pre-computed reachability, then serves compact, deterministic query results — so agents (and humans) get the right slice of the codebase without loading it into the prompt.

Decomposing a Monolith into Microservices with Call Graph Analysis

Tue, 01 Sep 2026 00:00:00 +0000

Decomposing a Monolith into Microservices with Call Graph Analysis

Splitting a monolith into microservices is a problem of finding boundaries. The wrong boundaries produce distributed monoliths – microservices that cannot be deployed independently because they call each other synchronously for every operation. The right boundaries follow natural seams in the code: clusters of functions that are tightly coupled internally but loosely connected to the rest of the system. This post picks up the CoolStore monolith from migrating it to Quarkus with rgctl and applies the same graph analysis to the next question: where to cut it into services.

Application Migration using A Graph-Driven Approach with rgctl

Mon, 31 Aug 2026 00:00:00 +0000

Application Migration using A Graph-Driven Approach with rgctl

Migrating an application takes a lot of time and energy, which itself is on a collision course with complexity in codebases. Leaving aside the discussion on people and process. In this blog post I would like to highlight the journey of migration and using a tool like Reachability Graph Control - rgctl which understands the codebase. Although I have taken an example of Java, the tool supports multiple languages like C, C#, Go, Node etc.