What does a bounded pilot look like when a policy changes an intake form?

An engagement coordinator is reviewing ENG-0734 when a revised acceptance policy introduces a conflict declaration. The old intake form contains the client category, proposed work and approving role, but no field for the new declaration. The engagement has not yet been accepted.

The pilot asks the agent to migrate the submission into the new form structure. Existing answers that remain valid must carry across. The new declaration must remain unanswered until the appropriate role supplies it; the agent cannot infer a negative answer from the absence of a previous field. The resulting record enters a waiting state with a targeted follow-up request.

A buyer can ask for the two form schemas, the policy amendment, the original submission and a field mapping with stated transformation rules. The expected output includes the migrated record and a conversion history showing which values were copied, transformed or left unresolved.

The pilot ends when the submission is correctly prepared for follow-up. Acceptance of the engagement remains outside scope. This creates a concrete first review: the lab can inspect whether the model preserves information and handles newly required evidence without manufacturing an answer.