Mention tradeoffs inherent in building designed-for-purpose APIs. (#440)

jyasskin · web-flow · commit f387e3cacb49 · 2024-10-23T08:42:44.000-07:00
diff --git a/index.html b/index.html
@@ -1912,7 +1912,9 @@
 
 Features that are designed-for-purpose facilitate these principles by providing functionality that is only or primarily
 useful for a particular purpose. Designed-for-purpose features make it easier to explain the purpose to people, and may
-also limit the feasible secondary uses of data.
+also limit the feasible secondary uses of data. When building a designed-for-purpose feature,
+<a data-cite="design-principles#high-level-low-level">consider tradeoffs between high and low-level
+APIs</a>.
 
 [=Controlled de-identified data=] may be used for additional purposes in ways that are compatible with the specified
 purpose.
