How jnunez2001/agencyos works
NexusOS is an organization-scoped agency operations platform: staff manage clients and projects, execute tasks and meetings, track time, maintain SOPs and QA, and record results for reporting. The principal workflow runs from the browser through the API routes into permission-aware domain services that persist agency data. Separate branches provide AI tools and Google integrations, alongside identity, activity, and notifications. The map reflects the README and the supplied source index; several capabilities are documented or listed but their implementation was not excerpted, so uncertain internal links are omitted.
Main entry points: api.js API routes · mcp.js AI assistants · clients.js Clients and goals · tasks.js Tasks and QA
Components 23
Web experience
- Web application
public/js/app.js - Feature views
public/js/views - API client
public/js/api.js
Agency operations
- Clients and goals
server/services/clients.js - Projects
server/services/projects.js - Tasks and QA
server/services/tasks.js - Events and meetings
server/services/events.js - Time and retainers
server/services/timeentries.js - SOPs
server/services/sops.js - Client requests
server/services/requests.js - Follow-ups
server/services/followups.js - Decisions
server/services/decisions.js
Insights and assistance
- Results
server/services/results.js - Reports
server/services/reports.js - AI assistants
server/mcp.js - Google integration
server/googlehub.js
Platform services
- API routes
server/routes/api.js - Identity and access
server/services/permissions.js - Activity log
server/services/audit.js - Notifications
server/services/notifications.js - SQLite database
server/db.js - HTTP server
server/app.js
Other components
- Agency staff
Connections 27
- Agency staff → Web application: uses
README.md - Web application → Feature views: loads
public/js/app.js - Feature views → API client: requests data
public/js/views/clients.js - API client → API routes: sends API requests
- HTTP server → API routes: mounts
server/app.js - API routes → Clients and goals: dispatches
server/routes/api.js - API routes → Projects: dispatches
server/routes/api.js - API routes → Tasks and QA: dispatches
server/routes/api.js - API routes → Events and meetings: dispatches
server/routes/api.js - API routes → Time and retainers: dispatches
server/routes/api.js - API routes → SOPs: dispatches
server/routes/api.js - API routes → Client requests: dispatches
server/routes/api.js - API routes → Follow-ups: dispatches
server/routes/api.js - API routes → Decisions: dispatches
server/routes/api.js - API routes → Results: dispatches
server/routes/api.js - API routes → Reports: dispatches
server/routes/api.js - API routes → Identity and access: checks access
server/routes/api.js - Clients and goals → Activity log: records changes
server/services/clients.js - Projects → Clients and goals: checks client
server/services/projects.js - Tasks and QA → SOPs: uses SOPs
server/services/tasks.js - AI assistants → Clients and goals: uses domain tools
server/mcp.js - AI assistants → Tasks and QA: uses domain tools
server/mcp.js - AI assistants → Events and meetings: uses domain tools
server/mcp.js - AI assistants → Client requests: uses domain tools
server/mcp.js - Google integration → HTTP server: integrates
- API routes → Notifications: dispatches
server/routes/api.js - API routes → SQLite database: persists through