Entity layer — operating objects gap audit¶
Purpose¶
Record what was missing in wiki/entities/ for repeatable operating objects (roles and categories that analyses referenced repeatedly without a stable link target), and what this pass added. Complements Structural audit — page ownership, entity gaps, and hub routing.
Rule: No site-specific hardware choices, deed facts, or legal names—those stay on worksheets, source-notes, or future named entity pages when evidenced.
Gap summary (before)¶
| Area | Issue | Direction |
|---|---|---|
| Field architecture | G/R/S/H/W node roles lived only inside Demory analyses | Entity + link from Field telemetry network — two-site |
| Gateways | “Gateway” used for RF→IP and WAN CPE interchangeably | Split: RF/telemetry gateway vs WAN edge / backhaul entities |
| Storage / backup | Longhorn vs central NAS vs tier labels scattered across DR analyses | Entities pointing at restore tiers + storage-role analyses |
| Labor / markets / legal | Business plan chapters held tables; no durable category pages | Generic labor roles, market channels, legal model placeholders |
| Platform | k3s/etcd/Rancher “roles” explained in analyses only | Control-plane entity as router |
| Infrastructure taxonomy | Water/power entities existed; cross-domain buckets for inventory matrices were implicit | Categories entity |
Added (this pass)¶
See Entities in index.md — operating-object cluster — and the pages listed in wiki/log.md under the matching refactor entry.
Habit: When an analysis introduces a third explanation of the same role label, add or extend an entity and replace prose with a link.