ai-crawler-readiness

Most tools are clearly distinct: domain_readiness covers archived per-domain status, measure_domain covers fresh measurement, edge_blocking covers vendor attribution, recent_changes covers temporal flips, and web_openness covers aggregate statistics. The only close pair is domain_readiness and measure_domain, but the explicit 'right now' vs 'archive' distinction prevents serious confusion.

All names are readable snake_case, but they do not follow a consistent pattern: domain_readiness and web_openness are noun compounds, edge_blocking is noun+gerund, measure_domain is verb+noun, and recent_changes is adjective+noun. The mixed conventions are still predictable enough to infer intent, but they are not uniform.

Five tools is well-scoped for an analytics and measurement server. Each tool covers a distinct question a user would reasonably ask: one domain now, one domain from archived data, which edge vendor is responsible, what changed recently, and overall web openness. There is no obvious redundancy or bloat.

The tool surface covers the core workflows: per-domain readiness, live remeasurement, aggregate openness, vendor-level edge blocking, and change detection. A minor gap is the lack of a direct way to enumerate all domains that currently block a specific crawler, but this does not undermine the main use cases.