Architecture map
How the repo is organized
Click systems in the graph to inspect responsibilities, important files, and nearby dependencies.
Architecture map
Use this map to orient around systems, dependencies, and files worth reading first.
Click a system in the map
Explore nex-crm/wuphf by selecting services, gateways, clients, and data stores. Each node shows the files, responsibilities, and neighboring systems an agent should keep in scope.
Pan, zoom, and use the minimap to keep large repos navigable.
Sign up to turn selected graph context into repo-aware agent sessions.
Key systems
What an agent should understand first
Web UI (React SPA) or Electron desktop app for human-agent interaction
Electron main process supervising broker and IPC to renderer
Loopback message bus with DNS-rebinding guard, bearer token auth, push-driven event pub/sub
Multi-agent orchestrator; decides which agents wake for messages; spawns headless runners
Fresh session per turn; no --resume accumulation; runs in isolated git worktree per task
Per-agent scoped MCP tool surface; DM loads ~4 tools, office loads ~27; approval gates
Branded types, receipt schema, stream events, audit chains, WebAuthn assertions
Per-agent notebook (private) + shared wiki (git-native markdown); LLM synthesis loop
Evidence coverage
What this context is grounded in
Coverage
- Citations
- 8
- Findings
- 5
- Files discovered
- 3,659
- Architecture systems
- 12
- Architecture relationships
- 15
- Agent graph
- Agent graph entities
- 21,686
- Agent graph relationships
- 27,287