API

Verified host compositionSurface interpretation

File-level companion page: API source map

Verified anchors

NGB.Api/NGB.Api.csproj
NGB.PropertyManagement.Api/Program.cs

What is directly visible

Shared API module

NGB.Api.csproj shows the shared API layer depends on:

ASP.NET Core
contracts/application abstractions/runtime
authentication/OpenAPI/Serilog-related packages

Vertical API host composition

NGB.PropertyManagement.Api/Program.cs shows how a vertical host composes the platform:

shared infrastructure and logging
health checks
runtime registration
PostgreSQL provider registration
vertical module registration
controller mapping
auth/cors/exception pipeline

Practical interpretation

This strongly suggests the intended model is:

shared API package = reusable API building blocks
vertical API host = executable composition root

That is the right split for a multi-vertical platform.

Why this matters for docs and extension work

When documenting or extending API behavior, keep three concerns separate:

Shared API capabilities
Vertical host composition
Runtime business orchestration

Do not describe host startup code as if it were runtime logic, and do not describe runtime orchestration as if it were an ASP.NET concern.

Continue with