{{/* /fleet/architecture (archpage.go): the deployment's map — how a request reaches a process, drawn over the estate the account is carrying. Everything here is server-rendered: the diagram is inline SVG built in Go (archlayout.go's RenderArchSVG) so the picture is deterministic and testable as a whole, and the page works with JS off because there is no JS. Every block below is independently guarded — the inventory, the boxes, the resource tables and the failed-reads footer each appear only when their own read produced something, so one bad read costs its own section and never the page. */}} {{define "architecture"}}{{template "top" .}}
Estate {{.Account}} · inventoried {{fmtTime .TakenAt}}
{{end}} {{/* Two estates, one above the other, never one picture with a line through it. The account holds a CARLOS deployment and, very often, whatever was already there — Tito's own account carries a Kubernetes estate CARLOS deliberately sits beside so it can reach the legacy database. Drawn together that is one unreadable graph; drawn apart it is two readable ones. NOTHING IS FILTERED. Every node and every resource on the old single page is still here, under one of the two headings — the split groups, it does not hide (archestate.go). */}}{{if .InstanceType}}{{.InstanceType}}{{end}} {{if .State}}{{.State}}{{end}} {{if .Cores}}{{printf "%.0f" .Cores}} cores{{end}} {{if .MemGB}}{{printf "%.0f" .MemGB}} GB{{end}} {{if .DiscoveredDiskGB}}{{printf "%.0f" .DiscoveredDiskGB}} GB disk{{end}} {{if .USDMonth}}${{printf "%.0f" .USDMonth}}/mo{{end}} {{if not .CloudID}}no cloud machine (bring-your-own box){{end}}
Apps: {{if .Apps}}{{range .Apps}}{{.}} {{end}}{{else}}none reported{{end}}
{{if .CountsKnown}}static {{.Static}} · resident {{.Resident}} · hibernating {{.Hibernating}} ·
awake {{intOrDash .Awake}} · asleep {{intOrDash .Asleep}}
{{else}}counts unknown{{end}}
{{with .Release}}· {{.}}{{end}}
dark{{if .Dark}} {{.Dark}}{{end}}
{{end}} {{/* Drift is where the rate card and the estate disagree — a fact to watch, not an outage, so it wears chip-stale's bordered warn tone rather than a filled marker. */}} {{range .Drift}}{{.}}
{{end}}The box list could not be read — this is not a claim that the deployment has no boxes.
{{else}}No box has reported to this deployment yet.
{{end}} {{end}} {{range .CARLOS.Groups}}Everything else the account is carrying. The console has no first-hand knowledge of these — it can see them, and it cannot trace a path to any of them from a box it runs or the bucket it deploys from.
{{/* One picture per region, stacked down the page. Region is the STRUCTURE here, not a word on a card: a box is the only thing on this diagram that is really in a region, and everything else is drawn in the band of the box it reaches (archregion.go). That is also what keeps each picture inside the 64rem column — a band is at most four nodes wide — so this page scrolls down and never across. */}} {{range .Rest.Bands}}| Name | Type | Region | Detail |
|---|---|---|---|
| {{.Name}} | {{.NativeType}} | {{.Region}} | {{.Detail}} |