What ships

• Fleet Console — the app. Every instance on one page: recorded state, the version it is actually RUNNING, sampled health with the sample's age, and exact log links — attention first. Plus the record catalog and the request form for a new instance. An operator surface: it reports the fleet, it does not command it.
• Models — the first fleet configuration app (/Hosting/Models, formerly /Hosting/Ai, which redirects): pick a deployment and edit its AI providers, model slots, tiers and processing-region requirement, bound directly to its record, then Apply through a governed Reconcile. Its siblings follow the same shell — among them Integrations (/Hosting/Integrations), which registers the self-update announcement key a deployment generated, write-only with a fingerprint check — see Doc/Architecture/DomainConfigurationApps.
• Sign-in — the fleet identity-provider app (/Hosting/SignIn): a deployment's Microsoft, Google, LinkedIn and Apple client ids, tenant and developer login, bound directly to its record and applied through a governed Reconcile.
• Email — the fleet system-email app (/Hosting/Email): a deployment's Graph sender app, tenant, mailbox, inbound subscription and forwarding, bound directly to its record and applied through a governed Reconcile.
• Deployment — the git-backed record: host, namespace, database, update policy. Its Overview is the fleet table; its Logs area is that deployment's slice of the ingested window.
• FleetWatchPass — the watcher's OWN lifecycle: which pass opened, over how many rows, by when it must close, and how many of them it actually wrote. What tells a slow pass from a hung one from a schedule that has stopped.
• DeploymentStatus — observation: replicas, restarts, the image actually RUNNING, health — sampled every five minutes by the fleet watch. Every reading carries the cadence it is refreshed at and the instant it stops being current, so a frozen reading is shown as history rather than as the present. Its Board area is the fleet health board, compared against the latest available image.
• LogEntry — a window of Loki, landed as nodes so logs are searchable by meaning. Ingested by ingest-logs, browsable via Recent.
• Skills — /deployment to record and inspect, /deployment-activity for the pattern that keeps provisioning inside the mesh.

Records, not secrets

Deployment nodes are designed to sync to git, so they carry identifiers and topology only. Key Vault fields name secrets; they never hold them.

Contents