Skip to content

Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.

docs(erd): say a self-reference stays a foreign-key column, not a same-entity edge

tt-a1i9472fd192430
diff --git a/archify/references/authoring-contract.md b/archify/references/authoring-contract.md
index e29c9f66..ce8ba465 100644
--- a/archify/references/authoring-contract.md
+++ b/archify/references/authoring-contract.md
@@ -363,7 +363,7 @@ straight corridor. Never place an unrelated entity between two aligned anchors;
the router can detour around it, but the clear corridor is shorter and reads
better. A junction table has two parents: put it in a cell beside or between
both, not beneath one of them with tables stacked between it and the other,
-and keep every table that shares its domain tag in one solid block of cells.
+and keep every table that shares its domain tag in one solid block of cells. A relationship must connect two different entities; a self-reference such as manager_id stays as a foreign-key column (and optionally a card), not an `employees`→`employees` edge.
Use `row`/`col` for this normal grouped layout, and only use explicit
`pos`/`via` after a diagnostic identifies a concrete geometry problem.