Sites and apps
Which domains, document roots, services, and publish targets belong to a server.
Server profiles keep publishing workflows grounded in the right live state.
TraceLayer is structured as a multi-server control layer. The current source-of-truth server is the enabled default today, while future profiles can represent staging, backup, storage, worker, database, or public web nodes.
Server Registry
Primarysource truth
Stagingdisabled
Backupdisabled
Workerfuture
What a server profile can describe
Connection references
Server connection labels and scoped control areas, without exposing private keys or passwords in the frontend.
Service map
Which apps, websites, queues, and provider health checks belong to each server profile.
Storage and databases
Allowed workspaces, mounts, database inventories, and metadata-only sync boundaries.
Deployment mappings
Which server owns a deployment target and what dry-run review should check before a change.
Audit identity
Each action can record the target server so reviews stay clear across multiple machines.
Server control stays scoped and review-first.
TraceLayer is not an unrestricted root web shell. Server workflows are designed around scoped providers, allowed roots, metadata-first scans, dry-runs, audit logs, and explicit confirmation before writes or restarts.
Technical Details
Server profiles can include connection references, deployment mappings, service ownership, storage mounts, and source-of-truth flags. Private hostnames, credentials, exact paths, and live operational topology should stay out of public pages.
Default today
The current server profile is the primary source of truth for TraceLayer state and deployment review.
Future direction
Additional servers can be added as disabled profiles first, then enabled only after access, safety, and dry-run behavior are reviewed.