nx-master

The agent-first CRM behind https://master.nextrum-sy.de: one Go service that owns the session, the conversations and the CRM data, with Hermes as the agent behind it and an MCP surface so agents reach data without a shell.

The service

• Service - what it is, what it refuses to be, and its runtime shape.
• Runbook - deploy, restart, rotate, provision, recover.

Design

• Chat authorization, as built - who is allowed to see which conversation.
• One bot per user - the target design that replaces the shared token.
• MCP authorization - the bearer boundary and the member-only rule.
• Roles are data - a soul plus a tool set, defined by a master and enforced by the MCP.

Data

• Data model - the SQLite tables and what each row means.

Interface

• MCP tools - the thirteen tools, their arguments, and what was removed.

Measurements

• Agent latency - where the wall-clock actually goes.
• Prompt size - why 13.5k tokens is the floor.

Decisions

• One bot per user - rejected: per-turn minted tokens.
• Drop chats.* from MCP - not having a tool beats scoping it.

Reference

• Deploy - the exact commands.
• Gateway operations - Hermes on the box, including the tools/list cache trap.
• conformance.rb - validates this bundle against OKF v0.2.

Rendered from nx-master/index.md · OKF bundle · regenerate with npm run render