Verification hub

The Automation Boundary Standard

The collection standard every X'am is taken under.

The standard is the product

We do not sell the ability to keep collecting past a boundary. We sell proof that boundaries hold. The standard below is what a reading is taken under, and it is what we are asking the market to adopt.

The standard

• No credentials - no account, token, or credential we were not given is ever presented.
• No bypass - no CAPTCHA solving, no proxy, address, or user-agent rotation, no simulated human behavior.
• Hard stop - when a technical access control appears, collection stops.
• No retry - a stop is not re-attempted by an alternate route.
• Data minimization - only what the disclosed purpose requires is collected.
• No overclaim - a reading states what was observed and what was not observed in the sample, and nothing beyond it.

Why the detail stops here

We publish the standard, not target-specific collection detail. A document that taught a reader how to collect against a particular subject would undercut the standard it claims to defend.

When the standard is hit

A hard stop is not a failed reading. It is a recorded result: the boundary appeared and collection stopped. Where a position cannot be reached without crossing the standard, it is recorded NOT-MEASURABLE.