Intake Boundary

Definition

An intake boundary names the fields the public form may collect, the fields it must not collect, the storage state at intake time, and the operator-side handling that follows. It is one of four operating boundaries — intake, consent, anti-spam, retention — that together define the data-handling posture of the public intake.

Why it matters

Without a documented intake boundary, the form surface accumulates fields and processors over time without explicit decisions. The current prototype intake stays inside a narrow boundary; production intake widens it deliberately, only after the boundaries are reviewed.

Explore related entities

• Consent Boundary The operating boundary that defines what the user is consenting to when they submit the public intake, and what the surface must show before that submission.
• Anti-Spam Boundary The operating boundary that defines the minimum spam and abuse controls a production intake surface must hold before being enabled.
• Data Retention Boundary The operating boundary that defines how long prospect data is retained after intake, when it must be deleted, and who is responsible for both.
• Production Launch Gate The operating gate that production launch must clear: reviewed Privacy Policy and Terms, intake/consent/anti-spam/retention boundaries, endpoint scope, analytics disclosure, and the production-domain plan.
• Public-Signal Diagnostic A diagnostic review that uses only publicly observable surfaces of a business — no credentials, no shared accounts, no internal data movement.