Data handling boundary
Bound the data before the workflow. Public intake is for qualification and scoping, not unrestricted transfer of sensitive material.
Before a pilot
Define the workflow, permitted evidence sources, data classification, accountable reviewer, system boundary, and success criterion before substantive evaluation work begins.
Public intake
Use the public intake path for sanitized descriptions and representative, non-confidential material. The browser can hash permitted files locally to create a manifest; the public pilot intake does not upload those file bytes.
Restricted material
Confidential, regulated, privileged, credential-bearing, export-controlled, production, or personal data requires a separate handling decision and may require different infrastructure, agreements, access controls, retention rules, or customer-side execution.
Human authorization
Consequential outputs remain subject to the review and authorization requirements defined for the workflow. Fieldborne does not treat model output alone as final authority.
Evidence record
Where an evaluation proceeds, workflow state, permitted sources, reviewer decisions, exceptions, approvals, denials, and limitations should remain traceable to the bounded evaluation scope.
Supplier and model context
Deployment-specific supplier, model, version, configuration, and contractual evidence must be identified for the actual customer workflow. A generic public-site description is not a substitute for that deployment record.