Namespace overview
The full picture in one surface.
Path, child namespaces, repository count, agent sessions, and recent activity. Everything an operator needs to understand the state of their estate — without navigating away.
LOOM.
Namespaces
Structure that scales without sprawl.
Nested namespaces, repository ownership, inherited grants, and activity across your full estate — one coherent hierarchy instead of a dozen settings pages.
Namespace trees
Hierarchy you can see, not infer.
Parent-child trees, repository membership by subtree, and inherited role propagation at each node. Structure is always visible — not buried in configuration.
Repository inventory
Every repo you can access, with its current state.
Path, default thread, latest change ID, and sync status. Scoped to what your role can see — so the view is always truthful, never inflated.
Access and grants
Direct, inherited, and effective — resolved for you.
How access flows through namespace ancestry, grants, and repo-specific overrides. Effective permission is always explicit. You never guess.
Activity timeline
Who changed what, across every repo in scope.
Filter by actor, repository, verification state, or time range. Human and agent actions are distinguished. Nothing escapes the record.
Hosted model
Organizational structure should be legible, not bureaucratic.
Parents, children, repos, inherited roles, and effective access — one coherent hierarchy. Not a collection of tabs and settings pages. The teams that scale cleanly are the ones that can see their own structure.