A small review gate for public-source workflows

Public-source automation needs a visible boundary before the first request: what the source allows, what the source says, and what policy applies when the answer is unclear.

A small review loop can make that boundary inspectable:

1. Record the source URL with its stated terms and robots context.
2. Make the intended request scope explicit.
3. Return a review result instead of silently treating an ambiguous source as allowed.
4. Preserve the decision beside the downstream workflow.

The Robots, Terms & Source Policy Linter API produces a bounded policy-and-evidence check for this review step. The Public Source Health Badge API is separate: it focuses on source availability and freshness checks.

These tools support review. They do not replace source-owner permission, legal advice, or accountable operational ownership.

I publish these products and wrote this post to explain their intended scope.