Blog/Engineering Intelligence··3 min
Directories are the missing node
Files are too small. Repositories are too big. Orgs understand code at the folder.
- directory ownership
- code architecture
- engineering graph
- repository structure

Ask an engineer where checkout lives and they will not say a hash. They will say src/. Ask who owns payments and they will name a person and a folder.
Most graphs skip that layer. They draw files, or they draw services, and they miss the unit organizations actually talk in.
CONTAINS, TOUCHED, OWNS
Helix reconstructs directory nodes from file paths. A folder is a first-class node:
CONTAINS: repository → directory → fileTOUCHED: the people who keep changing files in that folderOWNS: the person who authored a majority of the indexed changes
Pulse shows an Architecture list: folders, file counts, inferred owners. Ask Helix can answer “Who owns src?” from those edges, not from CODEOWNERS folklore.
for (const file of files) {
const dir = dirname(file.label);
graph.addEdge({ from: dirId(dir), to: file.id, type: "CONTAINS" });
}
The reconstruction is boring, which is the point. Prefixes are not a machine-learning problem. They are a modeling choice. Skip them and you force every org question down onto files, where the answers get noisy and the staffing picture disappears.
Why files lie about ownership
A file can have three authors in a month and still live in a folder that one person has touched for a year. The file-level OWNS edge is a local claim. The directory-level TOUCHED edge is the org claim. Graph engineering keeps both and refuses to smush them into a single “owner” badge.
CODEOWNERS is an assignment you hope is true. Merge history is what still happened after the hope got stale.
Architecture as a list, not a slide
Executives do not need a 3D globe of microservices. They need: these ten folders absorb most of the change, these two are silos, this one is coupled to payments. Pulse is that list. The canvas is how an engineer verifies it. Ask Helix is how a new hire uses it on day one.
If your graph cannot answer “who owns src?”, it is not an engineering graph yet. It is a file browser with extra ink.
Index a repository and look at the Architecture list. Open Helix: directories are nodes, and they are how organizations actually think.



