How redjijb/sodboys-fieldops works
D-Central FieldOps is a clean-slate, D-Central-native field-operations backend intended to replace fieldops-system. Its current documented status is Phase 1: foundational identity, capability authorization, and MCP skeleton, with no domain logic. The repository also contains a REST façade and a broad set of operational domain modules, but the README cautions that implementation and verification status vary. The graph shows the evidenced runtime entry points and identity/storage relationships; several domain branches are grouped because their route and tool internals were not sampled.
Main entry points: routes REST route handlers · tools MCP tools · capabilities.ts Capability grants · server.ts REST façade
Components 21
Runtime interfaces
- REST façade
src/facade/server.ts - Route dispatch
src/facade/router.ts - REST route handlers
src/facade/routes - MCP tool server
src/mcp/server.ts - MCP HTTP transport
src/mcp/transports/http.ts - MCP stdio transport
src/mcp/transports/stdio.ts
Field operations
- MCP tools
src/mcp/tools - People and time
src/domain - Sites and resources
src/domain - Work and reporting
src/domain - Procurement and spend
src/domain - Notifications and chat
src/domain - Admin and integrations
src/domain
Identity and authorization
- REST authorization
src/facade/auth.ts - Capability grants
src/identity/capabilities.ts - Access tokens
src/identity/accessToken.ts - DID resolution
src/identity/did.ts - Identity keys
src/identity/keys.ts
Persistence
- Postgres pool
src/db/pool.ts - Database migration
src/db/migrate.ts
Other components
- API or agent client
Connections 26
- REST façade → Route dispatch: dispatches
src/facade/server.ts - REST façade → REST route handlers: registers
src/facade/server.ts - REST façade → API or agent client: serves requests
- Route dispatch → REST route handlers: invokes handlers
src/facade/routes/webhookTargets.ts - REST route handlers → REST authorization: authorizes
src/facade/routes/webhookTargets.ts - REST route handlers → Admin and integrations: calls
src/facade/routes/webhookTargets.ts - REST route handlers → People and time: calls
src/facade/routes/fieldTime.ts - REST route handlers → Procurement and spend: calls
src/facade/routes/procurement.ts - REST route handlers → Work and reporting: calls
src/facade/routes/payroll.ts - MCP HTTP transport → MCP tool server: serves
src/mcp/transports/http.ts - MCP stdio transport → MCP tool server: serves
- MCP tool server → MCP tools: registers
src/mcp/server.ts - MCP tools → Sites and resources: calls
src/mcp/tools/assets.ts - MCP tools → Notifications and chat: calls
src/mcp/tools/notifications.ts - MCP tools → Procurement and spend: calls
src/mcp/tools/orders.ts - MCP tools → Work and reporting: calls
src/mcp/tools/spending.ts - MCP tools → Capability grants: checks access
- REST authorization → Access tokens: verifies
src/facade/auth.ts - REST authorization → Capability grants: checks standing grant
src/facade/auth.ts - Capability grants → Postgres pool: queries grants
src/identity/capabilities.ts - Capability grants → DID resolution: verifies credential
src/identity/capabilities.ts - DID resolution → Identity keys: loads local key
src/identity/did.ts - Identity keys → Postgres pool: stores keys
src/identity/keys.ts - Access tokens → DID resolution: resolves identity
src/identity/accessToken.ts - Database migration → Postgres pool: uses pool
src/db/migrate.ts - REST route handlers → API or agent client: returns responses