Skip to content

Quick Reference

The thing you reach for, fast. The commands, ports, keys, conventions, and fixes — stripped to their densest form for someone who already knows the Engine. Every entry condenses the Developer docs or the Technical Reference; follow the cross-links for the full story.

Most reached-for

Build · run · test (from the repo root):

dotnet build Aetherium_Refactor\Aetherium_Refactor.slnx
dotnet watch --project Aetherium_Refactor\Aetherium_Refactor\Aetherium_Refactor.csproj
dotnet test Aetherium_Refactor\Aetherium_Refactor.Tests\Aetherium_Refactor.Tests.csproj

dotnet build Aetherium_Refactor/Aetherium_Refactor.slnx
dotnet watch --project Aetherium_Refactor/Aetherium_Refactor/Aetherium_Refactor.csproj
dotnet test Aetherium_Refactor/Aetherium_Refactor.Tests/Aetherium_Refactor.Tests.csproj

Is it up?

Invoke-RestMethod http://localhost:5257/api/health

curl -s http://localhost:5257/api/health | jq

Top ports: Engine 5257 · LM Studio 1234 · PostgreSQL 5432 · ChromaDB 8000 · docs site 8765.

Top gotchas:

  • Publish the server .csproj, never the .slnx (Conventions).
  • Outer template object is camelCase, the team block is snake_case (Conventions).
  • appsettings.Local.json outranks environment variables (Config keys).
  • A cloud-prefixed model ID (gpt-, claude-, …) is silently skipped (Config keys).

The §16 thesis — keep this in mind

The Engine degrades quietly more often than it crashes loudly. When behavior is wrong but nothing is red, trust the /api/health/detailed body and the bracketed journal tags ([VRAM], [MODEL-ROUTING]) over the absence of an exception.

The pages

Page What's on it
Commands Build, run, test, migrate, publish, deploy, ops — two-shell
Ports & Services Every port, service, container, health endpoint, inbound API
Config Keys The most-changed keys with default + layer (curated)
Conventions The disciplines as a checklist
Troubleshooting Symptom → fix one-liners