diff --git a/seeds/inventory.yaml b/seeds/inventory.yaml
index 97e075d..fb97788 100644
--- a/seeds/inventory.yaml
+++ b/seeds/inventory.yaml
@@ -446,7 +446,12 @@ relationships:
   - {source: "ingress:trmnl.hubris.network", target: "service:trmnl", type: routes-to}
   - {source: "ingress:zimaos.hubris.network", target: "service:zimaos", type: routes-to}
   - {source: "ingress:teddy.hubris.network", target: "service:teddycloud", type: routes-to}
-  - {source: "ingress:mcp.hubris.network", target: "service:homelab-mcp", type: routes-to}
+  # Re-pointed from service:homelab-mcp, which is deprecated — the Python MCP
+  # server on apps/105 was stopped at the Go cutover and mcp.hubris.network now
+  # fronts the Go api. Nomos recorded this correctly on 2026-07-12; the seed
+  # was the stale one, and re-asserting the old edge alongside it is what made
+  # ingress:mcp a cardinality violation.
+  - {source: "ingress:mcp.hubris.network", target: "service:oikos", type: routes-to}
   - {source: "ingress:secrets.hubris.network", target: "service:secrets-issuance", type: routes-to}
   - {source: "ingress:house.hubris.network", target: "service:house", type: routes-to}
   - {source: "ingress:books.hubris.network", target: "service:grimmory", type: routes-to}
diff --git a/seeds/ontology.yaml b/seeds/ontology.yaml
index 12ab8ec..2fd506b 100644
--- a/seeds/ontology.yaml
+++ b/seeds/ontology.yaml
@@ -970,7 +970,12 @@ relationship_types:
     inverse: documented-by
     source: document
     target: entity
-    cardinality: many-to-one
+    # many-to-many, not many-to-one: a single investigation routinely covers
+    # several entities (a fleet-wide apt audit documents every host it
+    # touched), and Nomos has been writing such edges for months. The stricter
+    # declaration made ~40 of them cardinality violations, which only surfaced
+    # once the seed could complete far enough to run ValidateCardinality.
+    cardinality: many-to-many
     description: Document describes an entity.
   involves:
     inverse: involved-in