diff --git a/frontend/src/components/AssetRelationships.vue b/frontend/src/components/AssetRelationships.vue
index 5aaf4afc..0b1d11b1 100644
--- a/frontend/src/components/AssetRelationships.vue
+++ b/frontend/src/components/AssetRelationships.vue
@@ -186,6 +186,7 @@
 </template>
 
 <script setup>
+import { assetRoute } from '@/utils/assetRoute'
 import { ref, computed, onMounted, watch } from 'vue'
 import { Cog, Monitor, Printer, Globe, Package, Ruler } from 'lucide-vue-next'
 import { assetsApi, relationshipTypesApi } from '../api'
@@ -472,28 +473,7 @@ function getAssetIcon(assettype) {
   return icons[assettype] || Package
 }
 
-function getAssetRoute(asset) {
-  if (!asset) return '#'
-
-  const routeMap = {
-    'machine': '/machines',
-    'computer': '/pcs',
-    'printer': '/printers',
-    'network_device': '/network',
-    'measuring_tool': '/measuringtools'
-  }
-
-  // serializer sends assettypename; old shape used assettype
-  const typename = asset.assettypename || asset.assettype
-  const basePath = routeMap[typename] || '/assets'
-
-  // pluginid is the extension-table id the detail routes key on
-  const id = asset.pluginid
-    || asset.typedata?.networkdeviceid
-    || asset.typedata?.machineid
-    || asset.assetid
-  return `${basePath}/${id}`
-}
+const getAssetRoute = assetRoute
 </script>
 
 <style scoped>
diff --git a/frontend/src/components/AssetTriageBand.vue b/frontend/src/components/AssetTriageBand.vue
index 270fc1c4..15556f89 100644
--- a/frontend/src/components/AssetTriageBand.vue
+++ b/frontend/src/components/AssetTriageBand.vue
@@ -8,13 +8,13 @@
     </div>
 
     <div v-if="machines.length" class="triage-item">
-      <span class="triage-label">{{ machines.length === 1 ? 'Serves machine' : 'Serves machines' }}</span>
+      <span class="triage-label">{{ counterpartheading }}</span>
       <span class="triage-values">
         <router-link
           v-for="machine in machines"
           :key="machine.assetid"
           class="triage-chip link"
-          :to="`/assets/${machine.assetid}`"
+          :to="assetRoute(machine)"
         >{{ machine.assetnumber || machine.name }}</router-link>
       </span>
     </div>
@@ -63,6 +63,7 @@
  */
 import { ref, computed, onMounted, watch, useSlots } from 'vue'
 import api from '@/api'
+import { assetRoute } from '@/utils/assetRoute'
 
 const props = defineProps({
   assetid: { type: Number, required: true },
@@ -71,11 +72,30 @@ const props = defineProps({
   // Shape: { level: 'ok'|'warning'|'critical'|'unknown', label: 'Reporting, 4m ago' }
   liveness: { type: Object, default: null },
   accessmethods: { type: Array, default: () => [] },
-  locationname: { type: String, default: '' }
+  locationname: { type: String, default: '' },
+  // Which side of a 'controls' edge this page wants to see, by asset type
+  // name. A PC page wants the machines it serves; a machine page wants the
+  // PCs that drive it. Defaults to 'machine' so the PC page - the only
+  // caller when this was written - keeps its exact behaviour.
+  counterparttype: { type: String, default: 'machine' },
+  // Overrides the heading. Empty keeps the shop-floor phrasing that earned
+  // its place: a PC matters because a machine stops without it.
+  counterpartlabel: { type: String, default: '' },
+  // Which relationship types link this asset to its counterpart. Not every
+  // pairing is 'controls': a PC controls a machine, but a machine reaches a
+  // printer through usesprinter and defaultprinter. Hardcoding 'controls'
+  // left the band blank on the printer page, which is the one page where the
+  // link is not obvious from the asset itself.
+  relationshiptypes: { type: Array, default: () => ['controls'] }
 })
 
 const machines = ref([])
 
+const counterpartheading = computed(() => {
+  if (props.counterpartlabel) return props.counterpartlabel
+  return machines.value.length === 1 ? 'Serves machine' : 'Serves machines'
+})
+
 const slots = useSlots()
 
 const hasAnything = computed(() =>
@@ -87,7 +107,7 @@ const hasAnything = computed(() =>
 )
 
 onMounted(loadMachines)
-watch(() => props.assetid, loadMachines)
+watch(() => [props.assetid, props.counterparttype, props.relationshiptypes], loadMachines)
 
 async function loadMachines() {
   machines.value = []
@@ -96,9 +116,11 @@ async function loadMachines() {
     const response = await api.get(`/assets/${props.assetid}/relationships`)
     const data = response.data.data || {}
     const found = []
-    // BOTH directions. The canonical edge is PC controls machine, but
-    // production also holds reciprocal rows, so reading one direction shows
-    // the link on half the pages and not the other half.
+    // BOTH directions, then deduped. Production holds reciprocal rows for
+    // the same link, so reading one direction shows it on half the pages and
+    // not the other half - and reading both without deduping shows it twice.
+    // Direction is therefore not trustworthy here and is deliberately not
+    // used to label anything.
     for (const edge of data.outgoing || []) collect(edge, edge.targetasset, found)
     for (const edge of data.incoming || []) collect(edge, edge.sourceasset, found)
     machines.value = found
@@ -111,10 +133,19 @@ async function loadMachines() {
 
 function collect(edge, other, found) {
   if (!other) return
-  if ((edge.relationshiptypename || '').toLowerCase() !== 'controls') return
-  if ((other.assettypename || '').toLowerCase() !== 'machine') return
+  const wanted = props.relationshiptypes.map(t => t.toLowerCase())
+  if (!wanted.includes((edge.relationshiptypename || '').toLowerCase())) return
+  if ((other.assettypename || '').toLowerCase() !== props.counterparttype.toLowerCase()) return
   if (found.some(m => m.assetid === other.assetid)) return
-  found.push({ assetid: other.assetid, assetnumber: other.assetnumber, name: other.name })
+  // pluginid and assettypename are what assetRoute() needs; without them the
+  // chip falls back to /assets/<assetid>, which is not a route.
+  found.push({
+    assetid: other.assetid,
+    assetnumber: other.assetnumber,
+    name: other.name,
+    pluginid: other.pluginid,
+    assettypename: other.assettypename
+  })
 }
 </script>
 
diff --git a/frontend/src/utils/assetRoute.js b/frontend/src/utils/assetRoute.js
new file mode 100644
index 00000000..36f96028
--- /dev/null
+++ b/frontend/src/utils/assetRoute.js
@@ -0,0 +1,43 @@
+/**
+ * Where an asset's detail page lives.
+ *
+ * Extracted from AssetRelationships.vue because a second caller appeared (the
+ * triage band) and got it wrong: it linked to `/assets/<assetid>`, which is not
+ * a route. There is no `/assets/:id` page and no catch-all, so every chip was a
+ * dead link. One copy, so a third caller cannot repeat it.
+ *
+ * Two ids are in play and they are not interchangeable. `assetid` is the core
+ * row; the detail routes key on `pluginid`, the id of the extension-table row
+ * (machineid, computerid, printerid). Sending assetid to /machines/:id opens
+ * the wrong machine, or none.
+ */
+
+// Asset type NAME to route base. The names are seed data, and seeding is not
+// consistent about case: shopdb/core/services/csvimport.py seeds 'Computer'
+// and 'Machine' capitalised, while this site's database holds them lowercase.
+// The lookup is therefore lowercased on both sides - a case-sensitive match
+// silently produced dead links at whichever site seeded the other way.
+const ROUTE_BY_TYPE = {
+  machine: '/machines',
+  computer: '/pcs',
+  printer: '/printers',
+  network_device: '/network',
+  'network device': '/network',
+  measuring_tool: '/measuringtools',
+  'measuring tool': '/measuringtools'
+}
+
+export function assetRoute(asset) {
+  if (!asset) return '#'
+
+  const typename = String(asset.assettypename || asset.assettype || '').toLowerCase()
+  const basePath = ROUTE_BY_TYPE[typename] || '/assets'
+
+  const id = asset.pluginid
+    || asset.typedata?.networkdeviceid
+    || asset.typedata?.machineid
+    || asset.assetid
+  return `${basePath}/${id}`
+}
+
+export default assetRoute
diff --git a/frontend/src/utils/assetRoute.spec.js b/frontend/src/utils/assetRoute.spec.js
new file mode 100644
index 00000000..819dbf74
--- /dev/null
+++ b/frontend/src/utils/assetRoute.spec.js
@@ -0,0 +1,54 @@
+import { describe, it, expect } from 'vitest'
+import { assetRoute } from './assetRoute'
+
+describe('assetRoute', () => {
+  // The bug this file exists to prevent: the triage band linked to
+  // /assets/<assetid>, and there is no /assets/:id route and no catch-all,
+  // so every chip was a dead link on five detail pages.
+  it('routes by asset type, never to /assets', () => {
+    expect(assetRoute({ assettypename: 'machine', pluginid: 223, assetid: 313 }))
+      .toBe('/machines/223')
+    expect(assetRoute({ assettypename: 'computer', pluginid: 279, assetid: 304 }))
+      .toBe('/pcs/279')
+    expect(assetRoute({ assettypename: 'printer', pluginid: 1, assetid: 594 }))
+      .toBe('/printers/1')
+  })
+
+  it('uses pluginid, not assetid - they are different rows', () => {
+    // /machines/:id keys on machineid. Passing assetid opens the wrong
+    // machine, or none, and looks like a data problem rather than a link bug.
+    const route = assetRoute({ assettypename: 'machine', pluginid: 223, assetid: 313 })
+    expect(route).toBe('/machines/223')
+    expect(route).not.toContain('313')
+  })
+
+  it('matches the type name whatever case the site seeded it in', () => {
+    // csvimport.py seeds 'Computer' and 'Machine' capitalised; this site's
+    // database holds them lowercase. A case-sensitive lookup produced dead
+    // links at whichever site seeded the other way.
+    expect(assetRoute({ assettypename: 'Computer', pluginid: 7 })).toBe('/pcs/7')
+    expect(assetRoute({ assettypename: 'MACHINE', pluginid: 8 })).toBe('/machines/8')
+  })
+
+  it('accepts the older assettype key as well as assettypename', () => {
+    expect(assetRoute({ assettype: 'printer', pluginid: 4 })).toBe('/printers/4')
+  })
+
+  it('falls back through typedata when pluginid is absent', () => {
+    expect(assetRoute({ assettypename: 'network_device', typedata: { networkdeviceid: 12 } }))
+      .toBe('/network/12')
+    expect(assetRoute({ assettypename: 'machine', typedata: { machineid: 30 } }))
+      .toBe('/machines/30')
+  })
+
+  it('returns a harmless anchor for nothing', () => {
+    expect(assetRoute(null)).toBe('#')
+    expect(assetRoute(undefined)).toBe('#')
+  })
+
+  it('handles both spellings of the multiword type names', () => {
+    expect(assetRoute({ assettypename: 'network device', pluginid: 2 })).toBe('/network/2')
+    expect(assetRoute({ assettypename: 'measuring_tool', pluginid: 3 })).toBe('/measuringtools/3')
+    expect(assetRoute({ assettypename: 'measuring tool', pluginid: 3 })).toBe('/measuringtools/3')
+  })
+})
diff --git a/plugins/machines/frontend/views/MachineDetail.vue b/plugins/machines/frontend/views/MachineDetail.vue
index fb48ed49..f9d49c88 100644
--- a/plugins/machines/frontend/views/MachineDetail.vue
+++ b/plugins/machines/frontend/views/MachineDetail.vue
@@ -70,6 +70,17 @@
               <span class="hero-detail-value">{{ machine.locationname }}</span>
             </div>
           </div>
+
+          <!-- The 6am band, machine side: which PCs drive this machine. The
+               same fact as a PC's "Serves machine", read from the other end -
+               and the end somebody is standing at when the machine has
+               stopped. It lived only in the relationships card near the
+               bottom of the page. -->
+          <AssetTriageBand
+            :assetid="machine.assetid"
+            counterparttype="computer"
+            counterpartlabel="Controlled by"
+          />
         </div>
       </div>
 
@@ -253,6 +264,7 @@ import { useRoute, useRouter } from 'vue-router'
 import { machinesApi } from '@/api'
 import { withBase } from '@/utils/basePath'
 import LocationMapTooltip from '@/components/LocationMapTooltip.vue'
+import AssetTriageBand from '@/components/AssetTriageBand.vue'
 import CustomFieldsSection from '@/components/CustomFieldsSection.vue'
 import PluginAssetPanels from '@/components/PluginAssetPanels.vue'
 import AssetRelationships from '@/components/AssetRelationships.vue'
diff --git a/plugins/measuringtools/frontend/views/MeasuringToolDetail.vue b/plugins/measuringtools/frontend/views/MeasuringToolDetail.vue
index dad0f38a..f92b7eb2 100644
--- a/plugins/measuringtools/frontend/views/MeasuringToolDetail.vue
+++ b/plugins/measuringtools/frontend/views/MeasuringToolDetail.vue
@@ -46,6 +46,15 @@
               <span class="hero-detail-value">{{ tool.locationname }}</span>
             </div>
           </div>
+
+          <!-- The 6am band. A gage usually has no controls edge at all,
+               and the band renders nothing when it has nothing to say - it is
+               here so the five asset pages stay one shape rather than five. -->
+          <AssetTriageBand
+            :assetid="tool.assetid"
+            counterparttype="machine"
+            counterpartlabel="Used on"
+          />
         </div>
       </div>
 
@@ -169,6 +178,7 @@ import { ref, onMounted } from 'vue'
 import { useRoute, useRouter } from 'vue-router'
 import { colorStyle } from '@/utils/colorStyle'
 import { measuringtoolsApi } from '@/api'
+import AssetTriageBand from '@/components/AssetTriageBand.vue'
 import CustomFieldsSection from '@/components/CustomFieldsSection.vue'
 import PluginAssetPanels from '@/components/PluginAssetPanels.vue'
 import AssetRelationships from '@/components/AssetRelationships.vue'
diff --git a/plugins/network/frontend/views/NetworkDeviceDetail.vue b/plugins/network/frontend/views/NetworkDeviceDetail.vue
index 365654d7..e3c3d5ac 100644
--- a/plugins/network/frontend/views/NetworkDeviceDetail.vue
+++ b/plugins/network/frontend/views/NetworkDeviceDetail.vue
@@ -68,6 +68,14 @@
             <span class="hero-detail-value">{{ device.businessunitname }}</span>
           </div>
         </div>
+
+        <!-- The 6am band: what stops if this switch or AP goes down. A network
+             device is rarely interesting in itself; it matters because of what
+             sits behind it. -->
+        <AssetTriageBand
+          :assetid="device.assetid"
+          counterparttype="machine"
+        />
         <div class="hero-features" v-if="device.networkdevice">
           <span v-if="device.networkdevice.ispoe" class="feature-badge poe">PoE</span>
           <span v-if="device.networkdevice.ismanaged" class="feature-badge managed">Managed</span>
@@ -227,6 +235,7 @@ import { useAuthStore } from '@/stores/auth'
 import { networkApi } from '@/api'
 import { withBase } from '@/utils/basePath'
 import AssetRelationships from '@/components/AssetRelationships.vue'
+import AssetTriageBand from '@/components/AssetTriageBand.vue'
 import CustomFieldsSection from '@/components/CustomFieldsSection.vue'
 import PluginAssetPanels from '@/components/PluginAssetPanels.vue'
 import { useWarrantyBadge } from '@/composables/warrantyBadge'
diff --git a/plugins/printers/frontend/views/PrinterDetail.vue b/plugins/printers/frontend/views/PrinterDetail.vue
index d45af3b5..89979167 100644
--- a/plugins/printers/frontend/views/PrinterDetail.vue
+++ b/plugins/printers/frontend/views/PrinterDetail.vue
@@ -66,6 +66,16 @@
               <span class="hero-detail-value mono">{{ ipAddress }}</span>
             </div>
           </div>
+
+          <!-- The 6am band: which machine stops if this printer is down.
+               A shop-floor printer is often a label or tag printer feeding one
+               machine, and that link was only visible in the relationships
+               card near the bottom of the page. -->
+          <AssetTriageBand
+            :assetid="printer.assetid"
+            counterparttype="machine"
+            :relationshiptypes="['usesprinter', 'defaultprinter']"
+          />
         </div>
       </div>
 
@@ -301,6 +311,7 @@ import { useRoute, useRouter } from 'vue-router'
 import { printersApi } from '@/api'
 import { withBase } from '@/utils/basePath'
 import LocationMapTooltip from '@/components/LocationMapTooltip.vue'
+import AssetTriageBand from '@/components/AssetTriageBand.vue'
 import CustomFieldsSection from '@/components/CustomFieldsSection.vue'
 import PluginAssetPanels from '@/components/PluginAssetPanels.vue'
 import AssetRelationships from '@/components/AssetRelationships.vue'
diff --git a/tests/test_core/test_relationship_directional.py b/tests/test_core/test_relationship_directional.py
index 4067b531..5cdf3667 100644
--- a/tests/test_core/test_relationship_directional.py
+++ b/tests/test_core/test_relationship_directional.py
@@ -104,3 +104,50 @@ def test_relationships_row_carries_isdirectional(client, db, auth_headers):
     ctrl_rows = [r for r in data['outgoing']
                  if r['relationshiptypename'] == 'controls']
     assert ctrl_rows and all(r['isdirectional'] is True for r in ctrl_rows)
+
+def test_the_controlled_asset_sees_the_link_from_its_own_page(client, db, auth_headers):
+    """The target of a directional edge must receive it in `incoming`.
+
+    A PC controls a machine, and the row is stored once, source=PC. The PC's
+    page reads it from `outgoing`; the machine's page can only ever see it in
+    `incoming`. Nothing asserted that second half, and a UI was shipped that
+    rendered the link on the PC page and showed the machine page nothing - the
+    reciprocal-links defect. The endpoint was correct all along, which is
+    exactly why this assertion is worth having: it pins the contract the
+    frontend depends on, so the next such bug cannot be blamed on the API.
+    """
+    atype_machine = AssetType(assettype='machine')
+    atype_computer = AssetType(assettype='computer')
+    db.session.add_all([atype_machine, atype_computer])
+    db.session.flush()
+
+    controls = RelationshipType(relationshiptype='controls', isdirectional=True)
+    db.session.add(controls)
+    db.session.flush()
+
+    pc = _make_asset('PC-1', atype_computer.assettypeid)
+    machine = _make_asset('M-1', atype_machine.assettypeid)
+
+    # Stored ONCE, in the canonical direction only.
+    db.session.add(AssetRelationship(sourceassetid=pc.assetid,
+                                     targetassetid=machine.assetid,
+                                     relationshiptypeid=controls.relationshiptypeid))
+    db.session.commit()
+
+    resp = client.get(f'/api/assets/{machine.assetid}/relationships',
+                      headers=auth_headers)
+    assert resp.status_code == 200
+    data = resp.get_json()['data']
+
+    assert data['outgoing'] == [], 'the machine controls nothing'
+    assert len(data['incoming']) == 1, 'the machine must see the PC that controls it'
+
+    row = data['incoming'][0]
+    assert row['relationshiptypename'] == 'controls'
+    # The peer has to arrive with the fields the UI routes on. assetid alone
+    # is not enough: the detail routes key on pluginid, and the type name
+    # chooses the route base.
+    peer = row['sourceasset']
+    assert peer is not None
+    assert peer['assetid'] == pc.assetid
+    assert peer['assettypename'] == 'computer'