← c12c12 / wf1 - Inventory Deep Dive / Inventory / Endpoints
Qpoint
QI
Inventory /endpoints

Endpoints Category View

Endpoint inventory should show which machines anchor trust, which ones are unresolved, and where sensitive work is physically running before it behaves like an asset list.

The category page should foreground environment type, ownership confidence, and whether one machine is becoming a shared lane for important work.

Use This Page When Asking

Which hosts are trusted execution homes, and which ones weaken attribution or boundary confidence?

Representative Detail

alice-mbp.local

Open representative detail

Endpoints observed

19

Developer and CI mixed

Unresolved hosts

1

Weak owner mapping

High-signal hosts

2

Sensitive work or weak trust

Developer baseline

7

Strong comparison set

Why This Page Exists

This category page should help the reviewer decide what matters in endpoints before the raw table takes over the reading experience.

What This Page Should Make Obvious

The reviewer should know what is routine, what is risky, and what deserves the next click.

Hosts are trust anchors

The page should show which endpoints strengthen attribution and which ones weaken it.

Context matters more than raw inventory facts

OS, runtime, and owner mapping only matter when kept beside the work actually running there.

User and session adjacency should stay close

A host without its people and sessions is harder to interpret correctly.

Fastest Drill Paths

The next clicks should feel obvious and intentional.

Known developer host baseline

A representative laptop with stable ownership and normal activity.

Open representative detail

It gives the reviewer a strong baseline for comparing unresolved endpoints.

Raw endpoint table

The canonical host list still matters for exact OS, runtime, and session counts.

Open c6 raw list

The refined page should lead into the raw host inventory rather than replace it.

Endpoint-Centered Topology

An endpoint map should show the machine, the identities on it, and the activity that originates there.

Useful per endpoint: host identity, OS/runtime posture, associated users, agent stack, models, destinations, and whether the machine fits an expected environment class.

Endpoint

10.0.1.44

Unresolved host currently tied to an active session and an unknown API key.

1 session · unknown OS

Type

unknown

Associated user

unknown

Current agent

Claude Code v1.2.0

Current credential

sk-ant-...C001

Machine Identity

What the host is supposed to be.

3 nodes
10.0.1.44hostname + IP
unknown OSfingerprint gap
unknown archfingerprint gap

Observed Activity

What is running there right now.

3 nodes
unknown user1 session
Claude Code v1.2.0agent
claude-sonnet-4-6model

Comparative Context

How this host compares with normal fleet shapes.

3 nodes
developer_machineexpected class
ci_runnerexpected class
outside known fleettriage path

Risk Lens

Why a machine-level view matters.

3 nodes
unknown key attachedcredential issue
active sessionlive activity
needs enrichmentasset inventory link

c6 Raw Reference

c6 shape: endpoint roster with host metadata, session counts, and user counts.

1 unresolved endpoint

10.0.1.44 has active AI usage but no owner or environment label yet.

Endpoints

19

Unknown owners

1

Active hosts

5

Users across hosts

7

Why Keep The Raw Ledger

c12 should still flow back into the raw inventory model. This page frames the question and likely answer; the raw table proves it.

Open c6 Raw List

Use the original category ledger for exact rows, counts, and timestamps.

Open c6 raw list

Raw Endpoint Inventory

Host, IP, environment, type, sessions, and users.

HostnameIPOSTypeSessions
alice-mbp.local10.0.1.12macOSdeveloper6
10.0.1.4410.0.1.44macOSunknown1
gh-actions-runner-1210.0.3.19linuxci11