Skip to content

Technical Reference

The complete tables. Every key, every endpoint, every signature.

The Technical Reference is the lookup layer for a developer who already understands the Engine and now needs the exact name, shape, or default. Where a Developer section said "the important keys; the full list is in the Technical Reference," this set is that full list — the exhaustive forms of §07 — MCP Architecture, §08 — Templates, and §09 — Configuration.

The Developer docs teach and curate; this set enumerates. It is consulted, not read: terse, table-shaped, and verified against code. Where it and a Developer section disagree, the code wins.

Lookup map

If you need… Go to
A config key, env var, default, or whether a setting is live Configuration
A REST endpoint's method, route, request, or response API Reference
An MCP tool's full parameter signature, tier, or return shape Tools
Which class owns a tool, or its dependencies MCP Server Classes
A template field's JSON name and casing, or an EF entity's columns Schema & Data Model

What's here

  • Configuration — every key across appsettings*.json and SystemSettings, with type, default, layer, and a live/inert mark. Includes the shadowed Cleanup timers and the hardcoded literals that have no key.
  • API Reference — 31 controllers, ~200 endpoints, four SignalR hubs, and the /mcp transport. Grouped into five domain pages. The whole surface is unauthenticated — stated plainly, per page.
  • Tools — all 33 MCP tools, full signatures, grouped by capability domain. Includes the verbatim group and tier maps and the router's argument coercions.
  • MCP Server Classes — the ten tool-owning classes, their tools, and their per-call dependencies.
  • Schema & Data Model — the ProjectTemplate / TeamConfig schema (with the camelCase/snake_case boundary) and the 26 EF entities.

Reading conventions

  • Voice. Terse. A sentence of context, then the table. This set is for lookup; the why lives in the Developer docs, cross-linked from each page.
  • Live vs. inert. Configuration and tools are marked for what the code actually does, not what a name implies. An inert key, a stale class comment, an unauthenticated endpoint — all called out honestly. A reference that hides these is worse than useless.
  • Anonymized. Defaults that ship with deployment-specific hosts, IPs, secrets, or identifiers are rendered as placeholders. Use localhost/127.0.0.1 and override locally.
  • Code-verified. Every entry was enumerated from source. Where a value differed from a Developer section, the delta is noted inline (the live default of the container image is one such case — see Configuration).

Where to go next