https://jq1.io/tags/scope-invariant/ Recent content in scope-invariant on jq1.io Hugo -- gohugo.io en Sat, 05 Sep 2026 10:00:56 -0600 https://jq1.io/posts/moar_semantic_toolchain/ Sat, 05 Sep 2026 10:00:56 -0600 https://jq1.io/posts/moar_semantic_toolchain/ What’s better than 5 semantic outputs? 5 MOAR semantic outputs! The first 5 outputs in the compiler semantic toolchain enabled engineers to have reachability, diagnostics, provenance, policy diff, and equivalence. That answered “what did the compiler decide?” and “did my refactor break anything?”. Now the toolchain extends to 10 semantic outputs total, answering “prove my invariants hold,” “how big is this change operationally,” “what does my network look like from one VPC’s perspective,” “is my policy carrying dead weight,” and “show me the topology. https://jq1.io/posts/topology_compiler_semantic_toolchain/ Sun, 30 Aug 2026 14:09:21 -0600 https://jq1.io/posts/topology_compiler_semantic_toolchain/ Previously, the routing policy language gave cloud network engineers a way to express topology intent through four algebraic primitives. Declare deny > allow > segments > default, run terraform plan, and the compiler emits the correct route set. The algebra and its mental model should simplify cloud network topology. And it does. But correctness by construction answers “is this valid?” It doesn’t answer “is this what I meant?” A policy can be structurally correct and semantically wrong. https://jq1.io/posts/routing_policy_language/ Mon, 17 Aug 2026 17:15:26 -0600 https://jq1.io/posts/routing_policy_language/ Compiling Cloud Network Topology I think cloud network engineers should take a serious look at the compilation approach given the routing policy language fell out of the architecture naturally. What started as a functional route generator evolved into something with algebraic properties and those properties change what’s possible. From Aggregates to Identity Previous versions of the system built full meshes from VPC aggregate semantics. You’d collect all VPCs, compute the cartesian product of route tables and CIDRs, and emit every possible route. https://jq1.io/posts/white_paper/ Fri, 12 Dec 2025 08:23:23 -0700 https://jq1.io/posts/white_paper/ What began as a modular Terraform experiment evolved into a full compiler-style architecture for AWS networking. The system transforms a declarative map of VPCs into complete multi-region Transit Gateway mesh configurations, performing automatic adjacency synthesis, route expansion, and deterministic cross-region propagation. Below is the white paper that documents the underlying model, a provable O(N² + V²) → O(N + V) reduction alongside empirical validation across multi-region deployments and is currently a work in progress.