Engineering intelligence

Practical answers for teams that need software to explain itself.

Product tutorials, release notes, and evidence-led field guides to code ownership, AI review, software graphs, and safer change.

32 articles · 4 categories

A luminous engineering graph connecting repositories, people, pull requests, and files

Engineering Intelligence·Featured · August 31, 2026 · 4 min

What Is Engineering Intelligence? A Practical Guide

Engineering intelligence turns repository history into evidence about ownership, risk, architecture, and how software actually changes.

Browse the field notes

Find the question you need answered.

32 articles

  1. Evidence trails connecting MCP transport confinement merges to session-boundary ownership

    Engineering Intelligence·5 min

    Everyone's talking OpenAPI SSRF. Helix's window lights session/transport confinement instead.

    CVE-2026-59973 is FrontMCP's OpenAPI SSRF story. Helix's last-8 tip is session/transport confinement (SSE, DNS-rebinding), not that advisory mashed into #525.

  2. Evidence trails connecting DNS allow-list fence merges to sandbox ownership

    Engineering Intelligence·4 min

    Claude Fable sold the long-horizon agent. Helix's change center is the DNS fence that refuses loopback.

    Anthropic's Fable week is long-horizon agents. Helix on sandbox-runtime lights #522 DNS fence (loopback/private), not release #528; dannycochran owns src/sandbox.

  3. Evidence trails connecting context compression merges to multi-agent ownership silos

    Engineering Intelligence·5 min

    Hermes opened Bot Mode. Helix's couples lit the context compressor instead.

    Pantheon / Bot Mode shipped Hermes Agent v2026.8.31. Helix indexed 9 PRs; every couple runs through the context compression loop one person owns.

  4. Evidence trails connecting desktop cloud-session coverage to hub identity pull requests

    Engineering Intelligence·4 min

    Cline migrated ~11M users to a new harness. Helix tip is cloud-session UX coverage.

    Cline's Sep 2 harness migration blog is Layer A. Helix indexed 39 PRs and tips cloud-session UX coverage, with johnwschoi and abeatrix owning different silos.

  5. Evidence trails connecting URI validation pull requests to public host-confusion advisories

    Engineering Intelligence·3 min

    fast-uri shipped host-confusion CVEs. Helix indexed the IPv6 validation tip.

    Public advisories fixed host confusion in fastify/fast-uri. Helix indexed 45 PRs and shows the tip as URI hardening (#213, #215, #216), not a CVE node.

  6. Evidence trails connecting gateway security documentation to the pull requests that moved them

    Engineering Intelligence·4 min

    OpenClaw 2.0 said the gateway is the trust domain. The graph is the security docs.

    We indexed the latest 44 merged PRs on openclaw/openclaw with Helix. The change center isn’t the sandbox. It’s gateway security docs and the install-policy scan.

  7. Evidence trails connecting render-service merges to outbound URL hardening ownership

    Engineering Intelligence·4 min

    OpenMAIC closed a critical SSRF advisory today. Helix lit up render-service first.

    OpenMAIC patched critical SSRF (GHSA-9m7h-vh2h-rc3w). Helix indexed 32 PRs and lights up render-service first, with one-author security silos beside that firehose.

  8. A repository map with file clusters connected to recent authors and reviewers

    Product Tutorials·3 min

    How to Build a Code Ownership Map from GitHub History

    Build an evidence-based code ownership map from merged pull requests, reviews, paths, and recency, without treating CODEOWNERS as ground truth.

  9. A luminous engineering graph connecting repositories, people, pull requests, and files

    Engineering Intelligence·4 min

    What Is Engineering Intelligence? A Practical Guide

    Engineering intelligence turns repository history into evidence about ownership, risk, architecture, and how software actually changes.

  10. A software graph with one overloaded ownership node and several paths for knowledge sharing

    Product Tutorials·3 min

    How to Find Bus-Factor Risk in a Repository

    Find concentrated code knowledge with repository evidence, then reduce bus-factor risk through review rotation, pairing, and focused documentation.

  11. A pull request node sending risk signals through coupled code and ownership boundaries

    Product Tutorials·3 min

    How to Calculate Pull Request Blast Radius Before Merge

    Estimate pull request blast radius with changed paths, historical coupling, ownership boundaries, churn, and review evidence before you merge.

  12. An evidence panel connecting a pull request verdict to files, reviewers, and repository history

    Product Updates·3 min

    Helix Review: AI Code Review Grounded in Engineering Evidence

    Helix Review evaluates pull requests against repository history, showing blast radius, reviewer evidence, and a transparent merge recommendation.

  13. A shared engineering workspace connecting team members to a central repository graph

    Product Updates·3 min

    Introducing Helix Workspaces: Shared Context, Clear Ownership

    Helix Workspaces give teams a shared, permissioned home for repository graphs, Ask history, Pulse insights, reviews, and evidence.

  14. Three connected systems comparing code search, a knowledge graph, and an engineering graph

    Engineering Intelligence·3 min

    Engineering Graph vs. Knowledge Graph vs. Code Search

    Compare engineering graphs, enterprise knowledge graphs, and code search, and learn which questions each architecture can answer reliably.

  15. Engineering knowledge flowing from one expert into a shared graph of code and decisions

    Engineering Intelligence·3 min

    How to Preserve Tribal Knowledge in Software Teams

    Preserve engineering knowledge by capturing decisions in real work, connecting them to code, and making the evidence discoverable when teams need it.

  16. An AI review lens connecting a code diff with ownership, coupling, and prior decision evidence

    AI Engineering·3 min

    Why AI Code Review Needs Organizational Context

    AI code review becomes more trustworthy when it sees ownership, coupling, prior decisions, and review history, not only the current diff.

  17. A detailed engineering graph connecting code, people, and change history

    Engineering Intelligence·3 min

    Graph engineering is a practice, not a visualization

    Drawing nodes is easy. Encoding the relationships an organization actually uses is the work.

  18. A retrieval pipeline expanding from a code query through graph relationships to cited evidence

    AI Engineering·3 min

    RAG for Codebases: Why Graph Retrieval Beats Chunk Search

    Graph retrieval gives codebase RAG relationship and change context that chunk similarity misses, producing more relevant and inspectable answers.

  19. A constellation of connected software changes revealing pull request blast radius

    Engineering Intelligence·3 min

    Blast radius is a walk, not a feeling

    “What could this break?” is a graph query. Treat it like one.

  20. Helix agent loops learning from a continuous engineering workflow

    Product Updates·3 min

    Change intelligence is a closed loop

    Index, learn, ask, review, merge. Then the graph is smarter than it was yesterday.

  21. An API connection delivering trusted engineering graph context to coding agents

    Product Tutorials·3 min

    The Helix API is how agents get trusted context

    IDEs, CI, and coding agents should query the Engineering Graph: not guess from a README.

  22. A forensic graph of the repositories, pull requests, files, and people Helix connects

    Product Tutorials·3 min

    What Helix actually connects

    Relationships reconstructed from merge history: the map an organization can trust.

  23. An open engineering record organizing files into meaningful directory structures

    Engineering Intelligence·3 min

    Directories are the missing node

    Files are too small. Repositories are too big. Orgs understand code at the folder.

  24. Five Helix agent loops orbiting a luminous engineering graph

    Product Updates·3 min

    The graph that learns while you ship

    Helix agent loops watch merge history, encode Engineering DNA, and write it back as evidence you can click.

  25. A measured stream of engineering evidence flowing through the Helix API

    Product Updates·3 min

    Rate limits are evidence budgets

    Helix does not meter vanity. It meters how much of the graph you can ask in a day.

  26. A new engineer navigating a connected map of software knowledge

    Engineering Intelligence·3 min

    Onboarding without tribal knowledge

    A new engineer should not need six weeks of Slack to learn who knows checkout.

  27. An engineering DNA strand revealing a concentrated software knowledge silo

    Engineering Intelligence·3 min

    A silo is a graph shape, not a personality

    Single-owner files are a structural fact. Treat them as staffing evidence, not a score.

  28. An engineering knowledge book connected to a graph retrieval system

    AI Engineering·3 min

    GraphRAG is not a wiki with extra steps

    Retrieval over a junk graph still hallucinates. The graph has to be true before the language model speaks.

  29. A software constellation connecting code changes to the reasons behind them

    Engineering Intelligence·3 min

    Software should explain itself

    Speed without understanding creates complexity. Helix exists to preserve the why.

  30. The Helix Engineering Graph connecting files, pull requests, and people

    Engineering Intelligence·3 min

    The Engineering Graph is the system

    Software is a connected system. Never analyze files in isolation.

  31. A metallic helix representing the engineering patterns learned by a software team

    Engineering Intelligence·3 min

    Every team has Engineering DNA

    Helix learns the patterns that make your organization successful, and helps every engineer build with them.

  32. A forensic evidence board connecting engineering claims to their sources

    AI Engineering·3 min

    Evidence over opinion

    Every important claim should be traceable. Confidence comes from evidence, never assumptions.