Privacy and abuse controls

DeDi is oriented toward public information, but public does not mean frictionless bulk abuse should be ignored.

Operators SHOULD document:

• whether namespace and registry enumeration is intentionally public,
• rate limits for query and historical endpoints,
• bulk access expectations,
• scraping posture,
• and what data classes should never be published in DeDi.

Historical endpoints and pagination-heavy queries deserve special attention because they are frequently the easiest abuse path.