tropo

The Agentic Builders / New to Agents · 12 of 14

Navigating with Tropo-Nav

· 3 min read

New to Agents · Beginner Path · 12 of 14

A graph of files named by hex IDs is perfect for an agent and miserable for a human. Tropo-nav is the bridge.

There's a tension built into the design. The files are named by short IDs - b1f9cc95.md - so the graph can reference them reliably no matter how they're renamed or retitled. That's exactly right for the machine. But a person staring at a folder full of b1f9cc95.md and c5acb1a3.md can't navigate anything. People need readable names and a tree they can walk.

Tropo-nav resolves it. It's a second, human-facing view of the same graph, where every file appears under its readable title in a folder tree that mirrors the relationships. The agent reads the ID-based graph; you browse the readable tree. Same underlying files, two surfaces - one tuned for the machine, one for you.

And - you can probably guess by now - it isn't maintained by hand. Tropo-nav is generated from the graph. Add a file, give it a title, link it to its parent, and it shows up in the readable tree in the right place automatically. So you get the machine's reliable IDs and the human's readable navigation at the same time, and neither one can drift from the other, because both are drawn from the one set of files.

Underneath sits a principle worth keeping: the substrate is built for agents, but the rendered surface is a deliverable for humans too. Agent-first, never agent-only. You always have a way in.

One graph, two views AGENT READS 30bdeba4.md b02630c5.md b1f9cc95.md c5acb1a3.md 57a9c21f.md reliable IDs the graph one set of files YOU BROWSE New to Agents What is an Agent What is an LLM Context Window What is Memory What is a Session readable tree both generated from the graph - neither one drifts

Why this matters for Tropo

Tropo-nav is the human-navigation half of Tropo's whole philosophy made tangible.

A system that's agent-first but agent-only would lock the human out of their own work - exactly the trap Tropo is built to avoid. So every file the agents reference by ID, you can reach by name; every relationship the graph holds, you can walk as a tree. The machine gets what it needs to be reliable, and you get what you need to stay in control, from the same source of truth. That balance - built for agents, navigable by humans - is the line Tropo refuses to cross.

Beginner Path · New to Agents ← Before: How Boards and Work Get Generated · Next: Changing How You Work → Related: Why a Graph Filesystem Works · See the whole path: New to Agents - Beginner Path