hzhang 604f6556fe feat(guild-discovery): add purpose column to guild_nodes + cli set-purpose
Adds a free-form 'purpose' text field on GuildNode so admins can describe
what each guild is for (debate broadcasts / agent triage / dev sandbox /
etc.). Surfaced through:

  - GET /api/auth/me/guilds   (existing user-facing list)
  - GET /api/nodes             (existing admin-facing list)
  - new cli: node set-purpose --node-id X --purpose 'text'

Admin-only writes via CLI (HangmanLab pattern) — never HTTP. Empty string
clears. TypeORM synchronize auto-adds the column on first startup.

Motivates: agents discover the right guild by intent (purpose substring
match) before picking a channel, so dialectic/announce workflows don't
need hardcoded guild ids.
2026-05-23 19:21:49 +01:00
2026-05-15 18:47:35 +01:00
2026-05-15 18:47:35 +01:00

Fabric.Backend.Center

The identity hub for Fabric (NestJS, ES modules, MySQL/TypeORM). Default port 7001, global prefix /api.

Center is the single identity authority. Guild nodes register with it and introspect the tokens it issues; the frontend uses it to log in and to discover which guilds a user belongs to.

Responsibilities

  • Users & sessions — register/login, JWT access + refresh tokens, GET/ PATCH /auth/me. User display name defaults to the email until changed.
  • Agent auth — per-agent API keys (fak_…); POST /auth/agent/login exchanges a key for a normal user session (used by Fabric.OpenclawPlugin).
  • Guild-node registry — nodes register (/api/nodes/register, localhost or node API key) and are handed out to users as endpoints + short-lived guild access tokens.
  • Name resolutionPOST /auth/resolve-names maps name/email → userId, scoped to a guild's members (used for <@user.name:NAME> mentions).
  • MembershipPOST /auth/me/guilds/join, GET /auth/me/guilds (returns guilds + fresh guild access tokens), GET /auth/guilds/:nodeId/members.

CLI

node dist/cli.js user create  --email <e> --password <p>
node dist/cli.js user apikey  --email <e> [--label <l>]      # prints fak_… once
node dist/cli.js node register --node-id <id> --name <n> --endpoint <url>

Run

npm install
npm run build && npm start          # or: npm run start:dev

Typically run via the root docker-compose.local.yml (service backend-center). MySQL schema is auto-managed (DB_SYNC).

Notable env

  • FABRIC_BACKEND_CENTER_PORT (default 7001)
  • FABRIC_BACKEND_CENTER_DB_* (host/port/user/password/name)
  • JWT signing secret(s) — see src/ config

Auth model

A global CenterApiKeyGuard protects most routes; auth/session endpoints (login, agent/login, refresh, logout, me, me/guilds*, resolve-names, guild members, node register) are exempted so users, agents, and nodes can bootstrap.

Notes

  • ES modules (NodeNext); CJS deps are default-imported (import jwt from 'jsonwebtoken', import bcrypt from 'bcryptjs').
  • @IsEmail() rejects single-character TLDs — use e.g. @t.tt.
Description
No description provided
Readme 362 KiB
Languages
TypeScript 98.8%
JavaScript 0.7%
Dockerfile 0.5%