Code movement as project evidence.
Repository Topology brings Git into the same project truth. Branches, commits, merges, dirty worktrees, runtime identity, and release inclusion should not be understood only by the few people who remember which terminal did what. They should be visible enough for humans and agents to coordinate safely.
The central questions are practical: which mission does this branch belong to, what is already in main, what reached production, what runtime is serving which commit, and where can code be lost or overwritten if people continue blindly? Repository Topology makes those questions inspectable beside requirements and execution.
A commit is not just history. It is evidence about what reached which runtime.
The perspective should remain factual rather than decorative. It can use graph interactions, selection panels, and supporting lanes, but the authority comes from live repository facts attached to a Library, not from a manually maintained diagram.