Server record

Clicking a row in the server list opens the record. What separates it from a spreadsheet of the same data is that every value states who said it and when, and what the sources that disagreed said instead.

The record's address

The record key is the full host name, not its first label. SRV-APP-01.example.com and SRV-APP-01.example.net are two machines, and therefore two records at two addresses.

An address written with a short name still opens — the record resolves it by the first label and says on screen that it did. If more than one machine carries that first label, it names all of them and warns that they are not the same record.

The tabs

Tab	What is in it
Summary	Identity, the key fields, open vulnerabilities and recent changes
Specification	Hardware and software — including every field an administrator added
Network	Addresses, interfaces and connection details
Connectivity	The entities the server is related to: its system, its cluster, its host, the connected systems
Capacity	For a hypervisor — its guests and its share of the cluster; for a guest — its host and who moves with it
Updates	The maintenance events touching the server's system, two years back and one year forward
Vulnerabilities	The open vulnerabilities that match the server
Lifecycle	The record's state, in eight stages in order — discovered · requested · provisioning · active · maintenance · decommission planned · decommissioned · disposed
Requests · Documents	They hold their place and say they have no data source yet
Personal	Values true of this machine and no other, outside the entity type's field schema
History	Who changed what, when, and from which value to which

At the top of the record: host name, system, the environment tag, an "externally exposed" mark when the Tier faces outward, a completeness ring, and three clickable metrics — open vulnerabilities, last updated, next due.

Where the value came from

Beside every value is a small source label: the source name and its age ("4 hours ago"). Clicking it opens the Sources panel:

• Winner — the chosen value, its source, its age, and who set it if a person did.
• Disagrees — every source that answered differently, with its value shown. Disagreeing values are kept and never merged into the winner.
• Asked, did not answer — sources that were asked and returned empty.
• Too old to count — sources whose answer fell outside the field's freshness period.

The winning value is decided by the precedence chain configured for the field, not by whoever answered last. If the record holds fields where more than one source answered differently, their number appears as a Mismatch tag at the top.

An empty cell — four meanings

State	What it says
Never asked	No source was asked about this field
Asked — no value returned	The source was asked and returned empty. That is an answer, not an absence of one
Not entered	The field has no automatic source — somebody has to enter it
All answers too old	There are answers, all of them outside the field's freshness period, so none of them wins

Editing

Editing is per field, not per form. The field updates on screen immediately, and the save comes back with an explicit answer if it was not written — in which case the value reverts and a message appears.

• A field whose value comes from an automatic source is edited through Set a different value, with a reason. The override is recorded as a value a person set, and the automatic source stays in the panel as a disagreeing source.
• Two editors at once: the write carries the version number the editor saw. If it changed meanwhile the save is refused and a dialog shows your value against the one on the server. There is no silent overwrite.
• Inventory fields — host name, IP, system — are not edited here: they reflect the inventory source and would be rewritten on the next sync. Their label, group, order and visibility are yours to change, in screen design.

Vulnerabilities — two kinds of match, never blended

Label	What is behind it
Confirmed by scan	The server is named in the vulnerability's affected-host list
Estimated exposure	A match on OS family, version pattern and last update date

An authoritative host list that does not include the server is a definite "no" — and is not re-tested by the heuristic.

History

The change log records edits by people: who, when, from which value to which, and with what reason. It does not record what automatic sources reported — the Sources panel is for that.

When part of the data does not load

Each leg of the load is independent. The record layer — sources, history and editing — can be unavailable while the inventory fields render normally, and the record says which half is missing instead of looking empty.